No. 1 LSU wants to make sure it avoids letdown at Ole Miss
by BRIAN RIPPEEOXFORD, Miss. (AP) - After notching a season-defining victory at Alabama last week, No. 1 LSU is looking to avoid a letdown Saturday at Mississippi.
“We know we’re going to get their best shot,” LSU coach Ed Orgeron said. “They play great at home. It’s going to be a great crowd. It’s going to be a great challenge for our football team.”
It’s a different type of challenge than they faced last week.
TOP STORIES
Justice Kavanaugh addresses private Federalist Society gathering: 'I will always be not afraid'
Nancy Pelosi goes for slam dunk -- and crashes to court
Adam Schiff cracking under 'point of order' pressure
After dealing with Alabama’s high-powered passing attack in a 46-41 triumph over the Crimson Tide, LSU (9-0, 5-0 SEC, No. 1 College Football Playoff ) is dealing with a run-heavy Ole Miss offense commanded by fleet-footed freshman quarterback John Rhys Plumlee.
“They’re very difficult to stop on offense,” Orgeron said. “They have an excellent running game.’’
LSU’s offense will look to continue its torrid pace that has seen quarterback Joe Burrow average 355 yards passing per game. Burrow has thrown 33 touchdowns with just four interceptions.
“That’s pretty amazing,” Ole Miss coach Matt Luke said. “He’s a leader and very good player, and we’ll have our work cut out for us. We’ve got to find ways to slow them down and bow our neck in the red zone, try to hold them to field goals.  You try to find ways to slow them down.”
Ole Miss (4-6, 2-4) must pull the upset to maintain its slim hopes of becoming bowl eligible.
Some other things to know about the LSU-Ole Miss game:
EDWARDS-HELAIRE’S SURGE
LSU’s Clyde Edwards-Helaire is coming off a 103-yard, three-touchdown performance against Alabama.
“Unbelievable,” Oregon said. “I don’t know if I have seen a performance like that as a football player in a big game like that. I really don’t. I don’t know, I can’t recall.”
Edwards-Helaire also rushed for over 100 yards against No. 11 Florida (No. 11 CFP) and No. 13 Auburn (No. 12 CFP) last month.
“He’s so important to our team,” Burrow said. “He can catch the ball out of the backfield. He makes it difficult to play man-to-man, because you have a linebacker matched up on him and no linebacker in the country can cover Clyde. And then you go zone and we can pound it up the middle.”
The Rebels are doing a better job of containing the run under first-year defensive coordinator Mike MacIntyre, but Edwards will be one of the best backs the unit has faced all season.
STAYING FOCUSED
The win over Alabama ended LSU’s eight-game losing streak in that annual series and moved the Tigers atop the CFP rankings.
With Ole Miss, Arkansas and Texas A&M; left on the schedule before a potential SEC championship game berth, the Tigers must maintain their focus.
“We have a really mature team that understands the magnitude of the moment and understands where we can go as a team,” Burrow said when asked how players would avoid the natural inclination to become distracted from the task at hand by the increasing likelihood of appearing in SEC title game and College Football Playoff. “They know what we can do. They know what’s ahead of us.”
VULNERABILITY UP FRONT
LSU left tackles Saahdiq Charles and backup left tackle Dare Rosenthal are expected to miss this game. Right tackle Austin Deculus also is unlikely to play.
Ole Miss has been formidable up front and much better at rushing the passer than it was in 2018.
“The pass rush techniques have gotten better as the year has gone along,” MacIntyre said. “We are definitely going to need a pass rush in this game. Burrow does a great job getting rid of the ball.”
BURROW’S ACCURACY
Burrow has completed 78.9 percent of his passes to lead all Football Bowl Subdivision players. He went 31 of 39 against Alabama.
He could be in store for another monster game this week against a young Ole Miss secondary that has struggled at times.
Burrow said the Alabama game demonstrated that, “nobody can really stop us, and we can make lives difficult for a lot of defenses by putting different people in different spots, so we’re just going to keep doing what we do.”
More AP college football: https://apnews.com/Collegefootball and https://twitter.com/AP_Top25
Sign up for Daily Newsletters
Copyright © 2019 The Washington Times, LLC.
Please read our comment policy before commenting.


影/音通話
如果您仍在使用 Skype、Viber 或 Google Hangouts 等影音會議即時通訊軟體，不妨考慮其它的替代品吧。 請注意前面提到的多項即時通，其中不之乏支援VoIP功能者。下列軟體則以影音為主打。
{% include cardv2.html
title="Linphone"
image="/assets/img/svg/3rd-party/linphone.svg"
website="https://www.linphone.org/"
privacy-policy="https://www.linphone.org/terms-and-privacy"
description="Linphone 是個開源 SIP 電話，它可利用網路服務來撥打免費語音電話, 其能運行在手機與桌機環境和網頁瀏覽器。它支援 ZRTP 的端點到端點之間的影音加密通訊。"
forum="https://forum.privacytools.io/t/discussion-linphone/751"
github="https://github.com/BelledonneCommunications"
windows="https://www.linphone.org/technical-corner/linphone?qt-technical_corner=2#qt-technical_corner"
linux="https://www.linphone.org/technical-corner/linphone?qt-technical_corner=2#qt-technical_corner"
mac="https://www.linphone.org/technical-corner/linphone?qt-technical_corner=2#qt-technical_corner"
fdroid="https://f-droid.org/packages/org.linphone"
googleplay="https://play.google.com/store/apps/details?id=org.linphone"
ios="https://itunes.apple.com/us/app/linphone/id360065638?mt=8"
%}
{% include cardv2.html
title="Jitsi Meet"
image="/assets/img/svg/3rd-party/jitsi.svg"
website="https://jitsi.org/jitsi-meet/"
privacy-policy="https://jitsi.org/security/"
description='免費開源的跨平台網路電話（VoIP），視訊會議與即時通訊應用軟體，有 E2EE 可選，能運行於瀏覽器、桌面軟體或手機。能透過畫面分享縮小對話浮動視窗進行簡報。Jitsi Meet 公共服務站台列表。'
labels="color==warning::text==Requires WebRTC::tooltip==Our Firefox tweaks recommend disabling WebRTC as it can be used to leak your IP address even behind a VPN, which is why Tor Browser disables it.|color==warning::link==https://github.com/jitsi/lib-jitsi-meet/blob/master/doc/e2ee.md::text==Experimental E2EE::tooltip==E2EE in Jitsi Meet is dependent on Insertable Streams, which is currently supported in Chrome but not Firefox. The mobile apps also do not support E2EE for the moment. Prefer to use the desktop apps instead."
forum="https://forum.privacytools.io/t/discussion-jitsi-meet/1577"
github="https://github.com/jitsi/jitsi-meet"
windows="https://github.com/jitsi/jitsi-meet-electron/releases"
linux="https://github.com/jitsi/jitsi-meet-electron/releases"
mac="https://github.com/jitsi/jitsi-meet-electron/releases"
fdroid="https://f-droid.org/en/packages/org.jitsi.meet/"
googleplay="https://play.google.com/store/apps/details?id=org.jitsi.meet"
ios="https://apps.apple.com/us/app/jitsi-meet/id1165103905"
%}
{% include cardv2.html
title="Mumble"
image="/assets/img/svg/3rd-party/mumble.svg"
website="https://mumble.info/"
description="Mumble 為開源、低延遲高品質之語音聊天軟體，它主要用在打電玩遊戲。請注意 Mumble 本身預設不存留訊息與活動記錄。 可惜無支援點對點加密，故最好自行搭架此軟體。"
forum="https://forum.privacytools.io/t/discussion-mumble/1289"
github="https://github.com/mumble-voip/"
windows="https://www.mumble.info/downloads"
linux="https://www.mumble.info/downloads"
mac="https://www.mumble.info/downloads"
android="https://www.mumble.info/downloads/#third-party-clients"
ios="https://apps.apple.com/us/app/mumble/id443472808?ls=1"
%}
相關資訊


