Adding Components to a Page Using HTML Tags
The tags defined by the JavaServer Faces standard HTML tag library represent HTML form components and other basic HTML elements. These components display data or accept data from the user. This data is collected as part of a form and is submitted to the server, usually when the user clicks a button. This section explains how to use each of the component tags shown in Table 7-1.
The next section explains the important tag attributes that are common to most component tags. For each of the components discussed in the following sections, Writing Bean Properties explains how to write a bean property bound to a particular component or its value.
Common Component Tag Attributes
Most of the component tags support the attributes shown in Table 7-2.
Attribute |
Description |
|---|---|
Identifies a bean property and binds the component instance to it. |
|
Uniquely identifies the component. |
|
If set to true, indicates that any events, validation, and conversion associated with the component should happen when request parameter values are applied, |
|
Specifies a condition under which the component should be rendered. If the condition is not satisfied, the component is not rendered. |
|
Specifies a Cascading Style Sheet (CSS) style for the tag. |
|
Specifies a CSS class that contains definitions of the styles. |
|
Specifies the value of the component, in the form of a value expression. |
All the tag attributes (except id) can accept expressions, as defined by the EL, described in Chapter 6, Expression Language.
The id Attribute
The id attribute is not usually required for a component tag but is used when another component or a server-side class must refer to the component. If you don’t include an id attribute, the JavaServer Faces implementation automatically generates a component ID. Unlike most other JavaServer Faces tag attributes, the id attribute takes expressions using only the evaluation syntax described in The immediate Attribute, which uses the ${} delimiters. For more information on expression syntax, see Value Expressions.
The immediate Attribute
Input components and command components (those that implement the ActionSource interface, such as buttons and hyperlinks) can set the immediate attribute to true to force events, validations, and conversions to be processed when request parameter values are applied.
You need to carefully consider how the combination of an input component’s immediate value and a command component’s immediate value determines what happens when the command component is activated.
Assume that you have a page with a button and a field for entering the quantity of a book in a shopping cart. If the immediate attributes of both the button and the field are set to true, the new value entered in the field will be available for any processing associated with the event that is generated when the button is clicked. The event associated with the button as well as the events, validation, and conversion associated with the field are all handled when request parameter values are applied.
If the button’s immediate attribute is set to true but the field’s immediate attribute is set to false, the event associated with the button is processed without updating the field’s local value to the model layer. The reason is that any events, conversion, or validation associated with the field occurs after request parameter values are applied.
The bookshowcart.xhtml page of the Duke's Bookstore case study has examples of components using the immediate attribute to control which component's data is updated when certain buttons are clicked. The quantity field for each book does not set the immediate attribute, so the value is false (the default).
<h:inputText id="quantity" size="4" value="#{item.quantity}" title="#{bundle.ItemQuantity}"> <f:validateLongRange minimum="1"/> </h:inputText>
The immediate attribute of the Continue Shopping hyperlink is set to true, while the immediate attribute of the Update Quantities hyperlink is set to false:
<h:commandLink id="continue" action="bookcatalog" immediate="true"> <h:outputText value="#{bundle.ContinueShopping}"/> </h:commandLink> ... <h:commandLink id="update" action="#{showcart.update}" immediate="false"> <h:outputText value="#{bundle.UpdateQuantities}"/> </h:commandLink>
If you click the Continue Shopping hyperlink, none of the changes entered into the quantity input fields will be processed. If you click the Update Quantities hyperlink, the values in the quantity fields will be updated in the shopping cart.
The rendered Attribute
A component tag uses a Boolean EL expression along with the rendered attribute to determine whether the component will be rendered. For example, the commandLink component in the following section of a page is not rendered if the cart contains no items:
<h:commandLink id="check" ... rendered="#{cart.numberOfItems > 0}"> <h:outputText value="#{bundle.CartCheck}"/> </h:commandLink>
Unlike nearly every other JavaServer Faces tag attribute, the rendered attribute is restricted to using rvalue expressions. As explained in Value and Method Expressions, these rvalue expressions can only read data; they cannot write the data back to the data source. Therefore, expressions used with rendered attributes can use the arithmetic operators and literals that rvalue expressions can use but lvalue expressions cannot use. For example, the expression in the preceding example uses the > operator.
Note - In this example and others, bundle refers to a java.util.ResourceBundle file that contains locale-specific strings to be displayed. Resource bundles are discussed in Chapter 17, Internationalizing and Localizing Web Applications.
The style and styleClass Attributes
The style and styleClass attributes allow you to specify CSS styles for the rendered output of your tags. Displaying Error Messages with the h:message and h:messages Tags describes an example of using the style attribute to specify styles directly in the attribute. A component tag can instead refer to a CSS class.
The following example shows the use of a dataTable tag that references the style class list-background:
<h:dataTable id="items" ... styleClass="list-background" value="#{cart.items}" var="book">
The style sheet that defines this class is stylesheet.css, which will be included in the application. For more information on defining styles, see Cascading Style Sheets Specification at http://www.w3.org/Style/CSS/.
The value and binding Attributes
A tag representing an output component uses the value and binding attributes to bind its component’s value or instance, respectively, to a data object.
Adding HTML Head and Body Tags
The HTML head (h:head) and body (h:body) tags add HTML page structure to JavaServer Faces web pages.
The h:head tag represents the head element of an HTML page
The h:body tag represents the body element of an HTML page
The following is an example of an XHTML page using the usual head and body markup tags:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>Add a title</title> </head> <body> Add Content </body> </html>
The following is an example of an XHTML page using h:head and h:body tags:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://java.sun.com/jsf/html"> <h:head> Add a title </h:head> <h:body> Add Content </h:body> </html>
Both of the preceding example code segments render the same HTML elements. The head and body tags are useful mainly for resource relocation. For more information on resource relocation, see Resource Relocation Using h:outputScript and h:outputStylesheet Tags.
Adding a Form Component
An h:form tag represents an input form, which includes child components that can contain data that is either presented to the user or submitted with the form.
Figure 7-1 shows a typical login form in which a user enters a user name and password, then submits the form by clicking the Login button.
The h:form tag represents the form on the page and encloses all the components that display or collect data from the user, as shown here:
<h:form> ... other JavaServer Faces tags and other content... </h:form>
The h:form tag can also include HTML markup to lay out the components on the page. Note that the h:form tag itself does not perform any layout; its purpose is to collect data and to declare attributes that can be used by other components in the form.
A page can include multiple h:form tags, but only the values from the form submitted by the user will be included in the postback request.
Using Text Components
Text components allow users to view and edit text in web applications. The basic types of text components are as follows:
Label, which displays read-only text
Text field, which allows users to enter text, often to be submitted as part of a form
Text area, which is a type of text field that allows users to enter multiple lines of text
Password field, which is a type of text field that displays a set of characters, such as asterisks, instead of the password text that the user enters
Figure 7-2 shows examples of these text components.
Text components can be categorized as either input or output. A JavaServer Faces output component is rendered as read-only text. An example is a label. A JavaServer Faces input component is rendered as editable text. An example is a text field.
The input and output components can each be rendered in various ways to display more specialized text.
Table 7-3 lists the tags that represent the input components.
Tag |
Function |
|---|---|
Allows a page author to include a hidden variable in a page |
|
The standard password field: accepts one line of text with no spaces and displays it as a set of asterisks as it is typed |
|
The standard text field: accepts a one-line text string |
|
The standard text area: accepts multiple lines of text |
The input tags support the tag attributes shown in Table 7-4 in addition to those described in Common Component Tag Attributes. Note that this table does not include all the attributes supported by the input tags but just those that are used most often. For the complete list of attributes, refer to the documentation at http://docs.oracle.com/javaee/6/javaserverfaces/2.1/docs/vdldocs/facelets/.
Attribute |
Description |
|---|---|
Identifies a converter that will be used to convert the component’s local data. See Using the Standard Converters for more information on how to use this attribute. |
|
converterMessage |
Specifies an error message to display when the converter registered on the component fails. |
dir |
Specifies the direction of the text displayed by this component. Acceptable values are LTR, meaning left-to-right, and RTL, meaning right-to-left. |
label |
Specifies a name that can be used to identify this component in error messages. |
lang |
Specifies the code for the language used in the rendered markup, such as en_US. |
required |
Takes a boolean value that indicates whether the user must enter a value in this component. |
requiredMessage |
Specifies an error message to display when the user does not enter a value into the component. |
Identifies a method expression pointing to a managed bean method that performs validation on the component’s data. See Referencing a Method That Performs Validation for an example of using the f:validator tag. |
|
validatorMessage |
Specifies an error message to display when the validator registered on the component fails to validate the component’s local value. |
Identifies a method expression that points to a managed bean method that handles the event of entering a value in this component. See Referencing a Method That Handles a Value-Change Event for an example of using valueChangeListener. |
Table 7-5 lists the tags that represent the output components.
Tag |
Function |
|---|---|
Displays a localized message |
|
The standard read-only label: displays a component as a label for a specified input field |
|
Displays an <a href> tag that links to another page without generating an action event |
|
Displays a one-line text string |
The output tags support the converter tag attribute in addition to those listed in Common Component Tag Attributes.
The rest of this section explains how to use some of the tags listed in Table 7-3 and Table 7-5. The other tags are written in a similar way.
Rendering a Text Field with the h:inputText Tag
The h:inputText tag is used to display a text field. A similar tag, the h:outputText tag, displays a read-only, single-line string. This section shows you how to use the h:inputText tag. The h:outputText tag is written in a similar way.
Here is an example of an h:inputText tag:
<h:inputText id="name" label="Customer Name" size="50" value="#{cashier.name}" required="true" requiredMessage="#{bundle.ReqCustomerName}"> <f:valueChangeListener type="dukesbookstore.listeners.NameChanged" /> </h:inputText>
The label attribute specifies a user-friendly name that will be used in the substitution parameters of error messages displayed for this component.
The value attribute refers to the name property of a managed bean named CashierBean. This property holds the data for the name component. After the user submits the form, the value of the name property in CashierBean will be set to the text entered in the field corresponding to this tag.
The required attribute causes the page to reload, displaying errors, if the user does not enter a value in the name text field. The JavaServer Faces implementation checks whether the value of the component is null or is an empty string.
If your component must have a non-null value or a String value at least one character in length, you should add a required attribute to your tag and set its value to true. If your tag has a required attribute that is set to true and the value is null or a zero-length string, no other validators that are registered on the tag are called. If your tag does not have a required attribute set to true, other validators that are registered on the tag are called, but those validators must handle the possibility of a null or zero-length string. See Validating Null and Empty Strings for more information.
Rendering a Password Field with the h:inputSecret Tag
The h:inputSecret tag renders an <input type="password"> HTML tag. When the user types a string into this field, a row of asterisks is displayed instead of the text typed by the user. Here is an example:
<h:inputSecret redisplay="false" value="#{LoginBean.password}" />
In this example, the redisplay attribute is set to false. This will prevent the password from being displayed in a query string or in the source file of the resulting HTML page.
Rendering a Label with the h:outputLabel Tag
The h:outputLabel tag is used to attach a label to a specified input field for the purpose of making it accessible. The following page uses an h:outputLabel tag to render the label of a check box:
<h:selectBooleanCheckbox id="fanClub" binding="#{cashier.specialOffer}" /> <h:outputLabel for="fanClub" binding="#{cashier.specialOfferText}" > <h:outputText id="fanClubLabel" value="#{bundle.DukeFanClub}" /> </h:outputLabel> ...
The for attribute of the h:outputLabel tag maps to the id of the input field to which the label is attached. The h:outputText tag nested inside the h:outputLabel tag represents the label component. The value attribute on the h:outputText tag indicates the text that is displayed next to the input field.
Instead of using an h:outputText tag for the text displayed as a label, you can simply use the h:outputLabel tag’s value attribute. The following code snippet shows what the previous code snippet would look like if it used the value attribute of the h:outputLabel tag to specify the text of the label:
<h:selectBooleanCheckbox id="fanClub" binding="#{cashier.specialOffer}" /> <h:outputLabel for="fanClub" binding="#{cashier.specialOfferText}" value="#{bundle.DukeFanClub}" /> </h:outputLabel> ...
Rendering a Hyperlink with the h:outputLink Tag
The h:outputLink tag is used to render a hyperlink that, when clicked, loads another page but does not generate an action event. You should use this tag instead of the h:commandLink tag if you always want the URL specified by the h:outputLink tag’s value attribute to open and do not want any processing to be performed when the user clicks the link. Here is an example:
<h:outputLink value="javadocs"> Documentation for this demo </h:outputLink>
The text in the body of the h:outputLink tag identifies the text that the user clicks to get to the next page.
Displaying a Formatted Message with the h:outputFormat Tag
The h:outputFormat tag allows display of concatenated messages as a MessageFormat pattern, as described in the API documentation for java.text.MessageFormat. Here is an example of an h:outputFormat tag:
<h:outputFormat value="Hello, {0}!"> <f:param value="#{hello.name}"/> </h:outputFormat>
The value attribute specifies the MessageFormat pattern. The f:param tag specifies the substitution parameters for the message. The value of the parameter replaces the {0} in the sentence. If the value of "#{hello.name}" is “Bill”, the message displayed in the page is as follows:
Hello, Bill!
An h:outputFormat tag can include more than one f:param tag for those messages that have more than one parameter that must be concatenated into the message. If you have more than one parameter for one message, make sure that you put the f:param tags in the proper order so that the data is inserted in the correct place in the message. Here is the preceding example modified with an additional parameter:
<h:outputFormat value="Hello, {0}! You are visitor number {1} to the page."> <f:param value="#{hello.name}" /> <f:param value="#{bean.numVisitor}"/> </h:outputFormat>
The value of {1} is replaced by the second parameter. The parameter is an EL expression, bean.numVisitor, where the property numVisitor of the managed bean bean keeps track of visitors to the page. This is an example of a value-expression-enabled tag attribute accepting an EL expression. The message displayed in the page is now as follows:
Hello, Bill! You are visitor number 10 to the page.
Using Command Component Tags for Performing Actions and Navigation
In JavaServer Faces applications, the button and hyperlink component tags are used to perform actions, such as submitting a form, and for navigating to another page. These tags are called command component tags because they perform an action when activated.
The h:commandButton tag is rendered as a button. The h:commandLink tag is rendered as a hyperlink.
In addition to the tag attributes listed in Common Component Tag Attributes, the h:commandButton and h:commandLink tags can use the following attributes:
action, which is either a logical outcome String or a method expression pointing to a bean method that returns a logical outcome String. In either case, the logical outcome String is used to determine what page to access when the command component tag is activated.
actionListener, which is a method expression pointing to a bean method that processes an action event fired by the command component tag.
See Referencing a Method That Performs Navigation for more information on using the action attribute. See Referencing a Method That Handles an Action Event for details on using the actionListener attribute.
Rendering a Button with the h:commandButton Tag
If you are using an h:commandButton component tag, the data from the current page is processed when a user clicks the button, and the next page is opened. Here is an example of the h:commandButton tag:
<h:commandButton value="Submit" action="#{cashierBean.submit}"/>
Clicking the button will cause the submit method of CashierBean to be invoked because the action attribute references this method. The submit method performs some processing and returns a logical outcome.
The value attribute of the example h:commandButton tag references the button’s label. For information on how to use the action attribute, see Referencing a Method That Performs Navigation.
Rendering a Hyperlink with the h:commandLink Tag
The h:commandLink tag represents an HTML hyperlink and is rendered as an HTML <a> element.
A h:commandLink tag must include a nested h:outputText tag, which represents the text that the user clicks to generate the event. Here is an example:
<h:commandLink id="Duke" action="bookstore"> <f:actionListener type="dukesbookstore.listeners.LinkBookChangeListener" /> <h:outputText value="#{bundle.Book201}"/> /h:commandLink>
This tag will render the following HTML:
<a id="_idt16:Duke" href="#" onclick="mojarra.jsfcljs(document.getElementById('j_idt16'), {'j_idt16:Duke':'j_idt16:Duke'},''); return false;">My Early Years: Growing Up on Star7, by Duke</a>
Note - The h:commandLink tag will render JavaScript scripting language. If you use this tag, make sure that your browser is enabled for JavaScript technology.
Adding Graphics and Images with the h:graphicImage Tag
In a JavaServer Faces application, use the h:graphicImage tag to render an image on a page:
<h:graphicImage id="mapImage" url="/resources/images/book_all.jpg"/>
In this example, the url attribute specifies the path to the image. The URL of the example tag begins with a slash (/), which adds the relative context path of the web application to the beginning of the path to the image.
Alternatively, you can use the facility described in Web Resources to point to the image location. Here are two examples:
<h:graphicImage id="mapImage" name="book_all.jpg" library="images" alt="#{bundle.ChooseBook}" usemap="#bookMap" />
<h:graphicImage value="#{resource['images:wave.med.gif']}"/>
You can use similar syntax to refer to an image in a style sheet. The following syntax in a style sheet specifies that the image is to be found at resources/img/top-background.jpg:
header { position: relative; height: 150px; background: #fff url(#{resource['img:top-background.jpg']}) repeat-x; ...
Laying Out Components with the h:panelGrid and h:panelGroup Tags
In a JavaServer Faces application, you use a panel as a layout container for a set of other components. A panel is rendered as an HTML table. Table 7-6 lists the tags used to create panels.
Tag |
Attributes |
Function |
|---|---|---|
h:panelGrid |
columns,columnClasses, footerClass, headerClass, panelClass, rowClasses |
Displays a table |
h:panelGroup |
layout |
Groups a set of components under one parent |
The h:panelGrid tag is used to represent an entire table. The h:panelGroup tag is used to represent rows in a table. Other tags are used to represent individual cells in the rows.
The columns attribute defines how to group the data in the table and therefore is required if you want your table to have more than one column. The h:panelGrid tag also has a set of optional attributes that specify CSS classes: columnClasses, footerClass, headerClass, panelClass, and rowClasses.
If the headerClass attribute value is specified, the h:panelGrid tag must have a header as its first child. Similarly, if a footerClass attribute value is specified, the h:panelGrid tag must have a footer as its last child.
Here is an example:
<h:panelGrid columns="2" headerClass="list-header" rowClasses="list-row-even, list-row-odd" styleClass="list-background" summary="#{bundle.CustomerInfo}" title="#{bundle.Checkout}"> <f:facet name="header"> <h:outputText value="#{bundle.Checkout}"/> </f:facet> <h:outputLabel for="name" value="#{bundle.Name}" /> <h:inputText id="name" size="30" value="#{cashier.name}" required="true" requiredMessage="#{bundle.ReqCustomerName}"> <f:valueChangeListener type="dukesbookstore.listeners.NameChanged" /> </h:inputText> <h:message styleClass="error-message" for="name"/> <h:outputLabel for="ccno" value="#{bundle.CCNumber}"/> <h:inputText id="ccno" size="19" converterMessage="#{bundle.CreditMessage}" required="true" requiredMessage="#{bundle.ReqCreditCard}" > <f:converter converterId="ccno"/> <f:validateRegex pattern="\d{16}|\d{4} \d{4} \d{4} \d{4}|\d{4}-\d{4}-\d{4}-\d{4}" /> </h:inputText> <h:message styleClass="error-message" for="ccno"/> ... </h:panelGrid>
The preceding h:panelGrid tag is rendered as a table that contains components in which a customer inputs personal information. This h:panelGrid tag uses style sheet classes to format the table. The following code shows the list-header definition:
.list-header { background-color: #ffffff; color: #000000; text-align: center; }
Because the h:panelGrid tag specifies a headerClass, the h:panelGrid tag must contain a header. The example h:panelGrid tag uses an f:facet tag for the header. Facets can have only one child, so an h:panelGroup tag is needed if you want to group more than one component within an f:facet. The example h:panelGrid tag has only one cell of data, so an h:panelGroup tag is not needed.
The h:panelGroup tag has an attribute, layout, in addition to those listed in Common Component Tag Attributes. If the layout attribute has the value block, an HTML div element is rendered to enclose the row; otherwise, an HTML span element is rendered to enclose the row. If you are specifying styles for the h:panelGroup tag, you should set the layout attribute to block in order for the styles to be applied to the components within the h:panelGroup tag. You should do this because styles, such as those that set width and height, are not applied to inline elements, which is how content enclosed by the span element is defined.
An h:panelGroup tag can also be used to encapsulate a nested tree of components so that the tree of components appears as a single component to the parent component.
Data, represented by the nested tags, is grouped into rows according to the value of the columns attribute of the h:panelGrid tag. The columns attribute in the example is set to 2, and therefore the table will have two columns. The column in which each component is displayed is determined by the order in which the component is listed on the page modulo 2. So, if a component is the fifth one in the list of components, that component will be in the 5 modulo 2 column, or column 1.
Displaying Components for Selecting One Value
Another commonly used component is one that allows a user to select one value, whether it is the only value available or one of a set of choices. The most common tags for this kind of component are as follows:
An h:selectBooleanCheckbox tag, displayed as a check box, which represents a Boolean state
An h:selectOneRadio tag, displayed as a set of radio buttons
An h:selectOneMenu tag, displayed as a drop-down menu, with a scrollable list
An h:selectOneListbox tag, displayed as a list box, with an unscrollable list
Figure 7-3 shows examples of these components.
Displaying a Check Box Using the h:selectBooleanCheckbox Tag
The h:selectBooleanCheckbox tag is the only tag that JavaServer Faces technology provides for representing a Boolean state.
Here is an example that shows how to use the h:selectBooleanCheckbox tag:
<h:selectBooleanCheckbox id="fanClub" rendered="false" binding="#{cashier.specialOffer}" /> <h:outputLabel for="fanClub" rendered="false" binding="#{cashier.specialOfferText}"> <h:outputText id="fanClubLabel" value="#{bundle.DukeFanClub}" /> </h:outputLabel>
This example tag displays a check box to allow users to indicate whether they want to join the Duke Fan Club. The label for the check box is rendered by the h:outputLabel tag. The text is represented by the nested h:outputText tag.
Displaying a Menu Using the h:selectOneMenu Tag
A component that allows the user to select one value from a set of values can be rendered as a list box, a set of radio buttons, or a menu. This section describes the h:selectOneMenu tag. The h:selectOneRadio and h:selectOneListbox tags are used in a similar way. The h:selectOneListbox tag is similar to the h:selectOneMenu tag except that h:selectOneListbox defines a size attribute that determines how many of the items are displayed at once.
The h:selectOneMenu tag represents a component that contains a list of items from which a user can choose one item. This menu component is also commonly known as a drop-down list or a combo box. The following code snippet shows how the h:selectOneMenu tag is used to allow the user to select a shipping method:
<h:selectOneMenu id="shippingOption" required="true" value="#{cashier.shippingOption}"> <f:selectItem itemValue="2" itemLabel="#{bundle.QuickShip}"/> <f:selectItem itemValue="5" itemLabel="#{bundle.NormalShip}"/> <f:selectItem itemValue="7" itemLabel="#{bundle.SaverShip}"/> </h:selectOneMenu>
The value attribute of the h:selectOneMenu tag maps to the property that holds the currently selected item’s value. You are not required to provide a value for the currently selected item. If you don’t provide a value, the first item in the list is selected by default.
Like the h:selectOneRadio tag, the h:selectOneMenu tag must contain either an f:selectItems tag or a set of f:selectItem tags for representing the items in the list. Using the f:selectItem and f:selectItems Tags describes these tags.
Displaying Components for Selecting Multiple Values
In some cases, you need to allow your users to select multiple values rather than just one value from a list of choices. You can do this using one of the following component tags:
An h:selectManyCheckbox tag, displayed as a set of check boxes
Figure 7-4 shows examples of these components.
These tags allow the user to select zero or more values from a set of values. This section explains the h:selectManyCheckbox tag. The h:selectManyListbox and h:selectManyMenu tags are used in a similar way.
Unlike a menu, a list box displays a subset of items in a box; a menu displays only one item at a time when the user is not selecting the menu. The size attribute of the h:selectManyListbox tag determines the number of items displayed at one time. The list box includes a scroll bar for scrolling through any remaining items in the list.
The h:selectManyCheckbox tag renders a set of check boxes, with each check box representing one value that can be selected:
<h:selectManyCheckbox id="newslettercheckbox" layout="pageDirection" value="#{cashier.newsletters}"> <f:selectItems value="#{cashier.newsletterItems}"/> </h:selectManyCheckbox>
The value attribute of the h:selectManyCheckbox tag identifies the newsletters property of the CashierBean managed bean. This property holds the values of the currently selected items from the set of check boxes. You are not required to provide a value for the currently selected items. If you don’t provide a value, the first item in the list is selected by default. In the CashierBean managed bean, this value is instantiated to 0, so no items are selected by default.
The layout attribute indicates how the set of check boxes is arranged on the page. Because layout is set to pageDirection, the check boxes are arranged vertically. The default is lineDirection, which aligns the check boxes horizontally.
The h:selectManyCheckbox tag must also contain a tag or set of tags representing the set of check boxes. To represent a set of items, you use the f:selectItems tag. To represent each item individually, you use a f:selectItem tag. The following subsection explains these tags in more detail.
Using the f:selectItem and f:selectItems Tags
The f:selectItem and f:selectItems tags represent components that can be nested inside a component that allows you to select one or multiple items. An f:selectItem tag contains the value, label, and description of a single item. An f:selectItems tag contains the values, labels, and descriptions of the entire list of items.
You can use either a set of f:selectItem tags or a single f:selectItems tag within your component tag.
The advantages of using the f:selectItems tag are as follows.
Items can be represented by using different data structures, including Array, Map, and Collection. The value of the f:selectItems tag can represent even a generic collection of POJOs.
Different lists can be concatenated into a single component, and the lists can be grouped within the component.
Values can be generated dynamically at runtime.
The advantages of using f:selectItem are as follows:
Items in the list can be defined from the page.
Less code is needed in the bean for the f:selectItem properties.
The rest of this section shows you how to use the f:selectItems and f:selectItem tags.
Using the f:selectItems Tag
The following example from Displaying Components for Selecting Multiple Values shows how to use the h:selectManyCheckbox tag:
<h:selectManyCheckbox id="newslettercheckbox" layout="pageDirection" value="#{cashier.newsletters}"> <f:selectItems value="#{cashier.newsletterItems}"/> </h:selectManyCheckbox>
The value attribute of the f:selectItems tag is bound to the managed bean property cashier.newsletterItems. The individual SelectItem objects are created programmatically in the managed bean.
See UISelectItems Properties for information on how to write a managed bean property for one of these tags.
Using the f:selectItem Tag
The f:selectItem tag represents a single item in a list of items. Here is the example from Displaying a Menu Using the h:selectOneMenu Tag once again:
<h:selectOneMenu id="shippingOption" required="true" value="#{cashier.shippingOption}"> <f:selectItem itemValue="2" itemLabel="#{bundle.QuickShip}"/> <f:selectItem itemValue="5" itemLabel="#{bundle.NormalShip}"/> <f:selectItem itemValue="7" itemLabel="#{bundle.SaverShip}"/> </h:selectOneMenu>
The itemValue attribute represents the default value for the f:selectItem tag. The itemLabel attribute represents the String that appears in the drop-down menu component on the page.
The itemValue and itemLabel attributes are value-binding-enabled, meaning that they can use value-binding expressions to refer to values in external objects. These attributes can also define literal values, as shown in the example h:selectOneMenu tag.
Using Data-Bound Table Components
Data-bound table components display relational data in a tabular format. In a JavaServer Faces application, the h:dataTable component tag supports binding to a collection of data objects and displays the data as an HTML table. The h:column tag represents a column of data within the table, iterating over each record in the data source, which is displayed as a row. Here is an example:
<h:dataTable id="items" captionStyle="font-weight:bold" columnClasses="list-column-center, list-column-left, list-column-right, list-column-center" footerClass="list-footer" headerClass="list-header" rowClasses="list-row-even, list-row-odd" styleClass="list-background" summary="#{bundle.ShoppingCart}" value="#{cart.items}" border="1" var="item"> <h:column> <f:facet name="header"> <h:outputText value="#{bundle.ItemQuantity}" /> </f:facet> <h:inputText id="quantity" size="4" value="#{item.quantity}" title="#{bundle.ItemQuantity}"> <f:validateLongRange minimum="1"/> </h:inputText> ... </h:column> <h:column> <f:facet name="header"> <h:outputText value="#{bundle.ItemTitle}"/> </f:facet> <h:commandLink action="#{showcart.details}"> <h:outputText value="#{item.item.title}"/> </h:commandLink> </h:column> ... <f:facet name="footer" <h:panelGroup> <h:outputText value="#{bundle.Subtotal}"/> <h:outputText value="#{cart.total}" /> <f:convertNumber currencySymbol="$" type="currency" /> </h:outputText> </h:panelGroup> </f:facet> <f:facet name="caption"> <h:outputText value="#{bundle.Caption}"/> </f:facet> </h:dataTable>
The example h:dataTable tag displays the books in the shopping cart, as well as the quantity of each book in the shopping cart, the prices, and a set of buttons the user can click to remove books from the shopping cart.
The h:column tags represent columns of data in a data component. While the data component is iterating over the rows of data, it processes the column component associated with each h:column tag for each row in the table.
The h:dataTable tag shown in the preceding code example iterates through the list of books (cart.items) in the shopping cart and displays their titles, authors, and prices. Each time the h:dataTable tag iterates through the list of books, it renders one cell in each column.
The h:dataTable and h:column tags use facets to represent parts of the table that are not repeated or updated. These parts include headers, footers, and captions.
In the preceding example, h:column tags include f:facet tags for representing column headers or footers. The h:column tag allows you to control the styles of these headers and footers by supporting the headerClass and footerClass attributes. These attributes accept space-separated lists of CSS classes, which will be applied to the header and footer cells of the corresponding column in the rendered table.
Facets can have only one child, so an h:panelGroup tag is needed if you want to group more than one component within an f:facet. Because the facet tag representing the footer includes more than one tag, the h:panelGroup tag is needed to group those tags. Finally, this h:dataTable tag includes an f:facet tag with its name attribute set to caption, causing a table caption to be rendered above the table.
This table is a classic use case for a data component because the number of books might not be known to the application developer or the page author when that application is developed. The data component can dynamically adjust the number of rows of the table to accommodate the underlying data.
The value attribute of an h:dataTable tag references the data to be included in the table. This data can take the form of any of the following:
A list of beans
An array of beans
A single bean
A javax.faces.model.DataModel object
A java.sql.ResultSet object
A javax.servlet.jsp.jstl.sql.Result object
A javax.sql.RowSet object
All data sources for data components have a DataModel wrapper. Unless you explicitly construct a DataModel wrapper, the JavaServer Faces implementation will create one around data of any of the other acceptable types. See Writing Bean Properties for more information on how to write properties for use with a data component.
The var attribute specifies a name that is used by the components within the h:dataTable tag as an alias to the data referenced in the value attribute of h:dataTable.
In the example h:dataTable tag, the value attribute points to a list of books. The var attribute points to a single book in that list. As the h:dataTable tag iterates through the list, each reference to item points to the current book in the list.
The h:dataTable tag also has the ability to display only a subset of the underlying data. This feature is not shown in the preceding example. To display a subset of the data, you use the optional first and rows attributes.
The first attribute specifies the first row to be displayed. The rows attribute specifies the number of rows, starting with the first row, to be displayed. For example, if you wanted to display records 2 through 10 of the underlying data, you would set first to 2 and rows to 9. When you display a subset of the data in your pages, you might want to consider including a link or button that causes subsequent rows to display when clicked. By default, both first and rows are set to zero, and this causes all the rows of the underlying data to display.
Table 7-7 shows the optional attributes for the h:dataTable tag.
Attribute |
Defines Styles for |
|---|---|
captionClass |
Table caption |
columnClasses |
All the columns |
footerClass |
Footer |
headerClass |
Header |
rowClasses |
Rows |
styleClass |
The entire table |
Each of the attributes in Table 7-7 can specify more than one style. If columnClasses or rowClasses specifies more than one style, the styles are applied to the columns or rows in the order that the styles are listed in the attribute. For example, if columnClasses specifies styles list-column-center and list-column-right and if the table has two columns, the first column will have style list-column-center, and the second column will have style list-column-right.
If the style attribute specifies more styles than there are columns or rows, the remaining styles will be assigned to columns or rows starting from the first column or row. Similarly, if the style attribute specifies fewer styles than there are columns or rows, the remaining columns or rows will be assigned styles starting from the first style.
Displaying Error Messages with the h:message and h:messages Tags
The h:message and h:messages tags are used to display error messages when conversion or validation fails. The h:message tag displays error messages related to a specific input component, whereas the h:messages tag displays the error messages for the entire page.
Here is an example h:message tag from the guessnumber application:
<p><h:inputText id="userNo" title="Type a number from 0 to 10:" value="#{userNumberBean.userNumber}"> <f:validateLongRange minimum="#{userNumberBean.minimum}" maximum="#{userNumberBean.maximum}"/> </h:inputText> <h:commandButton id="submit" value="Submit" action="response"/> </p> <h:message showSummary="true" showDetail="false" style="color: #d20005; font-family: 'New Century Schoolbook', serif; font-style: oblique; text-decoration: overline" id="errors1" for="userNo"/>
The for attribute refers to the ID of the component that generated the error message. The error message is displayed at the same location that the h:message tag appears in the page. In this case, the error message will appear after the Submit button.
The style attribute allows you to specify the style of the text of the message. In the example in this section, the text will be a shade of red, New Century Schoolbook, serif font family, and oblique style, and a line will appear over the text. The message and messages tags support many other attributes for defining styles. For more information on these attributes, refer to the documentation at http://docs.oracle.com/javaee/6/javaserverfaces/2.1/docs/vdldocs/facelets/.
Another attribute supported by the h:messages tag is the layout attribute. Its default value is list, which indicates that the messages are displayed in a bullet list using the HTML ul and li elements. If you set the attribute value to table, the messages will be rendered in a table using the HTML table element.
The preceding example shows a standard validator that is registered on the input component. The message tag displays the error message that is associated with this validator when the validator cannot validate the input component’s value. In general, when you register a converter or validator on a component, you are queueing the error messages associated with the converter or validator on the component. The h:message and h:messages tags display the appropriate error messages that are queued on the component when the validators or converters registered on that component fail to convert or validate the component’s value.
Standard error messages are provided with standard converters and standard validators. An application architect can override these standard messages and supply error messages for custom converters and validators by registering custom error messages with the application.
Creating Bookmarkable URLs with the h:button and h:link Tags
The ability to create bookmarkable URLs refers to the ability to generate hyperlinks based on a specified navigation outcome and on component parameters.
In HTTP, most browsers by default send GET requests for URL retrieval and POST requests for data processing. The GET requests can have query parameters and can be cached, which is not advised for POST requests, which send data to the external servers. The other JavaServer Faces tags capable of generating hyperlinks use either simple GET requests, as in the case of h:outputlink, or POST requests, as in the case of h:commandLink or h:commandButton tags. GET requests with query parameters provide finer granularity to URL strings. These URLs are created with one or more name=value parameters appended to the simple URL after a ? character and separated by either &; or & strings.
To create a bookmarkable URL, use an h:link or h:button tag. Both of these tags can generate a hyperlink based on the outcome attribute of the component. For example:
<h:link outcome="response" value="Message"> <f:param name="Result" value="#{sampleBean.result}"/> </h:link>
The h:link tag will generate a URL link that points to the response.xhtml file on the same server, appended with the single query parameter created by the f:param tag. When processed, the parameter Result is assigned the value of the managed bean’s result method #{sampleBean.result}. The following sample HTML is generated from the preceding set of tags, assuming that the value of the parameter is success:
<a href="http://localhost:8080/guessnumber/response.xhtml?Result=success">Response</a>
This is a simple GET request. To create more complex GET requests and utilize the complete functionality of the h:link tag, you can use view parameters.
Using View Parameters to Configure Bookmarkable URLs
The core tags f:metadata and f:viewparam are used as a source of parameters for configuring the URLs. View parameters are declared as part of f:metadata for a page, as shown in the following example:
<h:body> <f:metadata> <f:viewParam id="name" name="Name" value="#{sampleBean.username}"/> <f:viewParam id="ID" name="uid" value="#{sampleBean.useridentity}"/> </f:metadata> <h:link outcome="response" value="Message" includeViewParams="true"/> </h:body>
View parameters are declared with the f:viewparam tag and are placed inside the f:metadata tag. If the includeViewParams attribute is set on the component, the view parameters are added to the hyperlink.
The resulting URL will look like this:
http://localhost:8080/guessnumber/response.xhtml?Name=Duke&;uid=2001
Because the URL can be the result of various parameter values, the order of the URL creation has been predefined. The order in which the various parameter values are read is as follows:
Component
Navigation-case parameters
View parameters
Resource Relocation Using h:outputScript and h:outputStylesheet Tags
Resource relocation refers to the ability of a JavaServer Faces application to specify the location where a resource can be rendered. Resource relocation can be defined with the following HTML tags:
h:outputScript
h:outputStylesheet
These tags have name and target attributes, which can be used to define the render location. For a complete list of attributes for these tags, see the documentation at http://docs.oracle.com/javaee/6/javaserverfaces/2.1/docs/vdldocs/facelets/.
For the h:outputScript tag, the name and target attributes define where the output of a resource may appear. Here is an example:
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://java.sun.com/jsf/html"> <h:head id="head"> <title>Resource Relocation</title> </h:head> <h:body id="body"> <h:form id="form"> <h:outputScript name="hello.js"/> <h:outputStylesheet name="hello.css"/> </h:form> </h:body> </html>
Since the target attribute is not defined in the tags, the style sheet hello.css is rendered in the head element of the page, and the hello.js script is rendered in the body of the page.
Here is the HTML generated by the preceding code:
<html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>Resource Relocation</title> <link type="text/css" rel="stylesheet" href="/context-root/faces/javax.faces.resource/hello.css"/> </head> <body> <form id="form" name="form" method="post" action="..." enctype="..."> <script type="text/javascript" src="/context-root/faces/javax.faces.resource/hello.js"> </script> </form> </body> </html>
If you set the target attribute for the h:outputScript tag, the incoming GET request provides the location parameter. Here is an example:
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:h="http://java.sun.com/jsf/html"> <h:head id="head"> <title>Resource Relocation</title> </h:head> <h:body id="body"> <h:form id="form"> <h:outputScript name="hello.js" target="#{param.location}"/> <h:outputStylesheet name="hello.css"/> </h:form> </h:body> </html>
In this case, if the incoming request does not provide a location parameter, the default locations will still apply: The style sheet is rendered in the head, and the script is rendered inline. However, if the incoming request specifies the location parameter as the head, both the style sheet and the script will be rendered in the head element.
The HTML generated by the preceding code is as follows:
<html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>Resource Relocation</title> <link type="text/css" rel="stylesheet" href="/context-root/faces/javax.faces.resource/hello.css"/> <script type="text/javascript" src="/context-root/faces/javax.faces.resource/hello.js"> </script> </head> <body> <form id="form" name="form" method="post" action="..." enctype="..."> </form> </body> </html>
Similarly, if the incoming request provides the location parameter as the body, the script will be rendered in the body element.
The preceding section describes simple uses for resource relocation. That feature can add even more functionality for the components and pages. A page author does not have to know the location of a resource or its placement.
By using a @ResourceDependency annotation for the components, component authors can define the resources for the component, such as a style sheet and script. This allows the page authors freedom from defining resource locations.


top
bottom
top of box
through box
down to beneath box
drop
up to beneath box
Loading...
Battery remaining:
Loading...


Don't hasitate to contact us.
Cuisine: Middle Eastern, Israeli
Meals: Breakfast, Lunch, Dinner
Open Hours: daily 10:00 - 01:00
Phone Number: +66 33 031 023
Email<EMAIL_ADDRESS>350 Soi Buakhao, 2nd Floor,
Buakhao Night Market ,
Moo 9, Pattaya 20150, Thailand


vulnerability climate agricultural coastal BBS Bangladesh adaptive change capacity ALVI districts high index land Figure area study population sensitivity low level crop vulnerable exposure region adaptation data spatial indicators {border-style Chang. Vulnerability livelihood Table px;} #ffffff;} Environ. agriculture assessment areas different district Climate soil (.%), ./s--- households using value Agricultural highly livelihoods rate score sensitivity, variability However, Islam approach higher integrated intensity total use values analysis exposure, indicator people salinity scores Glob. climatic coast farming hand, intervention rural sound used water Change Development diversity factors farm framework impacts irrigation rain-fed sanitation (.%) Disaster Furthermore, Land M.A. Nat. based capital collab: district, districts. drivers hazard heterogeneous income index, production px; sector specific {font-family ACI Assessment Clim. Coastal Manag. Patuakhali, Research Spatial Use agro-technology assessing case change, degradation distributed districts, effects entire erosion erosion, facilities font-size levels lower mortality productivity rise risks spatially structurally studies > < ./j.gloenvcha... Assessing Bangladesh: Bhola Dhaka, Health Int. Patuakhali Risk World accounted adoption aggregated assessments change. change: communities components countries develop developing distribution double; extreme global help hot houses impact map million model multiple organic pattern phosphorus potential rice risk socioeconomic systems years (.) Bhola, Bureau EI, Group Haque Hoque IPCC Indicators Khulna, Lakshmipur, M.N. Mapping Ocean Reduct. SI, Sci. Sensitivity Soil USA applied biophysical border-color border-width capacity, circumplex conditions considered corresponded crops, cyclones diversification drought, ds/m; ecological exposed following future identify improved key like literature livestock matter method natural planning practices results revealed sea shows significant solid; spots strong study, support temperature unhygienic values, variation variety vulnerability, weather {font-style {font-weight (.), (IPCC) .–.. AHP ALVI, Academy Adapt. Adaptive BMD Chinese Coast. Cui Data Dimension Drought Hazards Index Intergovernmental LISA M.Z.H. M.Z.H.; Meghna Mitig. Natural No. Panel Public Res. SRDI Satkhira, Strateg. Therefore, University Working [], agro-ecological, aspects assessed available bold buffers calculated categorized children collected community composite courier; decision density dependent dynamics em; emergency events female fisheries fisheries, flood geographical greater growth houses, human increased indicates indicating indices interior island large living local mainly major mangrove methodology moderate open period policy precipitation prioritized pt;} reduce referred relative represents research resources, riverbank scale sea-level source statistical strategies susceptibility technique techniques time zone


< back
Choose tabs and time to close your session
All tabs in all windows
All tabs in current window
All tabs opened after timer set
This tab only
minutes.


Number Calculator
Menu
Number Calculator
In this webpage you can enter three numbers and you will be able to get the max,min,averag, median and range.
Calculate
Max:
Min:
Average:
Median:
Range:


Meet my dog Maggie!
She really loves food!
Here are some of her favorites:
- Chicken
- Ice cream
- Potato chips
- Anything that falls on the floor
Here are some things she likes to do:
- Sleeping
- Walks
- Fetch
- Parks
- Barking at strangers
Table of Time Sleeping vs. Awake
In conclusion:
My dog Maggie is a a pain in the butt lovely and fun dog. She's a great part of my life. I hope you can see that too.
Feel free to reach out with any question or comments by clicking here
Or check out my site here!


YearPicker
Contents
What is YearPicker
YearPicker.js is a lightweight yet configurable yearpicker for jQuery that makes it easy to select a year from a popup similar to the date picker. This plugin allows you to easily customaize the YearPicker the way you want it to.
Installation
Include the script yearpicker.js and Stylesheet yearpicker.css on the webpage
<link rel='stylesheet' href='yearpicker.css' /> <script src= 'yearpicker.js'></script>
Basic Usage
The basic use of yearpicker.js plugin with a related javascript code
Examples
Code
$(".yearpicker").yearpicker()
Events
YearPicker allows you to invokes a function like on value changed, onShow, onHide.
Examples
Selected Value
Code:
-
$(".yearpicker").yearpicker({ onChange : function(value){ // YOUR CODE COMES_HERE } });
Options
| Property | Default | Description |
|---|


Ampia selezione di falci da collezione, per ordinarle utilizzare il pulsante con scritto: COMPRA.
Prodotti
Descrizione
Offerta prendi 2 paghi 1.
Pin and Leaf
Descrizione dell'autore:
After seeing SU movie i wanted to draw scythes variations, like these.
On left there is Leaf, a little obvious name for a green and curved scythe.
On right there is Pin, named after its lower part.
Sanguine Scythe
Descrizione dell'autore:
Well... I started this scythe with the idea of a raven one, but then the red won.
The blood of the victims cut in half by Sanguine add more red light to it.
Techno Scythe
Descrizione dell'autore:
The idea of this techno variation of a scythe came out after reaching the rank of Old Mate on Solaris United on Warframe.
The struggle of farming was intense...but the daily standing limit was the most difficult part.


Guidance
Contact details of the people in child death overview panels (CDOPs) who are responsible for receiving child death notifications.
ODS , 14.8KB
This file is in an OpenDocument format
If you use assistive technology (such as a screen reader) and need a version of this document in a more accessible format, please email<EMAIL_ADDRESS>. Please tell us what format you need. It will help us if you say what assistive technology you use.
MS Excel Spreadsheet , 101KB
If you use assistive technology (such as a screen reader) and need a version of this document in a more accessible format, please email<EMAIL_ADDRESS>. Please tell us what format you need. It will help us if you say what assistive technology you use.
Contact details of the person responsible for dealing with child death notifications in every child death overview panel ( CDOP ) in England.
CDOPs conduct case reviews to help prevent further child deaths. You can find out more about their responsibilities in the ‘Working together to safeguard children’ guidance.
Published: 13 October 2013
Updated: 13 February 2017
From: Department for Education


Not sure if this counts but having worked in a supermarket the past couple of years and aswell as during level 4 lockdowns last year it has given me a new perspective on things. There are a surprising amount of customers who are very rude and demanding no matter how nice you are and how much you try to help them. This has influenced me because now whenever I visit a retail store I try to be extra polite and understandble if there is ever an issue or I have to wait for something. I know most of the time the staff are usually just trying their best.
Strategic, because I when I come up against a big task I have to do, it will help me think about the ways to complete it.
Well back when I was at school we had to do a group project. But the others wouldn't be much help and would muck around the whole time. I didn't want to create any conflict at the time so I ended up just doing majority of the project myself and while we passed with an Achieved mark it could have been a lot better if everyone pitched in. I think the strategy I would use now would in this situation is just to keep motivating the rest of the group and keep reminding them so we all do our fair share of the project.


--- layout: data_model title: ClusteringAlgorithmParametersType this_version: 4.1 ---
The ClusteringAlgorithmParametersType captures any parameters that may have been used in a malware clustering algorithm.
| Field Name | Type | Description |
|---|---|---|
| Distance_Threshold0..1 | decimal |
The Distance_Threshold field specifies the minimum distance threshold for the cluster, or the minimum distance between nodes in order for them to belong to the same cluster. |
| Number_of_Iterations0..1 | positiveInteger |
The Number_of_Iterations field specifies the number of times that the algorithm was executed in order to produce the cluster. |


1. Choosing New from the File menu displays an email composition window..
2. Choosing Open from the File menu brings up the file chooser.
3. Choosing Preferences from the Edit menu will bring up a dialog. Most of this dialog is only for show.
4. Choosing About Metalworks from the help menu brings up a JOptionPane with a brief description of the application.
5. Choosing Open Help Window from the Help menu brings up an internal frame which displays a set of HTML files containing all sorts of useful info. Look through these for tips about using the Java Look and Feel.
6. Selecting from the Theme menu allows you to change the color theme of the application. The default theme (Steel) and several other demo themes are included. One note that the themes can control the sizes, as well as the colors of many controls. Also included with this release is the PropertiesMetalTheme class which allows you to read a theme's colors from a text file. The Charcoal theme is an example of using this.


Syntax:
get-dispatch-macro-character disp-char sub-char &optional readtable => function
set-dispatch-macro-character disp-char sub-char new-function &optional readtable => t
Arguments and Values:
disp-char---a character.
sub-char---a character.
readtable---a readtable designator. The default is the current readtable.
function---a function designator or nil.
new-function---a function designator.
Description:
set-dispatch-macro-character causes new-function to be called when disp-char followed by sub-char is read. If sub-char is a lowercase letter, it is converted to its uppercase equivalent. It is an error if sub-char is one of the ten decimal digits.
set-dispatch-macro-character installs a new-function to be called when a particular dispatching macro character pair is read. New-function is installed as the dispatch function to be called when readtable is in use and when disp-char is followed by sub-char.
For more information about how the new-function is invoked, see Section <IP_ADDRESS> (Macro Characters).
get-dispatch-macro-character retrieves the dispatch function associated with disp-char and sub-char in readtable.
get-dispatch-macro-character returns the macro-character function for sub-char under disp-char, or nil if there is no function associated with sub-char. If sub-char is a decimal digit, get-dispatch-macro-character returns nil.
Examples:
(get-dispatch-macro-character #\# #\{) => NIL (set-dispatch-macro-character #\# #\{ ;dispatch on #{ #'(lambda(s c n) (let ((list (read s nil (values) t))) ;list is object after #n{ (when (consp list) ;return nth element of list (unless (and n (< 0 n (length list))) (setq n 0)) (setq list (nth n list))) list))) => T #{(1 2 3 4) => 1 #3{(0 1 2 3) => 3 #{123 => 123If it is desired that #$foo : as if it were (dollars foo).
(defun |#$-reader| (stream subchar arg) (declare (ignore subchar arg)) (list 'dollars (read stream t nil t))) => |#$-reader| (set-dispatch-macro-character #\# #\$ #'|#$-reader|) => T
See Also:
Section <IP_ADDRESS> (Macro Characters)
Side Effects:
The readtable is modified.
Affected By:
Exceptional Situations:
For either function, an error is signaled if disp-char is not a dispatching macro character in readtable.
See Also:
Notes:
It is necessary to use make-dispatch-macro-character to set up the dispatch character before specifying its sub-characters.


we'll help you track, optimize, & analyze the substance of your news
your news habits through visualizations
your news reading goals
your news bias & slant


Mo'Go is a mobile platform that reduces transportation cost throughout the sharing economy. Tell us where you want to go, and we will match you with a community driver. All over the world, the sharing economy is changing transportation in cities making it cheaper and more efficient for citizens. Mo'Go brings the sharing economy to Accra so you can also cut your cost and save more money.
Join our carpool and catch a ride with a community member who is going in your direction


If you are using the Apache webserver, consider using mod_wsgi.
Watch Out
Please make sure in advance that any app.run() calls you might have in your application file are inside an if __name__ == '__main__': block or moved to a separate file. Just make sure it’s not called because this will always start a local WSGI server which we do not want if we deploy that application to mod_wsgi.
If you don’t have mod_wsgi installed yet you have to either install it using a package manager or compile it yourself. The mod_wsgi installation instructions cover source installations on UNIX systems.
If you are using Ubuntu/Debian you can apt-get it and activate it as follows:
# apt-get install libapache2-mod-wsgi
On FreeBSD install mod_wsgi by compiling the www/mod_wsgi port or by using pkg_add:
# pkg_add -r mod_wsgi
If you are using pkgsrc you can install mod_wsgi by compiling the www/ap2-wsgi package.
If you encounter segfaulting child processes after the first apache reload you can safely ignore them. Just restart the server.
To run your application you need a yourapplication.wsgi file. This file contains the code mod_wsgi is executing on startup to get the application object. The object called application in that file is then used as application.
For most applications the following file should be sufficient:
from yourapplication import app as application
If you don’t have a factory function for application creation but a singleton instance you can directly import that one as application.
Store that file somewhere that you will find it again (e.g.: /var/www/yourapplication) and make sure that yourapplication and all the libraries that are in use are on the python load path. If you don’t want to install it system wide consider using a virtual python instance. Keep in mind that you will have to actually install your application into the virtualenv as well. Alternatively there is the option to just patch the path in the .wsgi file before the import:
import sys
sys.path.insert(0, '/path/to/the/application')
The last thing you have to do is to create an Apache configuration file for your application. In this example we are telling mod_wsgi to execute the application under a different user for security reasons:
<VirtualHost *>
ServerName example.com
WSGIDaemonProcess yourapplication user=user1 group=group1 threads=5
WSGIScriptAlias / /var/www/yourapplication/yourapplication.wsgi
<Directory /var/www/yourapplication>
WSGIProcessGroup yourapplication
WSGIApplicationGroup %{GLOBAL}
Order deny,allow
Allow from all
</Directory>
</VirtualHost>
Note: WSGIDaemonProcess isn’t implemented in Windows and Apache will refuse to run with the above configuration. On a Windows system, eliminate those lines:
<VirtualHost *>
ServerName example.com
WSGIScriptAlias / C:\yourdir\yourapp.wsgi
<Directory C:\yourdir>
Order deny,allow
Allow from all
</Directory>
</VirtualHost>
For more information consult the mod_wsgi wiki.
If your application does not run, follow this guide to troubleshoot:
Keep in mind that mod_wsgi disallows doing anything with sys.stdout and sys.stderr. You can disable this protection from the config by setting the WSGIRestrictStdout to off:
WSGIRestrictStdout Off
Alternatively you can also replace the standard out in the .wsgi file with a different stream:
import sys
sys.stdout = sys.stderr
Your application probably is a single .py file you symlinked into the site-packages folder. Please be aware that this does not work, instead you either have to put the folder into the pythonpath the file is stored in, or convert your application into a package.
The reason for this is that for non-installed packages, the module filename is used to locate the resources and for symlinks the wrong filename is picked up.
To help deployment tools you can activate support for automatic reloading. Whenever something changes the .wsgi file, mod_wsgi will reload all the daemon processes for us.
For that, just add the following directive to your Directory section:
WSGIScriptReloading On
Virtual environments have the advantage that they never install the required dependencies system wide so you have a better control over what is used where. If you want to use a virtual environment with mod_wsgi you have to modify your .wsgi file slightly.
Add the following lines to the top of your .wsgi file:
activate_this = '/path/to/env/bin/activate_this.py'
execfile(activate_this, dict(__file__=activate_this))
This sets up the load paths according to the settings of the virtual environment. Keep in mind that the path has to be absolute.


[§580-16] Divorce decree, support order; social security number. The social security number of any individual who is party to a divorce decree or subject to a support order issued under this chapter shall be placed in the records relating to the matter. [L 1997, c 293, §7]


Messaging control center
GitHub
warning
Error
Notification title
Notification message
URL to notification icon
URL to notification image
Target URL for click action
email
Send


Cloud
Home
Support
For support, please complete the form below
Your Name
Your E-mail Address
Description of Problem
Send


Variables
Number Variable =
String Variable =
Test Variable =
Iterate
Up one =
Up more =
Up many =
Functions
Answer 1 =
Answer 2 =
Loops
Array from variable section =
If/Else
Strings =
Numbers =


Latest Trends and Stories
'twas the week before(and after) Christmas, when shoppers went nuts'
article - Dec 2017
why you should lean into how-to content in 2018
article - Dec 2017
the auto dealer's guide to moving metal in a digital world
tutorial - Dec 2017
why brands should take a stand in their ads: 3 perspectives, 1 campaign
case study - Nov 2017
are you worth it? your customer wants to know
perspective - Nov 2017
holiday shoppers are in the driver's seat now-here's what they're looking for
Article - Nov 2017


ZDFFT1D
Routine Documentation— Input: INTEGER MODE
The value of MODE on input determines the operation performed by
ZDFFT1D
.
On input:
- MODE=0 : only initializations (specific to the values of N) are performed using a default plan; this is usually followed by calls to the same routine with MODE=1.
- MODE=1 : a complex-to-real transform is performed. Initializations are assumed to have been performed by a prior call to
ZDFFT1D
.- MODE=2 : (default) initializations and a complex-to-real transform are performed.
- MODE=100 : similar to MODE=0; only initializations (specific to the value of N) are performed, but these are based on a plan that is first generated by timing a subset of all possible plans and choosing the quickest (i.e. the FFT computation was timed as fastest based on the chosen plan). The plan generation phase may take a significant amount of time depending on the value of N.
CALL DZFFT1D(0,N,X,Y,COMM,INFO) CALL DZFFT1D(1,N,X,Y,COMM,INFO) DO 10 I = 1, N/2+1 Y(I) = -Y(I)*EXP(-DBLE(I-1)/DBLE(N)) 10 CONTINUE CALL ZDFFT1D(2,N,Y,X,COMM,INFO) |


| Table 1 |
Simulated DEFAULT (i.e., including moisture stress) maize yi ... |
| Table 2 |
Simulated NONSTRESS maize yield (Mg ha -1) averaged across a ... |
| Table 3 |
Simulated average maize growing period length averaged acros ... |
| Table 4 |
Simulated average maize Yield Loss Index (YLI) averaged acro ... |


|
KratosMultiphysics
KRATOS Multiphysics (Kratos) is a framework for building parallel, multi-disciplinary simulation software, aiming at modularity, extensibility, and high performance. Kratos is written in C++, and counts with an extensive Python interface.
|
All the processes python should be derived from "Process". More...
Public Member Functions | |
| def | __init__ (self, Model, settings) |
| def | ExecuteInitialize (self) |
All the processes python should be derived from "Process".
| def level_set_remeshing_process.LevelSetRemeshingProcess.__init__ | ( | self, | |
| Model, | |||
| settings | |||
| ) |
| def level_set_remeshing_process.LevelSetRemeshingProcess.ExecuteInitialize | ( | self | ) |
| level_set_remeshing_process.LevelSetRemeshingProcess.distance_modification_parameters |
| level_set_remeshing_process.LevelSetRemeshingProcess.do_remeshing |
| level_set_remeshing_process.LevelSetRemeshingProcess.main_model_part |
| level_set_remeshing_process.LevelSetRemeshingProcess.max_iter |
| level_set_remeshing_process.LevelSetRemeshingProcess.metric_parameters |
| level_set_remeshing_process.LevelSetRemeshingProcess.model |
| level_set_remeshing_process.LevelSetRemeshingProcess.moving_parameters |
| level_set_remeshing_process.LevelSetRemeshingProcess.ray_casting_tolerance |
| level_set_remeshing_process.LevelSetRemeshingProcess.skin_model_part |
| level_set_remeshing_process.LevelSetRemeshingProcess.skin_model_part_name |
| level_set_remeshing_process.LevelSetRemeshingProcess.step |
| level_set_remeshing_process.LevelSetRemeshingProcess.update_coefficient |


The detailed diagnosis of the problem suggests that a larger portion of SQL statements are
being compiled rather than retrieving their access plans from the package cache. To analyse the problem further
database administrator monitors elements for SQL compilation.
Note: Set the refresh interval on the top right pane to 5 seconds.
Ideally, we would like to see very minimal compilations and package cache inserts. At the same time, package cache lookups should be high to indicate package is being reused. The above evidence suggests that a larger portion of SQL statements are being compiled rather than retrieving their access plans from the package cache.


VisClass
has seven different instance data fields as shown in VisClass Instance Data
. Each of these fields is discussed in detail in the following sections, and each may be set or reset during execution by sending the visible object certain messages.
Several of the instance fields will never be used by the application programmer. Most likely, you will work directly with the
VI_bounds
field and perhaps the
VI_attrs
or
VI_geoAttrs
fields. It's unlikely you will need to use the others unless you're doing something quite unusual.
Code Display 15-1 VisClass Instance Data
/* This is the definition of the VisClass instance data fields with some comments * as to their use. */
/* VI_bounds * VI_bounds is a Rectangle structure defining the outermost boundaries of * the visible object. */
@instance Rectangle VI_bounds = {0, 0, 0, 0};
/* VI_typeFlags * VI_typeFlags is a record containing eight flags that determine the * type of the visible object. None are set by default. */
@instance VisTypeFlags VI_typeFlags = 0; /* Possible flags: * VTF_IS_COMPOSITE VTF_IS_WINDOW * VTF_IS_PORTAL VTF_IS_WIN_GROUP * VTF_IS_CONTENT VTF_IS_INPUT_NODE * VTF_IS_GEN VTF_CHILDREN_OUTSIDE_PORTAL_WIN */
/* VI_attrs * VI_attrs is a record that contains eight attribute flags for the * object. Those set by default are shown. */
@instance VisAttrs VI_attrs = (VA_MANAGED | VA_DRAWABLE | VA_DETECTABLE | VA_FULLY_ENABLED); /* Possible flags: * VA_VISIBLE VA_FULLY_ENABLED * VA_MANAGED VA_DRAWABLE * VA_DETECTABLE VA_BRANCH_NOT_MINIMIZABLE * VA_OLD_BOUNDS_SAVED VA_REALIZED */
/* VI_optFlags * VI_optFlags is a record containing eight window update flags. * The flags set by default are shown. */
@instance VisOptFlags VI_optFlags = (VOF_GEOMETRY_INVALID | VOF_GEO_UPDATE_PATH | VOF_WINDOW_INVALID | VOF_WINDOW_UPDATE_PATH | VOF_IMAGE_INVALID | VOF_IMAGE_UPDATE_PATH); /* Possible flags: * VOF_GEOMETRY_INVALID VOF_GEO_UPDATE_PATH * VOF_IMAGE_INVALID VOF_IMAGE_UPDATE_PATH * VOF_WINDOW_INVALID VOF_WINDOW_UPDATE_PATH * VOF_UPDATE_PENDING VOF_EC_UPDATING */
/* VI_geoAttrs * VI_geoAttrs is a record of eight geometry management flags. */
@instance VisGeoAttrs VI_geoAttrs = 0; /* Possible flags: * VGA_GEOMETRY_CALCULATED VGA_NO_SIZE_HINTS * VGA_NOTIFY_GEOMETRY_VALID VGA_DONT_CENTER * VGA_USE_VIS_SET_POSITION VGA_USE_VIS_CENTER * VGA_ALWAYS_RECALC_SIZE VGA_ONLY_RECALC_SIZE_WHEN_INVALID
/* VI_specAttrs * VI_specAttrs is a record containing eight flags used when the visible * object is part of a specific UI library. This field is rarely if ever * used by applications. */
@instance SpecAttrs VI_specAttrs = 0; /* Possible flags: * SA_ATTACHED SA_REALIZABLE * SA_BRANCH_MINIMIZED SA_USES_DUAL_BUILD * SA_CUSTOM_VIS_PARENT SA_SIMPLE_GEN_OBJ * SA_CUSTOM_VIS_PARENT_FOR_CHILD * SA_TREE_BUILT_BUT_NOT_REALIZED */
/* VI_link * VI_link contains an object pointer to the visible object's next sibling * in the tree. Note that VisClass has no corresponding @composite field; * if the object is to have children, it must be of class VisCompClass.
@instance @link VI_link;


--- title: "How to Cook Favorite Cranberry Jalapeno Cream Cheese Dip Delicious" slug: cranberry-jalapeno-cream-cheese-dip description: "Cranberry Jalapeno Cream Cheese Dip Recipe - This is a fun dip that is both sweet and spicy. I got the recipe by varying other cranberry salsa and dip recipes I have found. I got the idea of the fusion of oil from a friend. There are many ideas for use and a great item to take along when you want to surprise your friends with something they probably have not tried. Serve with Triscuits®, pita chips, or crackers. Easiest Way to Make Super Quick Homemade Cranberry Jalapeno Cream Cheese Dip Tasty" date: 2021-05-09T12:27:33Z image: https://cdn.statically.io/img/images.media-allrecipes.com/userphotos/4475630.jpg thumbnail: https://cdn.statically.io/img/images.media-allrecipes.com/userphotos/4475630.jpg cover: https://cdn.statically.io/img/images.media-allrecipes.com/userphotos/4475630.jpg author: Lili ratingvalue: 4.2 reviewcount: 872 recipeingredient: - "¼ cup vegetable oil" - "10 ounces dried sweetened cranberries" - "½ cup white sugar, or to taste" - "½ cup water, or more as needed" - "2 small jalapeno peppers, seeded and finely diced" - "1 tablespoon lemon juice" - "2 teaspoons dried cilantro" - "¼ teaspoon salt" - "2 (8 ounce) packages cream cheese, softened" recipeinstructions: - "Heat a saucepan over medium heat; add oil. Stir cranberries into hot oil and cook until cranberries absorb most of oil, 5 to 10 minutes. Mix sugar, water, jalapeno peppers, lemon juice, cilantro, and salt into cranberries; cook until reduced and softened, 10 to 15 more minutes. Add more water if needed." - "Pulse cranberry mixture in a food processor or blender until very smooth; cool completely." - "Stir cooled cranberry mixture and cream cheese together in a bowl until smooth and creamy." categories: - "Appetizers and Snacks" - "Dips and Spreads Recipes" - "Cheese Dips and Spreads Recipes" - "Recipes" tags: - "appetizers and snacks" - "dips and spreads recipes" - "cheese dips and spreads recipes" katakunci: cranberry jalapeno cream cheese dip, appetizers and snacks, dips and spreads recipes, cheese dips and spreads recipes, . nutrition: 205.5 calories recipecuisine: Western preptime: "P0DT0H10M" cooktime: "P0DT0H15M" totaltime: "P0DT0H55M" recipeyield: "16 servings" recipecategory: - Appetizers and Snacks - Dips and Spreads Recipes - Cheese Dips and Spreads Recipes quotes: Who needs love when you can eat all the chocolate in the world. ---
Cranberry Jalapeno Cream Cheese Dip - Hey everyone, hope youre having an amazing day today. It is me again Lili , welcome to our recipe website. Today, I will show you a way to make a distinctive dish, Cranberry Jalapeno Cream Cheese Dip. One of my favorites food recipes. For mine, Im gonna make it a little bit tasty. This will be really delicious.
Cranberry Jalapeno Cream Cheese Dip is This is a fun dip that is both sweet and spicy. I got the recipe by varying other cranberry salsa and dip recipes I have found. I got the idea of the fusion of oil from a friend. There are many ideas for use and a great item to take along when you want to surprise your friends with something they probably have not tried. Serve with Triscuits®, pita chips, or crackers.
Cranberry Jalapeno Cream Cheese Dip is one of the most well liked of recent trending meals in the world. its simple, it is fast, it tastes yummy. its appreciated by millions daily. It is easy, it is quick, it tastes delicious. Cranberry Jalapeno Cream Cheese Dip is something that I have loved my entire life. They are fine and they look fantastic. They are fine and they look fantastic. Cranberry Jalapeno Cream Cheese Dip is something that I have loved my whole life.
To get started with this recipe, we have to first prepare a few components. You can cook Cranberry Jalapeno Cream Cheese Dip using 9 ingredients and 3 steps. Here is how you cook it.
So that is going to wrap it up with this special food Cranberry Jalapeno Cream Cheese Dip recipe. Thanks so much for your time. Im sure you can make this at home. Theres gonna be another interesting food in home recipes coming up. Remember to bookmark this page on your browser, and share it to your family, friends and colleague. Thank you for reading. Go on get cooking!


DIRSITE
Development aid intended to provide convenience by offering CLI input and output as browser-viewable web pages. When installed above a python package, prefab command lines are presented in tables. Other table contents may be assigned in a configuration file.
Installation
DIRSITE files may be copied into any directory to be used for executing arbitrary CLI instructions.
- Commands are executed with the privileges of the server login.
- URL may not require encoding. Example: {readme_cgi}
- URL may require encoding. Example for Windows: {dir_readme_cgi}. The
&&
operator may not be parsed when used in a URL. Improved results may be seen by using the encoded URL, {encoded_dir_readme_cgi}
Python Package Assistant
When configured, test by going to {command_line}.
DIRSITE Configuration File dirsite_files/dirsite.ini
{dirsite_ini}
Some configuration changes to consider:
- To see the interface with buttons rather than links, change
navigate_by_post
to True. When True, custom URLs can no longer be typed into the URL line.
- To change the dirsite_cl.py refresh rate to once every 5 minutes, change
reload_time
to 300 (seconds). When navigate_by_post
is True, reload is disabled to prevent the loss of persistent page view in the browser.
- At server start, automatically load a view page by changing
first_page
value to {command_line}
DIRSITE Views Configuration File dirsite_files/views.ini
{views_ini}
Some configuration changes to consider:
- To change the view shown when the command line is entered, change the
[template] selection
assignment.
- To add a directory wide command... (Note: <n> indicates a number denoting order of row appearance, starting from 1.)
- 'dir_header_<n>' for the table header of the command.
- 'dir_content_<n>' for the command as it appears on command line.
- If necessary, the following variables are available at runtime:
dirtest
.
- To add a file specific command... (Note: <n> indicates a number denoting order of column appearance, starting from 1.)
- 'file_header_<n>' for the table header of the command.
- 'file_content_<n>' for the command as it appears on command line.
- 'file_dependency_<n>' required by command as it appears on command line.
- If necessary, the following variables are available at runtime:
dirtest
.
Do not edit this HTML file. It is regenerated every time server is started.


---
layout: home
title: Home Page of Prasanna Balaprakash
---
{{ site.author }}
Director of AI Programs and Distinguished R&D Staff Scientist
Computing and Computational Sciences Directorate
Oak Ridge National Laboratory
Building 5700, Room G215, Mail Stop 6164
P.O. Box 2008, 1 Bethel Valley Road
Oak Ridge, TN 37831
865-576-9087 (Please no cold calls/solicitations)
pbalapra (at) ornl (dot) gov
Since March 2023, I am leading Oak Ridge National Laboratory's Artificial Intelligence Initiative, wherein I direct laboratory research, development and application of artificial intelligence and machine learning (AI/ML) to solve problems of national importance. I seek to deliver foundational, scalable, and applied AI/ML capabilities supporting Oak Ridge National Laboratory's broad mission and provide world-class solutions in computer and computational science, neutron science, materials science, biology and health science, nuclear engineering, isotopes, manufacturing, energy, and climate science.
My research interests span the areas of artificial intelligence, machine learning, optimization, and high-performance computing. My research focuses on the design and development of foundational and scalable data science algorithms to model and optimize complex systems in scientific and engineering domains.
I am a recipient of U.S. Department of Energy 2018 Early Career Award. I lead the AI area in RAPIDS2: A SciDAC Institute for Computer Science, Data, and Artificial Intelligence. I lead the research and development of DeepHyper, a scalable automated machine learning package for DOE leadership-class systems.
Previously,
I received my PhD in 2010 from CoDE-IRIDIA (AI Lab), Université Libre de Bruxelles, Brussels, Belgium, where I was a recipient of Marie Skłodowska-Curie and F.R.S-FNRS Aspirant fellowships from the the European Commission and the Belgian-French Community's National Fund for Scientific Research, respectively.


There will be queries within the HTML, like this.
SELECT a.col, b.col FROM table_a AS a, table_b AS b WHERE a.col = b.col;
SELECT a.col, b.col FROM table_a AS a, table_b AS b;
There will be other queries as well with different keywords.
CREATE TABLE Sample (
ColumnA int,
ColumnB varchar(255)
);
Hyperlinks like this should work.
Even if there are SELECT or other keywords in the middle of text, hopefully it should not think these are queries.
If there are multiple queries within the same tag, it should not be a problem.
ALTER TABLE Sample ADD ColumnC varchar(255);
SELECT a.col, b.col FROM a, b WHERE a.col = 5;
If the query is after a normal sentence, it should still work. SELECT c.col FROM table_c as c;
SELECT statements look like this: SELECT d.col from table_d as d;
Hello.


Web developers working for Zühlke since 2013
made with reveal.js
Follow the presentation here
React is a library, not a framework.
It handles rendering and state, but leaves other things like ajax and routing up to you.
Fortunately, thanks to the huge community, there are always many options to choose from.
$ mkdir react-component && cd react-component
$ touch index.html
$ touch MyComponent.js
index.html

MyComponent.js
function MyComponent() {
return React.createElement(
'h1',
{},
'Hello Component!'
);
}
const container = document.querySelector('#container');
const element = React.createElement(MyComponent);
ReactDOM.render(element, container);


Package org.apache.sis.referencing
Base classes for reference systems used for general positioning.
An explanation for this package is provided in the OpenGIS® javadoc.
The remaining discussion on this page is specific to the SIS implementation.
The most commonly used kinds of Reference Systems in Apache SIS are the Coordinate Reference Systems (CRS), which handle coordinates of arbitrary dimensions. The SIS implementations can handle 2D and 3D coordinates, as well as 4D, 5D, etc. An other less-frequently used kind of Reference System uses labels instead, as in postal address. This package is the root for both kinds, with an emphasis on the one for coordinates. The two kinds of referencing system are implemented in the following packages:
org.apache.sis.referencing.crs
for referencing by coordinates (ISO 19111)org.apache.sis.referencing.gazetteer
for referencing by geographic identifiers (ISO 19112), together with the linking from geographic identifiers to coordinates.
Fetching geodetic object instances
Geodetic objects can be instantiated either
directly by specifying all information to a factory method or constructor, or
indirectly by specifying the identifier of an entry in a database.
In particular, the EPSG database provides definitions for many geodetic objects,
and Apache SIS provides convenience shortcuts for some of them in the
CommonCRS
enumerations. Other convenience methods are
CRS.forCode(String)
,
CRS.fromWKT(String)
and
CRS.fromXML(String)
Usage example
The following example projects a (latitude, longitude) coordinate to
a Universal Transverse Mercator projection in the zone of the coordinate:
GeographicCRS source = CommonCRS.WGS84.geographic(); ProjectedCRS target = CommonCRS.WGS84.UTM(20, 30); // 20°N 30°E (watch out axis order!) CoordinateOperation operation = CRS.findOperation(source, target, null); if (CRS.getLinearAccuracy(operation) > 100) { // If the accuracy is coarser than 100 metres (or any other threshold at application choice) // maybe the operation is not suitable. Decide here what to do (throw an exception, etc). } MathTransform mt = operation.getMathTransform(); DirectPosition position = new DirectPosition2D(20, 30); // 20°N 30°E (watch out axis order!) position = mt.transform(position, position); System.out.println(position);
The EPSG database
The EPSG geodetic parameter dataset is a structured database required to:
- define Coordinate Reference Systems (CRS) such that coordinates describe positions unambiguously;
- define Coordinate Operations that allow coordinates to be changed from one CRS to another CRS.
- classes or methods implementing a specific coordinate operation method;
- enumeration constants representing some specific CRS;
- fields containing parameter values.
AuthorityFactory
method to invoke, while
the code specifies the argument value to give to that method in order to get the EPSG object.
For example the CommonCRS.WGS84
documentation said that object
of type geodetic datum is associated to code EPSG:6326
.
This means that the EPSG object could be obtained by the following code:
The EPSG objects can also be inspected online on the EPSG registry web site.DatumAuthorityFactory factory = ...; // TODO: document how to obtain an EPSG factory. GeodeticDatum datum = factory.createGeodeticDatum("6326");
- Since:
- 0.4
Defined in the sis-referencing
module
-
Class Summary Class Description AbstractIdentifiedObject Base class for objects identified by a name or a code.AbstractReferenceSystem Description of a spatial and temporal reference system used by a dataset.Builder<B extends Builder<B>> Base class of builders for various kind ofIdentifiedObject
.CRS Static methods working on Coordinate Reference Systems.GeodeticCalculator Performs geodetic calculations on a sphere or an ellipsoid.IdentifiedObjects Utility methods working on arbitrary implementations of theIdentifiedObject
interface.ImmutableIdentifier Immutable value uniquely identifying an object within a namespace, together with a version.NamedIdentifier An identification of a CRS object which is both aIdentifier
and aGenericName
. -
Enum Summary Enum Description CommonCRS Frequently-used geodetic CRS and datum that are guaranteed to be available in SIS.CommonCRS.Temporal Frequently-used temporal CRS and datum that are guaranteed to be available in SIS.CommonCRS.Vertical Frequently-used vertical CRS and datum that are guaranteed to be available in SIS. -
Exception Summary Exception Description GeodeticException Unchecked exception thrown when an error occurred while computing a geodetic value.


|
tesseract
5.0.0-alpha-619-ge9db
|
#include "pgedit.h"
#include <cctype>
#include <cmath>
#include "blread.h"
#include "control.h"
#include "paramsd.h"
#include "pageres.h"
#include "tordmain.h"
#include "scrollview.h"
#include "svmnode.h"
#include "statistc.h"
#include "tesseractclass.h"
#include "werdit.h"
Go to the source code of this file.
Classes | |
| class | BlnEventHandler |
Namespaces | |
| tesseract | |
Macros | |
| #define | ASC_HEIGHT (2 * kBlnBaselineOffset + kBlnXHeight) |
| #define | X_HEIGHT (kBlnBaselineOffset + kBlnXHeight) |
| #define | BL_HEIGHT kBlnBaselineOffset |
| #define | DESC_HEIGHT 0 |
Variables | |
| char * | editor_image_win_name = "EditorImage" |
| int | editor_image_xpos = 590 |
| int | editor_image_ypos = 10 |
| int | editor_image_word_bb_color = ScrollView::BLUE |
| int | editor_image_blob_bb_color = ScrollView::YELLOW |
| int | editor_image_text_color = ScrollView::WHITE |
| char * | editor_dbwin_name = "EditorDBWin" |
| int | editor_dbwin_xpos = 50 |
| int | editor_dbwin_ypos = 500 |
| int | editor_dbwin_height = 24 |
| int | editor_dbwin_width = 80 |
| char * | editor_word_name = "BlnWords" |
| int | editor_word_xpos = 60 |
| int | editor_word_ypos = 510 |
| int | editor_word_height = 240 |
| int | editor_word_width = 655 |
| #define ASC_HEIGHT (2 * kBlnBaselineOffset + kBlnXHeight) |
Definition at line 41 of file pgedit.cpp.
| #define BL_HEIGHT kBlnBaselineOffset |
Definition at line 43 of file pgedit.cpp.
| #define DESC_HEIGHT 0 |
Definition at line 44 of file pgedit.cpp.
| #define X_HEIGHT (kBlnBaselineOffset + kBlnXHeight) |
Definition at line 42 of file pgedit.cpp.
| enum CMD_EVENTS |
Definition at line 46 of file pgedit.cpp.
| enum ColorationMode |
| Enumerator | |
|---|---|
| CM_RAINBOW | |
| CM_SUBSCRIPT | |
| CM_SUPERSCRIPT | |
| CM_ITALIC | |
| CM_BOLD | |
| CM_UNDERLINE | |
| CM_FIXEDPITCH | |
| CM_SERIF | |
| CM_SMALLCAPS | |
| CM_DROPCAPS |
Definition at line 80 of file pgedit.cpp.
| int editor_dbwin_height = 24 |
"Editor debug window height"
Definition at line 135 of file pgedit.cpp.
| char* editor_dbwin_name = "EditorDBWin" |
"Editor debug window name"
Definition at line 132 of file pgedit.cpp.
| int editor_dbwin_width = 80 |
"Editor debug window width"
Definition at line 136 of file pgedit.cpp.
| int editor_dbwin_xpos = 50 |
"Editor debug window X Pos"
Definition at line 133 of file pgedit.cpp.
| int editor_dbwin_ypos = 500 |
"Editor debug window Y Pos"
Definition at line 134 of file pgedit.cpp.
| int editor_image_blob_bb_color = ScrollView::YELLOW |
"Blob bounding box colour"
Definition at line 127 of file pgedit.cpp.
| int editor_image_text_color = ScrollView::WHITE |
"Correct text colour"
Definition at line 129 of file pgedit.cpp.
| char* editor_image_win_name = "EditorImage" |
"Editor image window name"
Definition at line 120 of file pgedit.cpp.
| int editor_image_word_bb_color = ScrollView::BLUE |
"Word bounding box colour"
Definition at line 125 of file pgedit.cpp.
| int editor_image_xpos = 590 |
"Editor image X Pos"
Definition at line 121 of file pgedit.cpp.
| int editor_image_ypos = 10 |
"Editor image Y Pos"
Definition at line 122 of file pgedit.cpp.
| int editor_word_height = 240 |
"Word window height"
Definition at line 141 of file pgedit.cpp.
| char* editor_word_name = "BlnWords" |
"BL normalized word window"
Definition at line 138 of file pgedit.cpp.
| int editor_word_width = 655 |
"Word window width"
Definition at line 142 of file pgedit.cpp.
| int editor_word_xpos = 60 |
"Word window X Pos"
Definition at line 139 of file pgedit.cpp.
| int editor_word_ypos = 510 |
"Word window Y Pos"
Definition at line 140 of file pgedit.cpp.


Ryu Hoshi (リュウ Ryū)
Résumé
— I do not compete with others, the only competition that challenges me is myself. As a fighter, friend and an employee I am known as contemplative, tortured and driven
Experience
-
2018
Amongst many fighters of the past was featured in the movie "Ready Player One". Ryu ready always!
-
2017
United with unknown until then to me Power Rangers to defea resurrected M.Bison.Damn good fighters they are, even not knowing karate ways!
-
2016
In "Street Fighter V" once and for all erased M.Bison from earth and tamed my inner Evil Ryu. Also spent some time on a side-project, mini-series "Street Fighter: Resurrection".
-
2014
Filmed in a martial arts tutorial "Street Fighter: Assassin's Fist", revealing to audience forgotten art of Ansatsuken.
-
2012
The gods of intenet concluded me in the animated movie "Wreck-It Ralph", but rewarded me with a good drink for it!
-
2008
My evil alter ego sneaked out of control and became a boss in "Street Fighter IV".
-
2006
Borrowed my famous ripped gi to Soki in "Onimusha: Dawn of Dreams", gods informed me he needed that for the battle.
-
1998
Defeated M. Bison in "Street Fighter Alpha 2", bastard wanted to use my heroic body for his evil intentions, but retreated with shame. Also this year I encountered Marvel universe in "Marvel vs. Capcom: Clash of Super Heroes" fighter,loyal to my employer, Capcom, of course.
-
1997
Reunited with Ken, my friend and opponent in "Street Fighter III". Men's friendship works mysteriously. Also helped with Arika project "Street Fighter EX"
-
1996
Took care of villainous Akuma in "Street Fighter Alpha 2". As a freelance on "Super Puzzle Fighter II Turbo" tried myself in a new genre, puzzle games. Let the wrath of seven heavens come upon these malicious enigmas, never again!
-
1995
Kept fighting in "Street Fighter Alpha: Warriors' Dreams".
-
1994
Screened in a movie "Street Fighter", so that the batllesof past would not be forgotten by millenial generation.
-
1991
Was promoted to "Street Fighter II". Didn't stay there for long, celebrations and office dwelling is not for me!
-
1987
Started working for Capcom project "Street Fighter". My partner was Ken Masters, the boss'name was Sagat.
Publications
-
2011
The true and humble story of me under pseudonim Tyler Wilde in an article "The evolution of Ken and Ryu"
-
2003 – 2018
For 15 years I have published comic books with Udon Entertainment depicting my adventures, bitter lessons and great victories.
Languages
Skills
Character
Life lesson
You must defeat Sheng Long to stand a chance.
Likes😃
Dislikes😞
Wants🥺
Education
Achievements
- #1 in "Top 25 Street Fighter Characters" by IGN, who also called me "fancy", "icon" and "a testament to the virtue of simplicity" ❤
- #2 in "Top 20 Street Fighter Characters of All Time" by GameDaily, same council found me worth of #6 place in "Top 25 Capcom Characters of All Time", which I proudly share with my partner Ken
- I was named "5th Most Powerful Street Fighter Character" by Screen Rant-san
- #71 in "Top 100 Heroes of All Time" by UGO Networks, also recognized #2 in their list of "Top 50 Street Fighter Characters"
- In a survey of 4000 online matches for Super Street Fighter IV, I got to be the most popular character, with 16.6% of players choosing my side


Ocean [ah39], ocean, in The Inner Sea
Last updated Turn #108
Ocean [ah39], ocean, in The Inner Sea
------------------------------------------------------------------------
15: Whalebone [fe4m], ship, 6 hulls, 1 rowing port, 18 sails, arrived from
15: Ocean [ah40], owner:
15: Toulouse [h1q], Pen, with 20 sailors, 15 lt. xbowmen,
15: accompanied by:
15: Jonathan [h9k], Pen, duke, with 39 pikemen
15: Halmary [f9m], Pen, with one worker, 15 lt. xbowmen
16: Whalebone [fe4m], ship, 6 hulls, 1 rowing port, 18 sails, departed for
16: Ocean [ah38].
17: Hungry looking birds circle overhead.
Routes leaving Ocean:
North, to Ocean [ag39], Crystal Sea, 6 days
East, to Ocean [ah40], 6 days
South, to Ocean [ai39], 6 days
West, to Ocean [ah38], 6 days
Inner locations:
Island [ab2f], island, 1 day, owner:
Pirate [ho8h], pirates, number: 4
Pirate [dt6j], pirates, number: 9
Pirate [eg8j], pirates, number: 10