We feature a limited selection of bikes, but you can be sure that you'll be set up with a quality bike when you shop with us. In addition to these three solid models, we have access to countless upgrades and parts to customize your bike.
PHONE:<PHONE_NUMBER>
EMAIL: info@mountainspoke.com


Hitler memorabilia auction rakes in thousands of euros despite protests
by AFP/The LocalAn auction of Nazi memorabilia, including Adolf Hitler's top hat, raked in hundreds of thousands of euros in Munich Wednesday amid German and international protest.
The hammer fell on the Nazi leader's top hat at €50,000, according to the Hermann Historica auction house website, while items of clothing belonging to his partner Eva Braun each sold for thousands.
One buyer paid €130,000 for a silver-plated copy of Hitler's anti-Semitic political manifesto Mein Kampf that once belonged to senior Nazi Hermann Göring, emblazoned with an eagle and the party's swastika emblem.
Other lots of clothing and personal belongings from notorious World War II Nazi leaders like Heinrich Himmler and Rudolf Hess also packed the catalogue pages.
READ ALSO: Hitler memorabilia auction in Munich sparks protests
"The Nazis' crimes are being trivialized here," the German government's anti-Semitism commissioner Felix Klein told the Funke newspaper group.
"They're acting as if they're trading in perfectly normal historical art objects," but "there is a danger that Nazi relics become cult objects" for the extreme right, he added.
A cocktail dress from Eva Braun, Hitler's long-term companion who was briefly his wife before their death. Photo: DPA
Ahead of the auction, European Jewish Association chairman Rabbi Menachem Margolin recalled that "it is Germany that leads Europe in the sheer volume of reported antisemitic incidents".
"We urge the German authorities to compel auction houses to divulge the names of those who are buying," who "should then be put on a government 'watch' list," Margolin said.
Many of the items belonging to top Nazi leaders were seized by US soldiers in the final days of World War II.
READ ALSO: Outrage grows over Hitler masks on sale in Prague
The dresses belonging to Braun, Hitler's long-term companion who was briefly his wife before their death, were found among 40 trunks seized by the US military in May 1945 in Salzburg in Austria.
Some of the more unusual lots include a copy of Hitler's rental contract in Munich and a pair of sunglasses worn by a defendant at the Nazi war crimes trials in Nuremberg to avoid the glare of the floodlights.


| Question | Answer |
|---|---|
| How do I share my pickup location? | When you request a ride, your driver will see where you've place your pickup location pin. For improved pickups, you can enable sharing your physical GPS location. This helps drivers know if you are coming towards them, or where to look for you if your pin is not in your exact location. |
| Can I ride with dog? | In accordance with state and federal laws, as well as our policies, service animals are permitted to accompany riders at all times. If you're traveling with a pet that's not a service animal, drivers may choose whether or not to allow the pet in their vehicle. |


| [ Team LiB ] |
4.4 Expressions and OperatorsAn expression is a phrase of code that the Python interpreter can evaluate to produce a value. The simplest expressions are literals and identifiers. You build other expressions by joining subexpressions with the operators and/or delimiters in Table 4-2. This table lists the operators in decreasing order of precedence, so operators with higher precedence are listed before those with lower precedence. Operators listed together have the same precedence. The A column lists the associativity of the operator, which can be L (left-to-right), R (right-to-left), or NA (non-associative). In Table 4-2, expr, key, f, index, x, and y indicate any expression, while attr and arg indicate identifiers. The notation ,... indicates that commas join zero or more repetitions, except for string conversion, where one or more repetitions are allowed. A trailing comma is also allowed and innocuous in all such cases, except with string conversion, where it's forbidden.
You can chain comparisons, implying a logical and. For example: a < b <= c < d has the same meaning as: a < b and b <= c and c < d The chained form is more readable and evaluates each subexpression only once. Operators and and or short-circuit their operands' evaluation: the right-hand operand evaluates only if its value is needed to get the truth value of the entire and or or operation. In other words, x and y first evaluates x and if x is false, the result is x; otherwise, the result is y. By the same token, x or y first evaluates x and if x is true, the result is x; otherwise, the result is y. Note that and and or don't force their results to be True or False, but rather return one or the other of their operands. This lets you use these operators more generally, not just in Boolean contexts. and and or, because of their short-circuiting semantics, differ from all other operators, which fully evaluate all operands before performing the operation. As such, and and or let the left operand act as a guard for the right operand. |
| [ Team LiB ] |


{% extends "base.html" %} {% import "bootstrap/wtf.html" as wtf %} {% block page_content %}
On profile: {{ current_user.username }}


Registration form here. There should be redirects to selected class if guest clicked an Enroll Now button.
Social media should be available?


A JavaScript file contains code that allows a user to interact with a browser or a web-based application. In some cases, the user may be presented with Windows controls to fill out or retrieve values from them. As an application developer, there are two types of values you will deal with. Primitive types are those created from simple types. We will study them when we get to variables. The other types of values are referred to as class types. We will explore them more when we get to object-oriented programming.
JavaScript uses the concept of class to identify or manage the many of the values used in an application. Consider an object like a house. It has such characteristics as its type (single family, town house, condominium, etc), the number of bedrooms, the number of bathrooms, etc. These characteristics are used to describe a house to somebody who wants to buy it. To get such an object, you must first define the criteria that describe it.
Soy SWAP 1
Soy SWAP 2


Sole is a new project taking place at EII. The project aims to adapt the Solid platform, for building a messagin application resulting in true data ownership as well as improved privacy.
Solid (derived from "social linked data") is a proposed set of conventions and tools for building decentralized social applications based on Linked Data principles. Solid is modular and extensible and it relies as much as possible on existing W3C standards and protocols.
At a glance, here is what Solid offers...
Users should have the freedom to choose where their data resides and who is allowed to access it. By decoupling content from the application itself, users are now able to do so.
Because applications are decoupled from the data they produce, users will be able to avoid vendor lock-in, seamlessly switching between apps and personal data storage servers, without losing any data or social connections.
Developers will be able to easily innovate by creating new apps or improving current apps, all while reusing existing data that was created by other apps.
As the project director, but also as a web developer, Ana is involved in the overall planning and evolution of Sole.
Pablo is the project manager, but he also keeps an eye on the research aspects of the project.
Astrid is also the project manager, but she also keeps an eye on the research aspects of the project.


Mark ups are tags that make up what you see:
HTML Attridutes (LINKS)
Inline Tags
BLock Tags
Uses paragraghs and break tags
for Example Inline and Block
Block put an invisible block around your text.
Inline elements are a,em,br,img,strong
Span is more like an inline element
Div is more like a block element.


Noise Field
Increase X:
Increase Y:
Increase Z:
Particles
Number:
Velocity:
Magnitude:
General
Scale:
Start simulation
Reset


ODAC Ford Housing - Admin
View and reply to housing-related queries.
- The housing allocation process is explained at *120*8864*1280#
- At that same number, community members can subscribe to SMS notifications on the status of housing projects in their area.
- If users have any queries, they can send an SMS to 083 9300 2801 0243
- This website is used by ODAC and the relevant local officials, for sending timely SMS notifications, and responding to queries.
{% if not current_user.is_authenticated() %}
{{ link | safe }}
{% endif %}


(Bi .Ta tetragonal orange pigments {border-style color px;} #ffffff;} samples cubic band crystal structure Bayferrox pigment Figure inorganic Table using .() monoclinic oxide pigments. px; reflectance sample solid {font-family .), Bi–O bond font-size gap high lattice phase properties ./s--- Anal. Calorim. Chem. Chemical Synthesis Therm. Wang absorption based calculated chemical double; energy observed optical room synthesized value Šulcová δ-Bi Phys. Thermal bismuth border-color border-width commercial composed friendly light obtained particle single-phase smaller solid; synthesis valence volumes {font-style {font-weight β-phase -doped ./j.dyepig... ACS Ch° Dyes Pigm. Trojan UV–vis XRD Zhang a*) article average b*) bold compared conduction conventional courier; em; environmentally exhibited hybrid ion phases pt;} reaction samples, samples. solid-state spectra summarized wavelength β-Bi δ-phase


|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
public interface ClientSessionFactory
A ClientSessionFactory is the entry point to create and configure HornetQ resources to produce and consume messages.
It is possible to configure a factory using the setter methods only if no session has been created.
Once a session is created, the configuration is fixed and any call to a setter method will throw a IllegalStateException.
| Method Summary | |
|---|---|
void |
addInterceptor(Interceptor interceptor)
Adds an interceptor which will be executed after packets are received from the server. |
void |
close()
Closes this factory and release all its resources |
ClientSessionFactory |
copy()
Creates a copy of this factory. |
ClientSession |
createSession()
Creates a non-transacted session. |
ClientSession |
createSession(boolean autoCommitSends,
boolean autoCommitAcks)
Creates a session. |
ClientSession |
createSession(boolean xa,
boolean autoCommitSends,
boolean autoCommitAcks)
Creates a session. |
ClientSession |
createSession(boolean xa,
boolean autoCommitSends,
boolean autoCommitAcks,
boolean preAcknowledge)
Creates a session. |
ClientSession |
createSession(boolean autoCommitSends,
boolean autoCommitAcks,
int ackBatchSize)
Creates a session. |
ClientSession |
createSession(String username,
String password,
boolean xa,
boolean autoCommitSends,
boolean autoCommitAcks,
boolean preAcknowledge,
int ackBatchSize)
Creates an authenticated session. |
ClientSession |
createTransactedSession()
Creates a transacted session. |
ClientSession |
createXASession()
Creates a session with XA transaction semantics. |
int |
getAckBatchSize()
Returns the acknowledgements batch size. |
long |
getCallTimeout()
Returns the blocking calls timeout. |
long |
getClientFailureCheckPeriod()
Returns the period used to check if a client has failed to receive pings from the server. |
int |
getConfirmationWindowSize()
Returns the size for the confirmation window of clients using this factory. |
String |
getConnectionLoadBalancingPolicyClassName()
Returns the class name of the connection load balancing policy. |
long |
getConnectionTTL()
Returns the connection time-to-live. |
int |
getConsumerMaxRate()
Returns the maximum rate of message consumption for consumers created through this factory. |
int |
getConsumerWindowSize()
Returns the window size for flow control of the consumers created through this factory. |
String |
getDiscoveryAddress()
Returns the address to listen to discover which connectors this factory can use. |
long |
getDiscoveryInitialWaitTimeout()
Returns the initial wait timeout if this factory is configured to use discovery. |
int |
getDiscoveryPort()
Returns the port to listen to discover which connectors this factory can use. |
long |
getDiscoveryRefreshTimeout()
Returns the refresh timeout for discovered HornetQ servers. |
String |
getGroupID()
Returns the group ID that will be eventually set on each message for the property Message.HDR_GROUP_ID . |
int |
getInitialMessagePacketSize()
Returns the initial size of messages created through this factory. |
String |
getLocalBindAddress()
Returns the local bind address to which the multicast socket is bound for discovery. |
long |
getMaxRetryInterval()
Returns the maximum retry interval (in the case a retry interval multiplier has been specified). |
int |
getMinLargeMessageSize()
Returns the large message size threshold. |
int |
getProducerMaxRate()
Returns the maximum rate of message production for producers created through this factory. |
int |
getProducerWindowSize()
Returns the window size for flow control of the producers created through this factory. |
int |
getReconnectAttempts()
Returns the maximum number of attempts to retry connection in case of failure. |
long |
getRetryInterval()
Returns the time to retry connections created by this factory after failure. |
double |
getRetryIntervalMultiplier()
Returns the multiplier to apply to successive retry intervals. |
int |
getScheduledThreadPoolMaxSize()
Returns the maximum size of the scheduled thread pool. |
List<Pair<TransportConfiguration,TransportConfiguration>> |
getStaticConnectors()
Returns the list of live - backup connectors pairs configured that sessions created by this factory will use to connect to HornetQ servers or null if the factory is using discovery group. |
int |
getThreadPoolMaxSize()
Returns the maximum size of the thread pool. |
boolean |
isAutoGroup()
Returns whether producers created through this factory will automatically assign a group ID to the messages they sent. |
boolean |
isBlockOnAcknowledge()
Returns whether consumers created through this factory will block while sending message acknowledgements or do it asynchronously. |
boolean |
isBlockOnDurableSend()
Returns whether producers created through this factory will block while sending durable messages or do it asynchronously. |
boolean |
isBlockOnNonDurableSend()
Returns whether producers created through this factory will block while sending non-durable messages or do it asynchronously. |
boolean |
isCacheLargeMessagesClient()
When true , consumers created through this factory will create temporary files to cache large messages. |
boolean |
isFailoverOnInitialConnection()
Returns true if the client will automatically attempt to connect to the backup server if the initial connection to the live server fails Default value is HornetQClient.DEFAULT_FAILOVER_ON_INITIAL_CONNECTION . |
boolean |
isFailoverOnServerShutdown()
Returns whether connections created by this factory must failover in case the server they are connected to has normally shut down. |
boolean |
isPreAcknowledge()
Returns whether messages will pre-acknowledged on the server before they are sent to the consumers or not. |
boolean |
isUseGlobalPools()
Returns whether this factory will use global thread pools (shared among all the factories in the same JVM) or its own pools. |
boolean |
removeInterceptor(Interceptor interceptor)
Removes an interceptor. |
void |
setAckBatchSize(int ackBatchSize)
Sets the acknowledgements batch size. |
void |
setAutoGroup(boolean autoGroup)
Sets whether producers created through this factory will automatically assign a group ID to the messages they sent. |
void |
setBlockOnAcknowledge(boolean blockOnAcknowledge)
Sets whether consumers created through this factory will block while sending message acknowledgements or do it asynchronously. |
void |
setBlockOnDurableSend(boolean blockOnDurableSend)
Sets whether producers created through this factory will block while sending durable messages or do it asynchronously. |
void |
setBlockOnNonDurableSend(boolean blockOnNonDurableSend)
Sets whether producers created through this factory will block while sending non-durable messages or do it asynchronously. |
void |
setCacheLargeMessagesClient(boolean cached)
Sets whether large messages received by consumers created through this factory will be cached in temporary files or not. |
void |
setCallTimeout(long callTimeout)
Sets the blocking call timeout. |
void |
setClientFailureCheckPeriod(long clientFailureCheckPeriod)
Sets the period (in milliseconds) used to check if a client has failed to receive pings from the server. |
void |
setConfirmationWindowSize(int confirmationWindowSize)
Sets the size for the confirmation window buffer of clients using this factory. |
void |
setConnectionLoadBalancingPolicyClassName(String loadBalancingPolicyClassName)
Sets the class name of the connection load balancing policy. |
void |
setConnectionTTL(long connectionTTL)
Sets this factory's connections time-to-live. |
void |
setConsumerMaxRate(int consumerMaxRate)
Sets the maximum rate of message consumption for consumers created through this factory. |
void |
setConsumerWindowSize(int consumerWindowSize)
Sets the window size for flow control of the consumers created through this factory. |
void |
setDiscoveryAddress(String discoveryAddress)
Sets the address to listen to discover which connectors this factory can use. |
void |
setDiscoveryInitialWaitTimeout(long initialWaitTimeout)
Sets the initial wait timeout if this factory is configured to use discovery. |
void |
setDiscoveryPort(int discoveryPort)
Sets the port to listen to discover which connectors this factory can use. |
void |
setDiscoveryRefreshTimeout(long discoveryRefreshTimeout)
Sets the refresh timeout for discovered HornetQ servers. |
void |
setFailoverOnInitialConnection(boolean failover)
Sets the value for FailoverOnInitialReconnection |
void |
setFailoverOnServerShutdown(boolean failoverOnServerShutdown)
Sets whether connections created by this factory must failover in case the server they are connected to has normally shut down |
void |
setGroupID(String groupID)
Sets the group ID that will be set on each message sent through this factory. |
void |
setInitialMessagePacketSize(int size)
Sets the initial size of messages created through this factory. |
void |
setLocalBindAddress(String localBindAddress)
Sets the local bind address to which the multicast socket is bound for discovery. |
void |
setMaxRetryInterval(long maxRetryInterval)
Sets the maximum retry interval. |
void |
setMinLargeMessageSize(int minLargeMessageSize)
Sets the large message size threshold. |
void |
setPreAcknowledge(boolean preAcknowledge)
Sets to true to pre-acknowledge consumed messages on the server before they are sent to consumers, else set to false to let
clients acknowledge the message they consume. |
void |
setProducerMaxRate(int producerMaxRate)
Sets the maximum rate of message production for producers created through this factory. |
void |
setProducerWindowSize(int producerWindowSize)
Returns the window size for flow control of the producers created through this factory. |
void |
setReconnectAttempts(int reconnectAttempts)
Sets the maximum number of attempts to retry connection in case of failure. |
void |
setRetryInterval(long retryInterval)
Sets the time to retry connections created by this factory after failure. |
void |
setRetryIntervalMultiplier(double retryIntervalMultiplier)
Sets the multiplier to apply to successive retry intervals. |
void |
setScheduledThreadPoolMaxSize(int scheduledThreadPoolMaxSize)
Sets the maximum size of the scheduled thread pool. |
void |
setStaticConnectors(List<Pair<TransportConfiguration,TransportConfiguration>> staticConnectors)
Sets the static list of live - backup connectors pairs that sessions created by this factory will use to connect to HornetQ servers. |
void |
setThreadPoolMaxSize(int threadPoolMaxSize)
Sets the maximum size of the thread pool. |
void |
setUseGlobalPools(boolean useGlobalPools)
Sets whether this factory will use global thread pools (shared among all the factories in the same JVM) or its own pools. |
| Method Detail |
|---|
ClientSession createXASession() throws HornetQException
HornetQException
- if an exception occurs while creating the sessionClientSession createTransactedSession() throws HornetQException
HornetQException
- if an exception occurs while creating the sessionClientSession.commit()
ClientSession createSession() throws HornetQException
HornetQException
- if an exception occurs while creating the sessionClientSession createSession(boolean autoCommitSends, boolean autoCommitAcks) throws HornetQException
autoCommitSends
- true
to automatically commit message sends, false
to commit manuallyautoCommitAcks
- true
to automatically commit message acknowledgement, false
to commit manually
HornetQException
- if an exception occurs while creating the sessionClientSession createSession(boolean autoCommitSends, boolean autoCommitAcks, int ackBatchSize) throws HornetQException
autoCommitSends
- true
to automatically commit message sends, false
to commit manuallyautoCommitAcks
- true
to automatically commit message acknowledgement, false
to commit manuallyackBatchSize
- the batch size of the acknowledgements
HornetQException
- if an exception occurs while creating the sessionClientSession createSession(boolean xa, boolean autoCommitSends, boolean autoCommitAcks) throws HornetQException
xa
- whether the session support XA transaction semantic or notautoCommitSends
- true
to automatically commit message sends, false
to commit manuallyautoCommitAcks
- true
to automatically commit message acknowledgement, false
to commit manually
HornetQException
- if an exception occurs while creating the sessionClientSession createSession(boolean xa, boolean autoCommitSends, boolean autoCommitAcks, boolean preAcknowledge) throws HornetQException
xa
- whether the session support XA transaction semantic or notautoCommitSends
- true
to automatically commit message sends, false
to commit manuallyautoCommitAcks
- true
to automatically commit message acknowledgement, false
to commit manuallypreAcknowledge
- true
to pre-acknowledge messages on the server, false
to let the client acknowledge the messages
HornetQException
- if an exception occurs while creating the sessionClientSession createSession(String username, String password, boolean xa, boolean autoCommitSends, boolean autoCommitAcks, boolean preAcknowledge, int ackBatchSize) throws HornetQException
username
- the user namepassword
- the user passwordxa
- whether the session support XA transaction semantic or notautoCommitSends
- true
to automatically commit message sends, false
to commit manuallyautoCommitAcks
- true
to automatically commit message acknowledgement, false
to commit manuallypreAcknowledge
- true
to pre-acknowledge messages on the server, false
to let the client acknowledge the messages
HornetQException
- if an exception occurs while creating the sessionList<Pair<TransportConfiguration,TransportConfiguration>> getStaticConnectors()
null
if the factory is using discovery group.
The backup configuration (returned by Pair.b
) can be null
if there is no
backup for the corresponding live configuration (returned by Pair.a
)
void setStaticConnectors(List<Pair<TransportConfiguration,TransportConfiguration>> staticConnectors)
Pair.b
) can be null
if there is no
backup for the corresponding live configuration (returned by Pair.a
)
staticConnectors
- a list of pair of TransportConfiguration corresponding to the live - backup nodeslong getClientFailureCheckPeriod()
HornetQClient.DEFAULT_CLIENT_FAILURE_CHECK_PERIOD
.
void setClientFailureCheckPeriod(long clientFailureCheckPeriod)
clientFailureCheckPeriod
- the period to check failureboolean isCacheLargeMessagesClient()
true
, consumers created through this factory will create temporary files to cache large messages.
There is 1 temporary file created for each large message.
Default value is HornetQClient.DEFAULT_CACHE_LARGE_MESSAGE_CLIENT
.
true
if consumers created through this factory will cache large messages in temporary files, false
elsevoid setCacheLargeMessagesClient(boolean cached)
cached
- true
to cache large messages in temporary files, false
elselong getConnectionTTL()
HornetQClient.DEFAULT_CONNECTION_TTL
.
void setConnectionTTL(long connectionTTL)
connectionTTL
- period in millisecondslong getCallTimeout()
HornetQException
with the code HornetQException.CONNECTION_TIMEDOUT
.
Value is in milliseconds, default value is HornetQClient.DEFAULT_CALL_TIMEOUT
.
void setCallTimeout(long callTimeout)
callTimeout
- blocking call timeout in millisecondsint getMinLargeMessageSize()
HornetQClient.DEFAULT_MIN_LARGE_MESSAGE_SIZE
.
void setMinLargeMessageSize(int minLargeMessageSize)
minLargeMessageSize
- large message size threshold in bytesint getConsumerWindowSize()
HornetQClient.DEFAULT_CONSUMER_WINDOW_SIZE
.
void setConsumerWindowSize(int consumerWindowSize)
consumerWindowSize
- window size (in bytes) used for consumer flow controlint getConsumerMaxRate()
HornetQClient.DEFAULT_CONSUMER_MAX_RATE
.
void setConsumerMaxRate(int consumerMaxRate)
consumerMaxRate
- maximum rate of message consumption (in messages per seconds)int getConfirmationWindowSize()
HornetQClient.DEFAULT_CONFIRMATION_WINDOW_SIZE
.
void setConfirmationWindowSize(int confirmationWindowSize)
confirmationWindowSize
- size of the confirmation window (in bytes)int getProducerWindowSize()
HornetQClient.DEFAULT_PRODUCER_WINDOW_SIZE
.
void setProducerWindowSize(int producerWindowSize)
producerWindowSize
- window size (in bytest) for flow control of the producers created through this factory.int getProducerMaxRate()
HornetQClient.DEFAULT_PRODUCER_MAX_RATE
.
void setProducerMaxRate(int producerMaxRate)
producerMaxRate
- maximum rate of message production (in messages per seconds)boolean isBlockOnAcknowledge()
HornetQClient.DEFAULT_BLOCK_ON_ACKNOWLEDGE
.
void setBlockOnAcknowledge(boolean blockOnAcknowledge)
blockOnAcknowledge
- true
to block when sending message acknowledgements or false
to send them asynchronouslyboolean isBlockOnDurableSend()
HornetQClient.DEFAULT_BLOCK_ON_DURABLE_SEND
.
void setBlockOnDurableSend(boolean blockOnDurableSend)
blockOnDurableSend
- true
to block when sending durable messages or false
to send them asynchronouslyboolean isBlockOnNonDurableSend()
HornetQClient.DEFAULT_BLOCK_ON_NON_DURABLE_SEND
.
void setBlockOnNonDurableSend(boolean blockOnNonDurableSend)
blockOnNonDurableSend
- true
to block when sending non-durable messages or false
to send them asynchronouslyboolean isAutoGroup()
true
, a random unique group ID is created and set on each message for the property
Message.HDR_GROUP_ID
.
Default value is HornetQClient.DEFAULT_AUTO_GROUP
.
void setAutoGroup(boolean autoGroup)
autoGroup
- true
to automatically assign a group ID to each messages sent through this factory, false
elseString getGroupID()
Message.HDR_GROUP_ID
.
Default value is is null
and no group ID will be set on the messages.
void setGroupID(String groupID)
groupID
- the group ID to useboolean isPreAcknowledge()
HornetQClient.DEFAULT_PRE_ACKNOWLEDGE
void setPreAcknowledge(boolean preAcknowledge)
true
to pre-acknowledge consumed messages on the server before they are sent to consumers, else set to false
to let
clients acknowledge the message they consume.
preAcknowledge
- true
to enable pre-acknowledgement, false
elseint getAckBatchSize()
HornetQClient.DEFAULT_ACK_BATCH_SIZE
.
void setAckBatchSize(int ackBatchSize)
ackBatchSize
- acknowledgements batch sizeString getLocalBindAddress()
void setLocalBindAddress(String localBindAddress)
localBindAddress
- the local bind addressString getDiscoveryAddress()
void setDiscoveryAddress(String discoveryAddress)
discoveryAddress
- address to listen to discover which connectors this factory can useint getDiscoveryPort()
void setDiscoveryPort(int discoveryPort)
discoveryPort
- port to listen to discover which connectors this factory can uselong getDiscoveryRefreshTimeout()
HornetQClient.DEFAULT_DISCOVERY_REFRESH_TIMEOUT
.
void setDiscoveryRefreshTimeout(long discoveryRefreshTimeout)
discoveryRefreshTimeout
- refresh timeout (in milliseconds) for discovered HornetQ serverslong getDiscoveryInitialWaitTimeout()
HornetQClient.DEFAULT_DISCOVERY_INITIAL_WAIT_TIMEOUT
.
void setDiscoveryInitialWaitTimeout(long initialWaitTimeout)
initialWaitTimeout
- initial wait timeout when using discoveryboolean isUseGlobalPools()
HornetQClient.DEFAULT_USE_GLOBAL_POOLS
.
true
if this factory uses global thread pools, false
elsevoid setUseGlobalPools(boolean useGlobalPools)
useGlobalPools
- true
to let this factory uses global thread pools, false
elseint getScheduledThreadPoolMaxSize()
HornetQClient.DEFAULT_SCHEDULED_THREAD_POOL_MAX_SIZE
.
void setScheduledThreadPoolMaxSize(int scheduledThreadPoolMaxSize)
scheduledThreadPoolMaxSize
- maximum size of the scheduled thread pool.int getThreadPoolMaxSize()
HornetQClient.DEFAULT_THREAD_POOL_MAX_SIZE
.
void setThreadPoolMaxSize(int threadPoolMaxSize)
threadPoolMaxSize
- maximum size of the thread pool.long getRetryInterval()
HornetQClient.DEFAULT_RETRY_INTERVAL
.
void setRetryInterval(long retryInterval)
retryInterval
- time (in milliseconds) to retry connections created by this factory after failuredouble getRetryIntervalMultiplier()
HornetQClient.DEFAULT_RETRY_INTERVAL_MULTIPLIER
.
void setRetryIntervalMultiplier(double retryIntervalMultiplier)
retryIntervalMultiplier
- multiplier to apply to successive retry intervalslong getMaxRetryInterval()
HornetQClient.DEFAULT_MAX_RETRY_INTERVAL
.
void setMaxRetryInterval(long maxRetryInterval)
maxRetryInterval
- maximum retry interval to apply in the case a retry interval multiplier has been specifiedint getReconnectAttempts()
HornetQClient.DEFAULT_RECONNECT_ATTEMPTS
.
void setReconnectAttempts(int reconnectAttempts)
reconnectAttempts
- maximum number of attempts to retry connection in case of failureboolean isFailoverOnInitialConnection()
HornetQClient.DEFAULT_FAILOVER_ON_INITIAL_CONNECTION
.
void setFailoverOnInitialConnection(boolean failover)
failover
- boolean isFailoverOnServerShutdown()
HornetQClient.DEFAULT_FAILOVER_ON_SERVER_SHUTDOWN
.
true
if connections must failover if the server has normally shut down, else false
void setFailoverOnServerShutdown(boolean failoverOnServerShutdown)
failoverOnServerShutdown
- true
if connections must failover if the server has normally shut down, false
elseString getConnectionLoadBalancingPolicyClassName()
void setConnectionLoadBalancingPolicyClassName(String loadBalancingPolicyClassName)
ConnectionLoadBalancingPolicy
.
loadBalancingPolicyClassName
- class name of the connection load balancing policyint getInitialMessagePacketSize()
HornetQClient.DEFAULT_INITIAL_MESSAGE_PACKET_SIZE
.
void setInitialMessagePacketSize(int size)
size
- initial size of messages created through this factory.void addInterceptor(Interceptor interceptor)
interceptor
- an Interceptorboolean removeInterceptor(Interceptor interceptor)
interceptor
- interceptor to remove
true
if the interceptor is removed from this factory, false
elsevoid close()
ClientSessionFactory copy()
|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |


Class: Aws::SNS::Types::SubscribeInput
| Relationships & Source Files | |
| Super Chains via Extension / Inclusion / Inheritance | |
|
Class Chain:
self,
Struct
|
|
|
Instance Chain:
self,
::Aws::Structure ,
Struct
|
|
| Inherits: |
Struct
|
| Defined in: | gems/aws-sdk-sns/lib/aws-sdk-sns/types.rb |
Overview
Input for Subscribe action.
Constant Summary
Instance Attribute Summary
-
#attributes ⇒ Hash<String,String>
rw
A map of attributes with their corresponding values.
-
#endpoint ⇒ String
rw
The endpoint that you want to receive notifications.
-
#protocol ⇒ String
rw
The protocol that you want to use.
-
#return_subscription_arn ⇒ Boolean
rw
Sets whether the response from the
Subscribe
request includes the subscription::Aws::ARN
, even if the subscription is not yet confirmed. -
#topic_arn ⇒ String
rw
The ARN of the topic you want to subscribe to.
Instance Method Summary
::Aws::Structure
- Included
| #to_hash | Alias for Aws::Structure#to_h. |
Instance Attribute Details
#attributes ⇒ Hash
<String
,String
> (rw)
A map of attributes with their corresponding values.
The following lists the names, descriptions, and values of the
special request parameters that the Subscribe
action uses:
DeliveryPolicy
– The policy that defines how Amazon SNS retries failed deliveries to HTTP/S endpoints.FilterPolicy
– The simple JSON object that lets your subscriber receive only a subset of messages, rather than receiving every message published to the topic.FilterPolicyScope
– This attribute lets you choose the filtering scope by using one of the following string value types:MessageAttributes
(default) – The filter is applied on the message attributes.MessageBody
– The filter is applied on the message body.
RawMessageDelivery
– When set totrue
, enables raw message delivery to Amazon SQS or HTTP/S endpoints. This eliminates the need for the endpoints to process JSON formatting, which is otherwise created for Amazon SNS metadata.RedrivePolicy
– When specified, sends undeliverable messages to the specified Amazon SQS dead-letter queue. Messages that can't be delivered due to client errors (for example, when the subscribed endpoint is unreachable) or server errors (for example, when the service that powers the subscribed endpoint becomes unavailable) are held in the dead-letter queue for further analysis or reprocessing.
The following attribute applies only to Amazon Kinesis Data Firehose delivery stream subscriptions:
SubscriptionRoleArn
– The ARN of the::Aws::IAM
role that has the following:- Permission to write to the Kinesis Data Firehose delivery stream
- Amazon SNS listed as a trusted entity
Specifying a valid ARN for this attribute is required for Kinesis Data Firehose delivery stream subscriptions. For more information, see Fanout to Kinesis Data Firehose delivery streams in the Amazon SNS Developer Guide.
#endpoint ⇒ String
(rw)
The endpoint that you want to receive notifications. ::Aws::SNS::Endpoints
vary
by protocol:
For the
http
protocol, the (public) endpoint is a URL beginning withhttp://
.For the
https
protocol, the (public) endpoint is a URL beginning withhttps://
.For the
email
protocol, the endpoint is an email address.For the
email-json
protocol, the endpoint is an email address.For the
sms
protocol, the endpoint is a phone number of an SMS-enabled device.For the
sqs
protocol, the endpoint is the::Aws::ARN
of an Amazon SQS queue.For the
application
protocol, the endpoint is the EndpointArn of a mobile app and device.For the
lambda
protocol, the endpoint is the::Aws::ARN
of an::Aws::Lambda
function.For the
firehose
protocol, the endpoint is the::Aws::ARN
of an Amazon Kinesis Data Firehose delivery stream.
# File 'gems/aws-sdk-sns/lib/aws-sdk-sns/types.rb', line 2750
class SubscribeInput < Struct.new( :topic_arn, :protocol, :endpoint, :attributes, :return_subscription_arn) SENSITIVE = [] include Aws::Structure end
#protocol ⇒ String
(rw)
The protocol that you want to use. Supported protocols include:
http
– delivery of JSON-encoded message via HTTP POSThttps
– delivery of JSON-encoded message via HTTPS POSTemail
– delivery of message via SMTPemail-json
– delivery of JSON-encoded message via SMTPsms
– delivery of message via::Aws::SMS
sqs
– delivery of JSON-encoded message to an Amazon SQS queueapplication
– delivery of JSON-encoded message to an EndpointArn for a mobile app and devicelambda
– delivery of JSON-encoded message to an::Aws::Lambda
functionfirehose
– delivery of JSON-encoded message to an Amazon Kinesis Data Firehose delivery stream.
# File 'gems/aws-sdk-sns/lib/aws-sdk-sns/types.rb', line 2750
class SubscribeInput < Struct.new( :topic_arn, :protocol, :endpoint, :attributes, :return_subscription_arn) SENSITIVE = [] include Aws::Structure end
#return_subscription_arn ⇒ Boolean
(rw)
Sets whether the response from the Subscribe
request includes the
subscription ::Aws::ARN
, even if the subscription is not yet confirmed.
If you set this parameter to true
, the response includes the ::Aws::ARN
in all cases, even if the subscription is not yet confirmed. In
addition to the ::Aws::ARN
for confirmed subscriptions, the response also
includes the pending subscription
::Aws::ARN
value for subscriptions that
aren't yet confirmed. A subscription becomes confirmed when the
subscriber calls the ConfirmSubscription
action with a
confirmation token.
The default value is false
.
#topic_arn ⇒ String
(rw)
The ARN of the topic you want to subscribe to.
# File 'gems/aws-sdk-sns/lib/aws-sdk-sns/types.rb', line 2750
class SubscribeInput < Struct.new( :topic_arn, :protocol, :endpoint, :attributes, :return_subscription_arn) SENSITIVE = [] include Aws::Structure end


---
layout: talk_reveal3
title: Where we stand with the COVID-19 pandemic and case-based solutions
venue: Congressman Heck Town Hall
author: Trevor Bedford
---
{{ page.title }}
Trevor Bedford (@trvrb)
Associate Professor
Fred Hutch
{{ page.date | date: "%-d %b %Y" }}
{{ page.event }}
{{ page.venue }}
Slides at: bedford.io/talks
Talk overview
- How we got here
- Where we are now
- How we get out here
How we got here:
Genomic overview of the COVID-19 pandemic, using viral sequencing to reconstruct
SARS-CoV-2 evolution and spread
Epidemic process
Sample some individuals
Sequence and determine phylogeny
Sequence and determine phylogeny
Dec/Jan: Emergence of SARS-CoV-2 from Wuhan in ~Nov 2019
Jan/Feb: Spread within China and seeding elsewhere
Feb/Mar: Epidemic spread within North America and Europe
Mar/Apr: Continued growth, but decreasing transmission with social distancing measures
Epidemic in the USA was introduced from China in late Jan and from Europe during Feb
Once in the US, virus spread rapidly
Where we are now:
Slow decline of detected cases, but continued transmission
With social distancing we've seen substantial drops in transmission, but not suppression
Transmission is heterogeneous across the US
My numbers
- Currently ~20,000 cases reported per day with 5-10X underreporting, this is likely ~100k infections per day and ~2M active infections
- NYC may have 20-30% seropositivity at this point, I'd guess ~5% nationally
- Herd immunity likely requires at least 60% recovered
- Infection-to-fatality ratio in general population of 0.5% to 1.0%
How we get out of here:
Case-based interventions to mitigate spread
Moving forward
- Suppression has failed
- Facing a long period of localized flare-ups and societal responses
- Recommend strategies to mitigate spread while keeping economy functioning
- Scalable case-based interventions (testing, contact tracing and isolation)
- Non-disruptive distancing and hygiene
Example transmission chain and intervention
Example transmission chain and intervention
Acknowledgements
Genomic epi: Data producers from all over the world, GISAID, Virological.org and the Nextstrain team


Current Temperature:
Current Humidity:
Today's low:
Today's High:
Current Pressure:
Current Wind Speed:
Today's Sunrise:
Today's Sunset:


Tutorial 4 - Cloud Workspace, Files, Projects and Orion Navigator
When going through Maqetta's tutorials, it is suggested that you have two side-by-side
browser windows open, one showing the tutorial, and the other where you run the application
and perform the steps listed in the tutorial.
This tutorial provides an overview of the features in Maqetta having to do
with your cloud workspace. Topics covered:
- The Files palette
- Creating Files
- Opening Files from the Files Palette
- Files Palette Context Menu
- Files Palette Toolbar
- Creating and Switching Projects
- Orion Navigator
Files Palette
- ⇒
Open up the Files palette (found in the left/bottom corner of the application).
If the palette isn't showing, click on the large-size Files palette icon to show
the Files palette.
The Files palette should look something like this:
What you are seeing is your personal cloud workspace.
Maqetta creates a default project (project1) for each new user,
and puts a set of default files in the newly created project:
app.css -
This file is the default location for project-level CSS style rules.
Maqetta includes app.css in all of the HTML files it creates.
Some of the advanced features found in Maqetta's various properties palettes
(found at the right/top of the application, such as Layout, Margins, etc)
will automatically add CSS style rules to this file. You can also double-click
on this file to bring up Maqetta's source editor so that you can add
CSS style rules manually.
app.js -
This file is the default location for project-level JavaScript logic.
Maqetta includes app.js in all of the HTML files it creates.
Beginning users typically do not touch this file, but advanced users
often find the need to put custom JavaScript logic in this file.
- lib -
Holds the JavaScript libraries (e.g., Dojo) that will
be used by the HTML files you create.
- samples -
Contains various sample files, including various files that are
used as part of Maqetta's tutorials.
- themes -
Contains various CSS themes, both the ones that ship standard
with Maqetta, and user-created themes.
Creating Files
- ⇒
Go to the Create menu
at the top of the application.
Choose the command Create -> Desktop Application....
In the dialog that appears, accept the defaults and click on the "Create" button.
- ⇒
Go to the Palette and find the section labelled "Containers".
Click on the "Containers" section to show its contents, and then click on the
"Dojo" sub-section to show its contents.
- ⇒
You should see various widget icons. Find the TabContainer widget.
With the mouse, drag the icon for the TabContainer widget from the
Palette onto the white canvas (in the middle of the application).
Drop the TabContainer somewhere inside of the white canvas.
A TabContainer widget should appear at the top/left of the canvas,
and a popup dialog should appear. Click OK in that popup dialog to accept its default values.
Your canvas should look something like this:
Now let's look at the various parts of the Maqetta user interface. Observe the following:
- Files palette - Observe that the filename of the file you just
created (e.g., file1.html) is now listed in the Files palette.
- File tabs - Look at the file tab area at the top of the application
(just under the main menubar and just above the page editor's toolbar).
Find the file tab for the file you just created. Observe that it contains
an asterisk next to the filename
to indicate that the file has unsaved changes.
- ⇒
Click on the Save button
on the page editor toolbar to save your document.
Notice that the asterisk goes away after the save operation.
Previewing Files
- ⇒
Click on the Preview icon
on the page editor toolbar.
Notice that a new browser tab (or window) opens showing the TabContainer widget.
(In Maqetta, this is called "Preview in browser".)
- ⇒
In the browser tab that just opened, select the full URL from the browser's URL address bar,
and issue a system copy command (e.g., Ctrl-C on Windows or Cmd-C on Mac) to put the URL
onto the system clipboard.
- ⇒
Open a different browser (if you have multiple browsers on your system),
open up a new browser tab in that browser, and issue a paste command into that
browser's URL bar. You should see your file previewed in the other browser.
What this shows is that each of your files in your cloud workspace has its own URL
that you can share with others (assuming your colleagues also can
access the Maqetta server).
- ⇒
Click on the file tab's close button -
- to close the page editor.
Opening Files from the Files Palette
- ⇒
Go to the Files palette and double-click on the file you just
created to reopen that file.
When you double-click on an HTML file in the Files palette,
Maqetta opens in the visual page editor.
- ⇒
In the Files palette, double-click on the app.css file.
Maqetta will open up a source editor where you can edit the source code of that CSS file.
- ⇒
Now, double-click on the app.js file.
Maqetta will open up a source editor where you can edit the source code of that JavaScript file.
When you double-click on CSS (*.css), JavaScript (*.js) or JSON file (*.json)
in the Files palette,
Maqetta opens up a source editor for the given file.
- ⇒
For each of the open files, click on the file tab's close button -
- to close all of the editors.
Files Palette Context Menu
In the Files palette, you can create folders, delete files, rename files,
upload files, and download files.
- ⇒
Go to the Files palette, put the mouse over the
app.css file, and bring up the context menu
(e.g., using right-mouse-button or Ctrl-click on a Mac). You should see the following
commands in the popup menu.
- New folder... - Adds a new folder to your cloud workspace.
- Upload files... - Allows you to upload files from your computer
to your cloud workspace.
- Rename... - Allows you to rename files.
- Delete - Allows you to delete files.
- Download - Allows you to download selected files.
- ⇒
Go to the Files palette, put the mouse over the
app.css file, bring up the context menu, and choose
"New Folder...".
- ⇒
The Create New Folder dialog will appear. Accept the default values and click on the "Create button".
A new folder with an automatically generated name (e.g., "folder1") will appear in the Files palette.
- ⇒
In the Files palette, put the mouse over the folder you just created
(e.g., "folder1"),
bring up the context menu, and choose the "Rename..." command.
Enter "images" as the new name for the folder, and click on the Rename button.
Notice in the Files palette that the folder has been renamed
to "images".
- ⇒
In the Files palette, put the mouse over the "images"
folder, bring up the context menu,
and once again choose the "New Folder..." command. In the Create New Folder
dialog, type "abc" into the folder name textbox, then click on the Create button.
Note that new folder "abc" is now a child of folder "images".
- ⇒
In the Files palette, put the mouse over the "abc" folder,
bring up the context menu, and choose the "Delete..." command. An "Are you sure"
dialog will appear. Click OK. Notice that folder "abc" has been removed from the Files palette.
- ⇒
Outside of Maqetta, find one or more image files on your computer (preferably, not massive).
Back in Maqetta, put the mouse over the "images" folder, bring up the context menu,
and choose the "Upload..." command. The Upload Files dialog will apepar.
- ⇒
Outside of Maqetta, find one or more image files on your computer (preferably, not massive).
Back in Maqetta, put the mouse over the "images" folder, bring up the context menu,
and choose the "Upload..." command. The Upload Files dialog will appear.
- ⇒
In the dialog, click on the "Select Files" button to bring up a file selection dialog.
In the file selection dialog, choose one or more image files from your computer,
and click on the "OK or "Open" button. The files you selected will now appear in the
Upload Files dialog.
- ⇒
Click on the Upload button to upload the files to your workspace.
Look in the Files palette and you will see the files you just uploaded.
You can click on the "Select Files" command again if you want to upload more files.
- ⇒
Click on the close box at the top/right of the dialog or click on "Cancel"
to close the Upload Files dialog.
- ⇒
In the Files palette, put the mouse over the "images" folder,
bring up the context menu, and choose the "Download" command.
The Download dialog will appear.
- ⇒
The Download dialog will provide a default file name for a ZIP file
that will hold the currently selected files (e.g., project1.zip),
and it will show the list of files you have selected
(in this case, "images"). Click on the Download button.
File project1.zip will now be in your browser's Downloads folder.
The ZIP file will contain the full contents of your "images" folder.
- ⇒
In the Files palette, put the mouse over the "images" folder,
bring up the context menu, and choose the "Delete..." command. An "Are you sure"
dialog will appear. Click OK. Notice that folder "images" has been removed from the Files palette.
Files Palette Toolbar
The Files palette has a toolbar with 3 icons:
.
The three icons are:
- Download entire project -
This command will download the full contents of your current project within a ZIP file.
You can take the contents of the ZIP file for your project and unzip into the
htdocs, public_html or www folder within a web server,
and you will have deployed your Maqetta-created sketch or prototype on that web server.
Assuming you accept the default download options,
the ZIP file will contain all of the files needed to successfully view your
creation, including necessary JavaScript libraries and CSS themes.
- Download selected files -
This icon will create a ZIP file that only contains the files that
are currently selected in the Files palette.
This icon is equivalent to the Download command on the Files palette context menu.
- Modify libraries -
This icon allows you to move your JavaScript libraries to different locations within
your current project. By default, JavaScript libraries are located in your
libs
folder. The typical reason for moving your JavaScript libraries is if your development team
requests that you send them prototypes where the JavaScript libaries are in a particular location.
Note that Maqetta will do its best to update all references to JavaScript libaries
in your HTML files so that the HTML files will continue to work properly after
the JavaScript libraries have been moved.
Creating and Switching Projects
When a user launches Maqetta for the first time, Maqetta creates a default project (named "project1").
Maqetta includes a Create -> New Project command that allows users
to create whole new projects.
- ⇒
Go to the Create menu
at the top of the application.
Choose the command Create -> Project....
In the dialog that appears, enter "temp1" as the name of the new project,
and click the "Create button".
- ⇒
The Maqetta browser window will now redraw.
Go to the Files palette, and you will see that
the project name (listed at the top of the Files palette) is now "temp1".
Also note that the Files palette contents shows the same
default contents (app.css, app.js, libs, samples, themes) as when you first launched
the Maqetta application.
The Create -> Project... command is useful if you are using
Maqetta for different work projects, or if you find the need to restart work
from scratch.
- ⇒
Let's now delete the "temp1" project. At the top of the Files palette,
click on the Delete Project icon
.
After deleting this project, Maqetta will switch back to one of your other existing
projects (e.g., "project1").
The Maqetta browser window will now redraw, and the Files palette
will show the contents of the "project1" project.
- ⇒
Using the drop-down menu at the top of the Files palette,
switch back to the "temp1" project.
Let's now delete the "temp1" project. At the top of the Files palette,
click on the Delete Project icon
.
After deleting this project, Maqetta will switch back to one of your other existing
projects (e.g., "project1").
The current release of the Maqetta application does not provide a quick and easy way
to transfer or copy files from one project to another. One possible strategy
to transfer files is to switch to the project that has your old files,
download selected files as a ZIP onto your local file system, expand the ZIP into a folder on your local file system,
switch to your new project in Maqetta, and then upload files into your new project.
Note that you have to be careful to upload files into the same locations in the new project
as they were in the old project for the relative URL references in your HTML files to work properly.
Orion Navigator
Maqetta embeds a version of Eclipse Orion,
which is an open source platform for cloud-based web development. With Orion,
you can edit source files stored in cloud workspaces directly in the browser.
Maqetta includes Orion inside so that Maqetta users can take advantage of Orion's
various features, including its source editor technology that runs in the browser.
- ⇒
In Maqetta, make sure all files are closed.
For each of the open files, click on the file tab's close button -
- to close all of the editors.
- ⇒
Go to the Open menu
at the top of the application.
Choose the command Open -> Orion Navigator.
A new browser tab/window will open that is running Eclipse Orion,
with the Orion navigator user interface showing the contents of
your personal cloud workspace.
In the Orion navigator, at the top level, you will see all of your projects.
In the picture above, there is only one project ("project1").
- ⇒
Click on the small right-pointing arrow just to the left of "project1"
to open up that folder. You should see nearly the same list of HTML, CSS, JavaScript files
and folders as the Maqetta Files palette.
The Orion Navigator will not show all of the same files as you see in the Maqetta workspace.
This is because that Maqetta injects some files and folders into user workspaces
that are read-only,
such as the samples
folders. Read-only files and folders do not appear
in the Orion Navigator.
- ⇒
Click on
file1.html
(assuming it is in your workspace due to previous steps in this tutorial).
Orion will now switch to its source editor and show the HTML contents of file1.html.
Find the line of source code that has "Tab 1" on it.

- ⇒
In the Orion source editor, change the string "Tab 1" to "Reports" (for the
title
attribute).
Then click on the Save button to save your changes.
- ⇒
Return to the Maqetta browser window. In the Files palette,
double-click on
file1.html
. On the visual editor canvas, you should
see that the first tab now says "Reports" instead of "Tab 1".
NOTE: Be very careful with source code changes. If you modify HTML, CSS or JavaScript files
using source editors, and the revised code is not valid HTML, CSS or JavaScript,
Maqetta might not be able to open your files.
- ⇒
Return to the Orion window. At the top/left, click on the hyperlink for "project1"
to return to the file navigator. You should once again see the list of files
in "project1", such as app.css, app.js and file1.html.
- ⇒
In the Orion window, click on the "New folder" button. In the type-in box,
enter "img". After completing the operation, you should see a new "img" folder in your project.
Go back to the Maqetta window. Hit browser refresh, which will cause Maqetta to restart
and update the Files palette. You should see the "img" folder in the
Maqetta Files palette.
- ⇒
Return to the Orion window. Click just to the right
(not directly on) the string "img"
to select the "img" folder. You should see an orange highlight on the "img" line to
show that it is selected.
In Orion, clicking on a file or folder name will cause Orion to open that file or folder.
Clicking to the right of a file or folder name will cause Orion to select that file or folder.
- ⇒
In the Actions menu, choose "Import local file".
You should see this dialog:
This dialog provides an alternate way for you to upload files into your Maqetta workspace.
Orion's upload feature includes various features that Maqetta's upload feature does not,
including the ability to upload a ZIP file.
- ⇒
Click on the close box (the "x") at the top/right of the Import files dialog.
This will return you to the Orion navigator.
- ⇒
Click just to the right
(not directly on) the string "file1.html"
to select that file. Press and hold on the "Actions" menu. You should see the following:
As you can see, the Orion navigator offers various useful file management features, such as
the ability to move files to different folders.
- ⇒
Click just to the right
(not directly on) the folder "img"
to select that folder. From the Actions menu, choose "Delete" to delete that file.
You'll see the "img" is no longer visible in the Orion navigator.
Go back to the Maqetta window. Hit browser refresh, which will cause Maqetta to restart
and update the Files palette. You should see that the "img" folder is no longer visible
in the Maqetta Files palette.
- ⇒
Close the browser tab containing the Orion navigator.
Previous / Next