Norman Walsh, Sun Microsystems, Inc<EMAIL_ADDRESS>DocBook is a general purpose [xml-rec] schema particularly well suited to books and papers about computer hardware and software (though it is by no means limited to these applications).
The Version 5.0 release is a complete rewrite of DocBook in RELAX NG. The intent of this rewrite is to produce a schema that is true to the spirit of DocBook while simultaneously removing inconsistencies that have arisen as a natural consequence of DocBook's long, slow evolution. The Technical Committee has taken this opportunity to simplify a number of content models and tighten constraints where RELAX NG makes that possible.
The Technical Committee provides the DocBook 5.0 schema in other schema languages, including W3C XML Schema and an XML DTD, but the RELAX NG Schema is now the normative schema.
This is a Committee Draft. It does not necessarily represent the consensus of the committee.
Please send comments on this specification to the<EMAIL_ADDRESS>list. To subscribe, please use the OASIS Subscription Manager.
The errata page for this specification is at http://www.oasis-open.org/docbook/specs/docbook5-errata.html.
Copyright © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 The Organization for the Advancement of Structured Information Standards [OASIS]. All Rights Reserved.
DocBook is general purpose XML schema particularly well suited to books and papers about computer hardware and software (though it is by no means limited to these applications).
The DocBook Technical Committee maintains the DocBook schema. Starting with V5.0, DocBook is normatively available as a [relaxng] Schema (with some additional Schematron assertions). W3C XML Schema and Document Type Definition (DTD) versions are also available.
The Version 5.0 release is a complete rewrite. In programming-language terms, think of it as a code refactoring.
This rewrite introduces a large number of backwards-incompatible changes. Essentially all DocBook V4.x documents will have to be modified to validate against DocBook V5.0. An XSLT 1.0 stylesheet is provided to ease this transition.
The DocBook Technical Committee welcomes bug reports and requests for enhancement (RFEs) from the user community. The current list of outstanding requests is available through the SourceForge tracker interface. This is also the preferred mechanism for submitting new requests. Old RFEs, from a previous legacy tracking system, are archived for reference.
The key words must, must not, required, shall, shall not, should, should not, recommended, may, and optional in this Committee Draft are to be interpreted as described in [rfc2119]. Note that for reasons of style, these words are not capitalized in this document.
The DocBook RELAX NG Schema is distributed from the DocBook site at OASIS. DocBook is also available from the mirror on http://docbook.org/.
There are no user-visible changes in 5.0 (Public Review Draft 1).
This version of DocBook V5.0 will become the official Committee Specification version of DocBook V5.0 as soon as the Technical Committee balloting process is finished.
There are no user-visible changes in 5.0CR7. Some of the sources we reorganized to make future customization easier.
If no bug reports are received before the November 7, 2007 DocBook TC meeting, this version will become the official DocBook V5.0 release.
This release contains a few bug fixes and improvements over V5.0CR5.
Fixed RFE 1759782: Allow uri
anywhere email
occurs.
Fixed RFE 1784312: Allow book
to be completely empty; allow personblurb
and titleabbrev
in bibliographic contexts.
Fixed RFE 1795884: Allow MathML in inlineequation
.
Fixed RFE 1800916: Allow keycap
(and friends) in userinput
.
This release contains a few improvements over V5.0CR3.
Fixed RFE 1708032: Fixed pattern naming inconsistency; changed db.href.attribute
to db.href.attributes
.
Fixed RFE 1700154: Added sortas
to termdef
.
Fixed RFE 1686919: Added an NVDL rules file.
Fixed RFE 1705596: Aded db.programming.inlines
(classname
, exceptionname
, function
, initializer
, interfacename
, methodname
, modifier
, ooclass
, ooexception
, oointerface
, parameter
, returnvalue
, type
, and varname
) to the content model of code
.
Fixed RFE 1689228: Fixed typo in Schematron assertion.
This release contains a few improvements over V5.0CR2.
Fixed RFE 1679775: Changed semantics of termdef
. A firstterm
is now required (instead of a glossterm
as in previous releases).
Fixed RFE 1673820: Adopted “http://docbook.org/xlink/role/olink
” as an XLink role value (xlink:role
) to identify OLinks expressed using XLink attributes.
Allow info
in HTML tables.
Fixed RFE 1682917: Added pgwide
attribute to example
.
Fixed RFE 1644553: Added label
attribute to CALS and HTML tables.
Fixed RFE 1588693: Added an acknowledgements
element, peer to dedication
, replacing ackno
which had only been available at the end of article
.
This release contains a few improvements over V5.0CR1 and a few bug fixes.
Fixed RFE 1630203: Allow empty glossary
.
Fixed RFE 1627845: Allow optional caption
on CALS table
and informaltable
.
Related to RFE 1627845: Allow inlines in HTML table
caption
.
Fixed RFE 1589139 (and RFE 1621178): Allow title
and titleabbrev
on qandaentry
.
Fixed RFE 1675932: Restore localname
, prefix
and namespace
as class
attribute values on tag
.
Fixed RFE 1669465: Schematron rules should refer to @xml:id
, not @id
.
This release contains a few improvements over V5.0b9 and a few bug fixes.
Made the content model of blockquote
broader. It was restricted too far in the transition to 5.0.
Fixed RFE 1575537: Allow markup from other namespaces in info
.
Fix the content model of ackno
so that it's the same as DocBook 4.x.
Fix bug where caption
was accidentally allowed in CALS tables.
This release contains several improvements over V5.0b8.
Fixed RFE 1537424: Allow jobtitle
inline.
Fixed typo; title
s are now required on task
, consistent with DocBook V4.x.
Fixed RFE 1554914: Make targetdoc
attribute on olink
optional.
Fixed RFE 1568417: Don't generate duplicate Schematron rules.
Fixed RFE 1568419: Inverted Schematron assertion for termdef
.
This release contains several improvements over V5.0b7.
Fixed RFE 1535166: Improve the data types of attributes in DocBook.
Fixed RFE 1549632: The inlineequation
element should use inlinemediaobject
not mediaobject
.
A number of small documentation improvements in the area of attribute and attribute enumerations.
This release contains several improvements over V5.0b6.
Fixed RFE 1520074: Define separate patterns for all the effectivity attributes to make customization easier.
Attempted to address RFE 1512505: Added an audience
effectivity attribute.
Rename audience
, origin
, and level
on simplemsgentry
to msgaud
, msgorig
, and msglevel
, respectively. This is a better parallel with the descendent elements of msgentry
and avoids a conflict with the
newly introduced audience
effectivity attribute.
Added startinglinenumber
attribute to orderedlist
.
Fixed bug where one of fileref
or entityref
was required on imagedata
even when the content was inline MathML or SVG.
This release contains several improvements over V5.0b5.
Fixed RFE 1434294: Allow MathML and SVG in imagedata
. Note: SVG is no longer allowed as an alternative to imagedata
. The alignment, scaling, and other presentational attributes are on imagedata
so it seems more
reasonable to allow SVG and MathML inside it.
Fixed RFE 1468921: Add person
element. Added person
and org
.
Fixed RFE 1306027: Support for aspect-oriented programming. Allow modifier
to appear in more places, and allow xml:space
on modifier
.
Added db.publishing.inlines
to db.bibliographic.elements
so that, for example, foreignphrase
can be used in bibliomixed
.
This release contains several improvements over V5.0b4.
Restored the class
attribute on refmiscinfo
(removing the type
attribute introduced in V5.0b4). The class
attribute is now an enumerated list with the standard otherclass
extension point.
Added parameter
to db.technical.inlines
. This allows parameter
to occur in places like userinput
and computeroutput
.
Allow XInclude elements in info
elements (in the docbookxi schemas).
Fixed bugs in the build process that resulted in broken DTD versions of beta 4 and earlier betas.
This release contains several improvements over V5.0b3.
Fixed RFE 1416903: Added a cover
element to hold additional material for document covers. Updated reference documentation.
Corrected a typo in the list of values allowed on the class
attribute of biblioid
: changed “pubnumber” to “pubsnumber” (note the “s”). This is consistent with its use as a replacement for the pubsnumber
tag that has been removed in DocBook V5.0.
Fixed a bug in the content model of the various “info
” elements. In previous beta releases, the title-related elements (title
, titleabbrev
, and subtitle
) were erroneously required to appear first. The requirement is only that they appear exactly or at most once, depending on the context.
Renamed the “sgmlcomment
” attribute value of the class
attribute of tag
. There's no significant difference between XML and SGML comments and the “SGML” name implies that there ought to be an “xmlcomment
” value, which there is not. The new value is simply “comment
”.
Renamed the “class
” attribute of refmiscinfo
. The DocBook semantics of class attributes is that they have enumerated values. This attribute should always have been called “type
” as it is now.
Updated renderas
on bridgehead
and class
on othercredit
to have “attribute/otherattribute” co-constraints. (In other words, if you select “other” for renderas
on bridgehead
or class
on othercredit
, you
have to also provide a value for otherrenderas
or othercredit
, respectively.
Changed width
attribute in media objects to be “text” instead of “xs:integer
”.
Fixed bug in the build process that resulted in unusable XML Schema versions of beta 2 and beta 3.
Improved reference documentation for attributes on many elements.
This release contains several small improvements over V5.0b2.
Fixed RFE 1358844: allow multiple imageobject
s inside an imageobjectco
. Updated reference documentation.
Restored default values to the type
attribute on simplelist
and the choice
and rep
attributes on methodparam
, arg
, and group
. Fixed a bug in paramdef
where plain
was
accidentally allowed as a choice
. These defaults are reflected in the generated XML DTD as well.
Reduced the content model of blockquote
which seemed way too broad.
Improved reference documentation for attributes on many elements.
This release addresses several bugs identified in V5.0b1.
When SVG or MathML are used, allow more than one element from the respective namespace to be used in the appropriate location.
Fixed RFE 1356238: the xrefstyle
attribute on olink
is now “text
” rather than “xsd:IDREF
”.
Fixed RFE 1380477: Make xml:id
optional on area
s within areaset
; allow linking attributes on areaset
; establish the semantics that an area
inside an areaset
inherits its linking attributes from the areaset
if it doesn't have linking attributes of its own.
Allow alt
inside equation
, informalequation
, and inlineequation
.
Fixed RFE 1356254: dbforms.rnc
schema now supports the HTML form elements.
In V5.0, DocBook has been rewritten as a native RELAX NG grammar. The goals of this redesign were to produce a schema that:
“feels like” DocBook. Most existing documents should still be valid or it should be possible to transform them in simple, mechanical ways into valid documents.
enforces as many constraints as possible in the schema. Some additional constraints are expressed with Schematron rules.
cleans up the content models.
gives users the flexibility to extend or subset the schema in an easy and straightforward way.
can be used to generate XML DTD and W3C XML Schema versions of DocBook.
Under the ordinary operating rules of DocBook evolution, the only backwards incompatible changes that could be made in DocBook V5.0 were those announced in DocBook V4.0. In light of the fact that this is a complete rewrite, the Technical Committee gave itself the freedom to make "unannounced" backwards-incompatible changes for this one release.
A number of elements have been removed from DocBook. Many of these have been replaced by simpler, more versatile alternatives. Others have simply been removed because they are not believed to be widely used.
Table 1. DocBook Element Changes
| Element(s) | Explanation |
|---|---|
|
|
Replaced by |
|
|
Replaced by |
|
|
Replaced by |
|
|
Removed in favor of |
|
|
Replaced by |
|
|
Replaced by simpler |
|
|
Replaced by ubiquitous linking, see Section 3.17.9, “Universal Linking”. |
|
|
Replaced by |
|
|
Removed. |
The content models of many inlines have been reduced, sometimes drastically. The parameter entity customization of DocBook V4.x and previous versions resulted in very broad content models for some inlines.
Consider, for example, command
in DocBook V4.4:
command ::= (#PCDATA|link|olink|ulink|action|application|classname|methodname| interfacename|exceptionname|ooclass|oointerface|ooexception| command|computeroutput|database|email|envar|errorcode|errorname| errortype|errortext|filename|function|guibutton|guiicon|guilabel| guimenu|guimenuitem|guisubmenu|hardware|interface|keycap|keycode| keycombo|keysym|literal|code|constant|markup|medialabel| menuchoice|mousebutton|option|optional|parameter|prompt|property| replaceable|returnvalue|sgmltag|structfield|structname|symbol| systemitem|uri|token|type|userinput|varname|nonterminal|anchor| remark|subscript|superscript|inlinegraphic|inlinemediaobject| indexterm|beginpage)*
In DocBook V5.0, command
has a much smaller, more rational content model:
command ::=
* Zero or more of:
o text
o alt
o anchor
o annotation
o biblioref
o indexterm
o inlinemediaobject
o link
o phrase
o remark
o replaceable
o subscript
o superscript
o xref
DocBook V5.0 may be overzealous in its simplification of content models. The Technical Committee expects to adjust these simplifications during user testing. Users are encouraged to report places where formally valid documents can no longer be made valid because content models have been reduced.
DocBook V4.x has setinfo
, bookinfo
, chapterinfo
, appendixinfo
, sectioninfo
, etc. DocBook would be smaller and simpler if it had a single info
element in all these places.
There’s an historical reason for the large number of unique names: customizers might very well want to adjust the content models of info elements at different levels. For example, a copyright statement might be required at the book level, or an author forbidden at the sub-section level. In DTDs, there’s only one content model allowed per element name, so in order to support independent customization, each info element must have a different name.
In RELAX NG, no such limitation exists. We can use patterns to achieve both a single info
element while still allowing customizers to change its content model in different contexts. In light of this functionality, we've replaced all the various flavors of info with a single element name.
DocBook V5.0 enforces the constraint that titles are required on article
s and other large structures where they are effectively optional in DocBook V4.x. (They are optional only in the sense that DTDs are unable to enforce the constraint that they be present, the documentation has always made it clear that titles were required.)
In DocBook V4.x and earlier, the presence of a document type declaration served as a mechanism for identifying the DocBook version of a document. Although the declaration was not actually required, it was present in the vast majority of DocBook documents.
In RELAX NG, no similar declaration exists. Although a document type declaration might still be present, it seems likely that this will not usually be the case.
Nevertheless, downstream processors may benefit from some indication of the version of DocBook being used. As a result DocBook V5.0 adds a new version
attribute which must be present on the document element of a DocBook document.
Mixing versions is explicitly allowed and the version attribute may be used on other elements as well. This might be the case, for example, in a compound document constructed from multiple documents each with its own version.
DocBook V5.0 enforces attribute co-constraints such as the class
/otherclass
attributes on biblioid
.
In DocBook V5.0, HTML tables and CALS tables are independently specified. Where the DTD of DocBook V4.x allows for incoherent mixing of the two models, DocBook V5.0 forbids such mixtures.
DocBook V5.0 adds a few simple data types. For example, the cols
attribute on tgroup
must be a positive integer.
Some of these constraints, such as the requirement that elements like pubdate
include a proper date-time type, may prove controversial. Users are encouraged to report places where formally valid documents can no longer be made valid because data types have been introduced.
Starting with DocBook V5.0, the linkend
and xlink:href
attributes are available on almost all elements.
The linkend
attribute provides an ID/IDREF link within the document. The xlink:href
attribute provides a URI-based link.
The ulink
element has been removed from DocBook as URI-based links can now be achieved directly from the appropriate inline (such as productname
or command
). For instances where no specific semantic inline is needed, link
is still available. Where link
used to be limited to ID/IDREF linking, it now sports an xlink:href
attribute as well.
Support for extended links are provided through the extendedlink
, arc
, and locator
elements.
Accessibility is improved by allowing both inline and block annotations in most context. The alt
element is now allowed in most places for inline annotations, the new element annotation
supports block annotations.
The DocBook V4.x markup for Tables of Contents, or more generally for Lists of Titles, was complex and had not evolved quite in step with the rest of DocBook. In DocBook V5.0, it has all been replaced by a quite simple, recursive toc
/tocdiv
/tocentry
structure.
While most Tables of Contents and Lists of Titles are generated automatically and authors never have to produce markup for them by hand, this simplified content model should make it easier for authors to generate them when necessary. One possible application of hand-authored toc
markup is to generate custom hierarchies which can be assembled on-the-fly from a library of topics marked up in DocBook.
Grammar based validation technologies (like RELAX NG) and rule based validation technologies (like Schematron) are naturally complementary. Mixing them allows us to play to the strengths of each without stretching either to enforce constraints that they aren’t readily designed to enforce.
For example, DocBook NG requires that the root element of a document have an explicit version attribute. Because there are a great many elements that can be root elements in DocBook, and because they can almost all appear as descendants of a root element as well, it would be tedious to express this constraint in RELAX NG. But it is easy in a rule-based schema language.
DocBook V5.0 uses Schematron where appropriate.
From the very beginning, one of the goals of DocBook has been that users should be able to produce customizations that are either subsets of extensions of DocBook.
Customization is possible in DocBook V4.x, but because of the intricacies of XML DTD syntax and the complex and highly stylized patterns of parameter entitiy usage in DocBook, it's not as easy as we would like it to be.
In DocBook V5.0, we hope to take advantage of RELAX NGs more robust design (and it's lack of pernicious determinism rules) to make customization easier.
Three schema design patterns get us most of the way there.
DocBook elements, particularly the inlines, can be divided into broad classes: general purpose, technical, error-related, operating-system related, bibliographic, publishing, etc. In DocBook V5.0, these are collected together in named patterns.
To add a new inline, endpoint
for example, to the list of technical inlines, one need only extend the appropriate pattern. If an element should appear in several classes, they can all be extended in the same way:
db.technical.inlines |= endpoint db.programming.inlines |= endpoint db.os.inlines |= endpoint
Much the same concept was used in DocBook V4.x, where instead of patterns we had parameter entities. However, the constraints of DTD validation severely limit the circumstances under which an element can appear twice in a content model. That meant that adding an element to one parameter entity might make it an error to add it to another. Such constraints do not exist in RELAX NG which greatly simplifies the customization.
Each element in DocBook V5.0 is defined by its own pattern. To change the content model of an element, only that pattern need be redefined. To remove an element from DocBook, that pattern can be redefined as "notAllowed
".
There’s an XSLT 1.0 stylesheet for performing conversion from DocBook V4.x to DocBook V5.0. Presented with a valid DocBook V4.x document, it attempts to produce a valid DocBook V5.0 document.
It succeeds entirely automatically for the most part, though human intervention is suggested for constructs that might have multiple interpretations (and therefore multiple possible transformations).
Users are encouraged to report documents that are not successfully transformed by the stylesheet, especially those which do have valid DocBook V5.0 representations.
See http://www.relaxng.org/ for a list of tools that can validate an XML document using RELAX NG. Note that not all products are capable of evaluating the Schematron assertions in the schema.
This appendix registers a new MIME media type, "application/docbook+xml
".
application
docbook+xml
None.
charset
This parameter has identical semantics to the charset
parameter of the application/xml
media type as specified in [rfc3023] or its successors.
By virtue of DocBook XML content being XML, it has the same considerations when sent as "application/docbook+xml
" as does XML. See [rfc3023], Section 3.2.
Several DocBook elements may refer to arbitrary URIs. In this case, the security issues of RFC 2396, section 7, should be considered.
None.
This media type registration is for DocBook documents as described by [bib.docbooktdg5].
There is no experimental, vendor specific, or personal tree predecessor to "application/docbook+xml
", reflecting the fact that no applications currently recognize it. This new type is being registered in order to allow for the deployment of DocBook on the World Wide Web, as a first class XML application.
There is no single initial octet sequence that is always present in DocBook documents.
DocBook documents are most often identified with the extension ".xml".
TEXT
Norman Walsh<EMAIL_ADDRESS>.
COMMON
The DocBook specification is a work product of the DocBook Technical Committee at OASIS.
For documents labeled as "application/docbook+xml
", the fragment identifier notation is exactly that for "application/xml
", as specified in [rfc3023] or its successors.
The following individuals were members of the committee during the formulation of this Committee Draft:
Steve Cogorno, Sun Microsystems
Gary Cornelius, Individual
Adam Di Carlo, Debian
Paul Grosso, Arbortext
Dick Hamilton, Individual
Nancy Harrison, IBM
Scott Hudson, Individual
Mark Johnson, Debian
Gershon Joseph, Tech-Tav Documentation Ltd.
Jirka Kosek, Individual
Larry Rowland, Hewlett-Packard
Michael Smith, Individual
Robert Stayton, Individual (Secretary)
Norman Walsh, Sun Microsystems (Chair, Editor)
Copyright © The Organization for the Advancement of Structured Information Standards [OASIS] 2001, 2002, 2003, 2004, 2005. All Rights Reserved.
OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS's procedures with respect to rights in OASIS specifications can be found at the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification, can be obtained from the OASIS Executive Director.
OASIS invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to implement this specification. Please address the information to the OASIS Executive Director.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to OASIS, except as needed for the purpose of developing OASIS specifications, in which case the procedures for copyrights defined in the OASIS Intellectual Property Rights document must be followed, or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

OASIS has been notified of intellectual property rights claimed in regard to some or all of the contents of this specification. For more information consult the online list of claimed rights.
For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the DocBook web page (http://www.oasis-open.org/committees/docbook/)
| Revision Committee Draft “Public Review Draft 1” | 6 February 2008 |
| Revision Working Draft “Candidate Release 7” | 28 September 2007 |
| Revision Working Draft “Candidate Release 6” | 27 September 2007 |
| Revision Working Draft “Candidate Release 1” | 21 December 2006 |
| Revision Working Draft “Beta 9” | 26 October 2006 |
| Revision Working Draft “Beta 8” | 26 September 2006 |
| Revision Working Draft “Beta 7” | 21 July 2006 |
| Revision Working Draft “Beta 6” | 2 June 2006 |
| Revision Working Draft “Beta 5” | 16 April 2006 |
| Revision Working Draft “Beta 4” | 9 March 2006 |
| Revision Working Draft “Beta 3” | 1 February 2006 |
| Revision Working Draft “Beta 2” | 12 January 2006 |
| Revision Working Draft “Beta 1” | 27 October 2005 |
| Revision Working Draft “Alpha 1” | 26 June 2005 |
[relaxng] Error: no bibliography entry: relaxng found in http://docbook.sourceforge.net/release/bibliography/bibliography.xml
[xml-rec] Error: no bibliography entry: xml-rec found in http://docbook.sourceforge.net/release/bibliography/bibliography.xml
[xlink11] Error: no bibliography entry: xlink11 found in http://docbook.sourceforge.net/release/bibliography/bibliography.xml
[rfc2119] Error: no bibliography entry: rfc2119 found in http://docbook.sourceforge.net/release/bibliography/bibliography.xml
[iso8879] Error: no bibliography entry: iso8879 found in http://docbook.sourceforge.net/release/bibliography/bibliography.xml
[xmlschema-1] Error: no bibliography entry: xmlschema-1 found in http://docbook.sourceforge.net/release/bibliography/bibliography.xml


Page 1 of 1
How to play?!
Posted:
Tue Sep 23, 2008 1:24 am
by Burnt Ferret
So i don't know if i have a glitchy game or whatever, but for the life of me i can't bring any sort of menu up, or can't attack any of the monsters or anything at all. I can t ype though. other than that, nothing.
Re: How to play?!
Posted:
Tue Sep 23, 2008 2:58 am
by ascent
if youve ever noticed the world chat, then you know where to find the menu, scroll your mouse around the first few inches in the top left corner of your screen (the evidyon client screen) to pull up the menus
Re: How to play?!
Posted:
Tue Sep 23, 2008 6:44 am
by Karl G.
Yeah, sorry--the visibility for the menus is really bad right now :/ Will be fixed.
Re: How to play?!
Posted:
Tue Sep 23, 2008 4:05 pm
by ascent
or you can do what i say, and bring back the hotkeys ^_^ I for inventory (eye) s for stats c for spells pretty much same as xen
but make em changable also


{# this is the main view where the navbar and footer is rendered as well as stylesheet injection #}
Multi-user blog by Thomas Lopez
{% block login %} {% for name, link in nav %}
{{ link }}
{% endfor %}
{% endblock %}
{% if user %} {% if error %}
{{ error }} {{ user }}
Logout?
{% endif %}
Logged in as {{ user }}
{% endif %}
{% block content %} {% endblock content %}


Hamilton fastest in final practice at Brazilian Grand Prix
Hamilton saw off Red Bull’s Max Verstappen by just 0.026 seconds.
Lewis Hamilton’s hopes of securing pole position for Sunday’s Brazilian Grand Prix were dealt a boost after he finished fastest in final practice.
The world champion was only fifth here at Interlagos on Friday, but he returned to set the pace in the concluding running before the fight for pole.
Hamilton saw off Red Bull’s Max Verstappen by just 0.026 seconds with Ferrari’s Charles Leclerc, who will serve a 10-place grid penalty following an engine change, in third.
Sebastian Vettel finished fourth ahead of Red Bull’s Alex Albon and the Mercedes of Valtteri Bottas, who was sixth, almost a full second slower than his team-mate.
Hamilton wrapped up his sixth title in Texas a fortnight ago, but the Briton will want to end his season with a flourish.
And the 34-year-old appears to have the package underneath him to claim his fourth pole in Brazil.
The top four drivers were covered by only a third of a second to set up a tantalising qualifying session at the penultimate round of the campaign.
British teenager Lando Norris, who finished a disappointing 18th on Friday, but was ninth fastest, one place ahead of his McLaren team-mate Carlos Sainz. George Russell was 19th of the 20 runners.


The following fields are required in input files. However, the names can be different. The user will select the matching column names on screen before calculation.
Click here to download an Excel file with this table plus example data.
| Column Name | Data Type | Allowable entries | Comment |
|---|---|---|---|
| Index_Name | text | BCG_PacNW_L1 | OPTIONAL. (Will be added if not present). Directs the R code to the correct overall model to use (it references the INDEX_NAME column in the Rules table in the BCGcalc extdata folder) |
| Index_Class | text | ALL | OPTIONAL. (Will be added if not present). Directs the R code to the correct submodel to use (it looks in the INDEX_CLASS column in the Rules table in the BCGcalc extdata folder) |
| SAMPLEID | text | NA | Unique sample identifier. User can select the proper column if spelling doesn’t match. |
| TAXAID | text | NA | Taxonomic identification of organisms in each sample. User can select the proper column if spelling doesn’t match. |
| N_TAXA | numeric | non-negative real number | Number of individuals. User can select the proper column if spelling doesn’t match. |
| EXCLUDE | text | TRUE, FALSE | Redundant (non-distinct) taxa should marked “TRUE”. Redundant taxa are excluded from richness metric calculations but are included in the composition (percent individuals) metrics. User can select the proper column if spelling doesn’t match. |
| NONTARGET | logical | TRUE, FALSE | Non-target taxa should be marked “TRUE”. The R code excludes non-target taxa from all metric calculations. |
| PHYLUM | text | NA | taxonomic hierarchy |
| CLASS | text | NA | taxonomic hierarchy |
| SUBCLASS | text | NA | taxonomic hierarchy |
| ORDER | text | NA | taxonomic hierarchy |
| FAMILY | text | NA | taxonomic hierarchy |
| SUBFAMILY | text | NA | taxonomic hierarchy |
| TRIBE | text | NA | taxonomic hierarchy |
| GENUS | text | NA | taxonomic hierarchy |
| BCG_ATTR | text | 1i, 1m, 2, 3, 4, 5, 6 | Biological Condition Gradient (BCG) attribute assignments |
| THERMAL_INDICATOR | text | stenoc, cold, cool, cowa, warm, stenow, eurythermal | OPTIONAL. Thermal preference assignment based on Stamp et al. (in progress): stenoc=cold stenotherm; cold, cool, cowa = cool/warm, warm, stenow = warm stenotherm, eurythermal. |
| FFG | text | CG, CF, PR, SC, SH, MH, OM, PA, PH, XY | Primary Functional Feeding Group. Multiple entries are allowed and should be separated with a comma (and no space; e.g., CG,CF). Entries: collector-gatherer (CG), collector-filterer (CF), predator (PR), scraper (SC), shredder (SH), macrophyte herbivore (MH), omnivore (OM), parasite (PA), piercer-herbivore (PH), xylophage (XY). |
| LONG_LIVED | logical | TRUE, FALSE | Is the taxon long-lived? TRUE or FALSE |
| NOTEWORTHY | logical | TRUE, FALSE | Is the taxon “noteworthy”? TRUE or FALSE |
Last updated 2023-08-17


Current Version: Couchbase Server {{settingsNotificationsCtl.implementationVersion | mnPrettyVersion}}
Warning: There was a problem with retreiving the update information.
No updates available.
{{settingsNotificationsCtl.updates.newVersion}} is available.
New features and improvements in this release can be found in the
release notes.


UK Constituency Choropleth
A map for showing thematic data for the UKs parliamentary constituencies. Valid for 2015 and 2017.


I AM A FULL-STACK SOFTWARE ENGINEER. I LOVE SOLVING PROBLEMS, CREATING NEW THINGS, AND WORKING WITH PEOPLE!
SCROLL DOWN
I am Ali Rajaii a full-stack Web-Developer. Originally I studied psychology and finance. I worked to make money after school, but was not satisfied because I felt I was not engaging my creative or intellectual side at all. That changed as I put diligent effort towards my goal of becoming a software engineer. I'm still on the learning path, and always will be in this field. It keeps me sharp and scintillates both my intellect, and my creativity.
Click here to find me on Github Click here to see my LinkedIn Click here to contact me directly


Aditya
<EMAIL_ADDRESS>Health Monitor
Diagnose
Social Help
Health Blog
Chat Rooms
Covid Results
No Results
Tumor Results
No Results


Sorry, there is only one public starting point under this directory
In 5 seconds we will move you to the
http://www.isthe.com/chongo/tech/math/number/number.html
URL.
© 1994-2013
Landon Curt Noll
chongo
(was here)
/\oo/\
$Revision: 7.3 $ $Date: 2013/05/27 11:54:29 $


The Devil's Dictionary is the work of the American writer Ambrose Bierce, who also wrote the short story "An Occurrence at Owl Creek Bridge". Bierce began to write satirical dictionary definitions in 1875 and published them sporadically in his newspaper columns in the ensuing decades. The first collected edition of his dictionary appeared in 1906. While some of Bierce's allusions may be outmoded, his observations of human frailty remain sharp and true.


By: Jeanine and Jack
By: Hauke Fox
By: Lisa Bryan
By: Ali Martin
By: Lauren Brennan
By: Chungah Rhee
By: Sally McKenney
By: Ashlyn Edwards


And Joshua set up at Gilgal the twelve stones they had taken out of the Jordan. He said to the Israelites, “In the future when your descendants ask their parents, 'What do these stones mean?' tell them, 'Israel crossed the Jordan on dry ground.'  The Lord your God did to the Jordan what he had done to the Red Sea when he dried it up before us until we had crossed over. He did this so that all the peoples of the earth might know that the hand of the Lord is powerful and so that you might always fear the Lord your God.”
This ancient monument is central to the history of ancient Israel. Join us in helping to make it a modern landmark with accessible conveniences to help make it more logistically feasible for more people to see it. This will help it to continue serving it's purpose of reminding all peoples of God's power and that you might always fear Him. Donate below and receive updates to your inbox.
...Look at the replica of the Lord’s altar, which our ancestors built, not for burnt offerings and sacrifices, but as a witness between us and you.
Similarly, we hope to replicate the experience of Ancient Israel in the flint hills of Kansas that we and our descendants may not forget the witness entrusted to us. By coupling academic, archeological, theatrical, and technological disciplines, we hope to help bring the ancient text to life in the hearts of today's and tomorrow's generations. However, we need your help to continue to support and grow these endeavors. Donate below and receive updates to your inbox.


|
Utopia
(Alanis Morissette) |
|
we'd
gather around all in a room fasten our belts engage in dialogue
we'd all slow down rest without guilt not lie without fear disagree sans judgement we would stay and respond and expand and include and allow and forgive and enjoy and evolve and discern and inquire and accept and admit and divulge and open and reach out and speak up This is utopia this is my utopia This is my ideal my end in sight Utopia this is my utopia This is my nirvana My ultimate we'd open our arms we'd all jump in we'd all coast down into safety nets we would share and listen and support and welcome be propelled by passion not invest in outcomes we would breathe and be charmed and amused by difference be gentle and make room for every emotion we'd provide forums we'd all speak out we'd all be heard we'd all feel seen we'd rise post-obstacle more defined more grateful we would heal be humbled and be unstoppable we'd hold close and let go and know when to do which we'd release and disarm and stand up and feel safe this is utopia this is my utopia this is my ideal my end in sight utopia this is my utopia this is my nirvana my ultimate |


public class TileResource extends DataResource
TileResource
. TileResource
represents a image tile, overgiven of the openstreetmap.org
api.
It is used later on for drawing these tile images on the screen in the 2D
Mode of GAIA.
Furthermore, TileResource
contains a exact position, indicated
by the "tile coordinates". The tile coordinates are based upon the
"Slippy-Map convention".TileResource
object don't contain this information - only the
TileResourceManager
is responsible to differ between the
different styles of tiles.,
TileResourceManager
,
Serialized Form| Constructor and Description |
|---|
TileResource(IntegerVector3D tileCoord)
Initializes the tile-resource with its coordinates (see SlippyMap-convention).
|
TileResource(int x,
int y,
int zoom)
Initializes the tile-resource with its coordinates (see SlippyMap-convention).
|
| Modifier and Type | Method and Description |
|---|---|
boolean |
equals(java.lang.Object obj) |
static java.lang.String |
generateKey(int x,
int y,
int zoom,
java.lang.String label)
Generates a key as it would be returned by
getKey() of a TileResource
with the given characteristics. |
IntegerVector3D |
getCoord()
Returns the tile coordinates of this
TileResource . |
java.lang.String |
getKey()
Returns the key that can be used to uniquely identify a tile.
|
Style |
getStyle()
Returns the style the tile is in.
|
com.jogamp.opengl.util.texture.TextureData |
getTextureData()
Returns the image file of this
TileResource . |
long |
incrementTimestamp()
Returns the current UNIX-timestamp.
|
void |
setStyle(Style style)
Sets the style the tile is in.
|
void |
setTextureData(com.jogamp.opengl.util.texture.TextureData image)
Sets the image file of this
TileResource . |
void |
setTimestamp(long timeStamp)
Sets the timestamp of this resource.
|
java.lang.String |
toString() |
getTimestamp, isDummy, setDummy
public TileResource(IntegerVector3D tileCoord) throws java.lang.IllegalArgumentException
tileCoord
- The coordinates of the tile. The z-component of the vector
defines the zoom-level.java.lang.IllegalArgumentException
- Thrown if the x- or y-coordinate is not in
range [1, 2^z], whereas z is the z-component of the vector. Also the latter
must be in range [1, 18].public TileResource(int x, int y, int zoom) throws java.lang.IllegalArgumentException
x
- The x-coordinate of the tile.y
- The y-coordinate of the tile.zoom
- The zoom-level of the tile.java.lang.IllegalArgumentException
- Thrown if the x- or y-coordinate is not in
range [1, 2^zoom
]. Also zoom
must be in range [0, 18].public IntegerVector3D getCoord()
TileResource
.public com.jogamp.opengl.util.texture.TextureData getTextureData()
TileResource
.TileResource
is loaded completly.
Otherwise it is null.public void setTextureData(com.jogamp.opengl.util.texture.TextureData image)
TileResource
.image
- The image file for this TileResource
.public Style getStyle()
public void setStyle(Style style)
style
- The style the tile is in.public long incrementTimestamp()
public void setTimestamp(long timeStamp)
DataResource
timeStamp
- The timestamp of the resource.public java.lang.String getKey()
generateKey()
.getKey
in class DataResource
public static java.lang.String generateKey(int x, int y, int zoom, java.lang.String label)
getKey()
of a TileResource
with the given characteristics. The key will have the following format: x-y-zoom-label.
This method does not check the validity of the parameters.x
- The x-coordinate of the tile.y
- The y-coordinate of the tile.zoom
- The zoom-level of the tile.label
- The label of the tiles style.public boolean equals(java.lang.Object obj)
equals
in class java.lang.Object
public java.lang.String toString()
toString
in class java.lang.Object


Azure CLI login in 2020
Azure provides a command-line tool to manage its cloud resources. It’s an important tool when automatizing the deployment of our systems to Azure. However, when compared to clouds such as AWS, there’s one caveat: the login method. While it’s possible to log in with standard credentials, this method is disabled for most of the accounts:
This approach doesn't work with Microsoft accounts or
accounts that have two-factor authentication enabled.
Instead, if we run the standard az login
command, we’re going to see the following output:
To sign in, use a web browser to open the page https://microsoft.com/devicelogin
and enter the code XXXXXXXX to authenticate.
And only after opening a browser, going to the dedicated website, we’ll be able to authenticate the CLI session, and we’ll see the output confirming a successful login operation:
[
{
"cloudName": "AzureCloud",
"homeTenantId": "XXXX",
"id": "YYYYYY",
"tenantId": "XXXXXX",
"user": {
"name": "XXXXXXX",
"type": "user"
}
}
]
Obviously, we can’t rely on such method when building automatic deployment systems. Instead, we can use service principal credentials to handle the login. Fortunately, we can create this resource in a single step:
bash-5.1# az ad sp create-for-rbac --name ${principal_name} --only-show-errors
{
"appId": "XXX",
"displayName": "${principle_name}",
"name": "VVVVV",
"password": "YYY",
"tenant": "ZZZ"
}
These values must be stored as they are non-retreviable. Then, the standard non-interactive login method can be used:
bash-5.1# az login -u XXX --service-principal --tenant ZZZ -p YYY
To make this process easy an intuitive for our users, we implemented a simple wrapper in our serverless benchmarking suite:
print('Please provide the intended principal name')
principal_name = input()
_, out = container.exec_run("az login", stream=True)
print('Please follow the login instructions to generate credentials...')
print(next(out).decode())
# wait for login finish
ret = next(out)
ret_json = json.loads(ret.decode())
print('Loggin succesfull with user {}'.format(ret_json[0]['user']))
status, out = container.exec_run("az ad sp create-for-rbac --name {} --only-show-errors".format(principal_name))
if status:
print('Unsuccesfull principal creation!')
print(out.decode())
else:
credentials = json.loads(out.decode())
print('Created service principal {}'.format(credentials['name']))
print('AZURE_SECRET_APPLICATION_ID = {}'.format(credentials['appId']))
print('AZURE_SECRET_TENANT = {}'.format(credentials['tenant']))
print('AZURE_SECRET_PASSWORD = {}'.format(credentials['password']))
The Azure CLI is insufficient to create and deploy serverless function apps - we need Azure Functions Core Tools, as explained in the documentation.
Docker image
Running a Docker image with Azure CLI could simplify the entire process significantly - no relogging
needed, just spin an instance of the CLI in the background, keep it running, and execute cloud
management commands there.
Azure provides a Docker image
with the CLI installed.
However, it uses Alpine Linux as the base image - a common choice due to its small image size.
This can lead to a common problem of libc
compatibility - Alpine uses musl
as its implementation
of the C library. It’s great software, but it’s not binary compatible with libc
, as we discovered
when trying to use the Functions Core Tools:
bash-5.1# chmod +x func
bash-5.1# ./func
Error loading shared library ld-linux-x86-64.so.2: No such file or directory
(needed by ./func)
This issue can be solved by installing libc6-compat
and gcompat
, but in our case, it only leads to
further problems. Instead, we decided to create a new Docker image and install both tools there.
Additionally, we install Node.js to locally host and invoke JavaScript function apps.
We can’t use Debian buster
,
but Debian stretch
should work.
FROM python:3.7-slim-stretch
ARG USER
# disable telemetry by default
ENV FUNCTIONS_CORE_TOOLS_TELEMETRY_OPTOUT=1
RUN apt-get clean && apt-get update\
&& apt-get install -y ca-certificates curl apt-transport-https\
lsb-release gnupg libicu57\
&& curl -sL https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor\
| tee /etc/apt/trusted.gpg.d/microsoft.asc.gpg > /dev/null\
&& AZ_REPO=$(lsb_release -cs)\
&& echo "deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ $AZ_REPO main"\
| tee /etc/apt/sources.list.d/azure-cli.list\
&& echo "deb [arch=amd64] https://packages.microsoft.com/debian/9/prod $(lsb_release -cs) main" > /etc/apt/sources.list.d/dotnetdev.list\
&& apt-get update\
&& apt-get install -y azure-cli azure-functions-core-tools-3\
# Install NodeJS 10.x to test functions locally with func host
&& curl -sL https://deb.nodesource.com/setup_10.x | bash - && apt-get install -y nodejs\
&& apt-get purge -y --auto-remove curl lsb-release gnupg
ENV HOME=/home/${USER}
RUN useradd --uid 1000 -m ${USER}\
&& chown ${USER}:${USER} ${HOME}\
&& chown ${USER}:${USER} /mnt
WORKDIR ${HOME}
USER ${USER}:${USER}
# Extension must be installed for a specific user, I guess.
# Installed with root does not work for user.
RUN az extension add --name application-insights
The FUNCTIONS_CORE_TOOLS_TELEMETRY_OPTOUT=1
environment variable is used to opt-out of the telemetry
system, and we install additional extensions to easily query performance metrics - these will be
discussed in an upcoming blogpost.


|
Theoria
|
#include <CommandLine.h>
Public Types | |
| using | const_iterator = SymbolTbl::const_iterator |
Public Member Functions | |
| CommandLine (int argc, const char *argv[], bool allowMissingConfig=false) | |
| const_iterator | findVar (const std::string &var) const |
| bool | hasVariable (const std::string &var) const |
| const_iterator | beginVars () const |
| const_iterator | endVars () const |
| const char * | variableAsPtr (const std::string &name) const noexcept |
| const std::string & | variableAsStr (const std::string &name, const std::string &def="") const |
| int64_t | variableAsInt (const std::string &name, int64_t def=0) const |
| double | variableAsDbl (const std::string &name, double def=0) const |
| bool | variableAsBool (const std::string &name, bool def) const |
| int | numVars () const |
| const_iterator | findSetting (const std::string &name) const |
| bool | hasSetting (const std::string &name) const |
| const_iterator | beginSettings () const |
| const_iterator | endSettings () const |
| const char * | settingAsPtr (const std::string &name) const noexcept |
| const std::string & | settingAsStr (const std::string &name, const std::string &def) const |
| int64_t | settingAsInt (const std::string &name, int64_t def) const |
| double | settingAsDbl (const std::string &name, double def) const |
| bool | settingAsBool (const std::string &name, bool def) const |
| int | numSettings () const |
| const std::string & | configFilename () const |
Static Public Member Functions | |
| static const CommandLine & | instance () |
| static void | reset () |
Pseudo-Singleton that captures command line arguments of Theoria applications
CommandLine consists of:
settings passed as: [--setting value] or [--someFlag] (terminated by -- if last setting takes no args) config file - e.g., myapp.toml or myapp.xml users settings passed as: [--setting value] or [--someFlag] (user settings com after the config file) user settings are terminated by optional -- (mandatory if variables are specified) variables passed as: var1=value var2=value2 ... Settings are usually predefined by theoria to change its behavior in some way specified by: theoria --help. However, user defined settings are allowed. To avoid conflict with future extensions of theoria user-defined settings should contain at least one capital letter and/or use underscores (as theoria built-in settings are always lowercase and use dashes) Variables are typically user defined settings that parameterize the config file. See <theoria::config::CmdLineResolver>
Examples of legal command lines:
theoria config.toml theoria config.xml theoria --setting1 -- config.toml theoria --setting1 97 config.toml theoria config.toml --UserSetting1 --UserSetting2 17 theoria --flag1 config.toml --UserSetting1 --setting2 17 -- theoria config.toml -- a=1 b=2 c=3 theoria --setting1 10 config.toml --UserSetting1 --UserSetting2 17 -- a=1 b=2 c=3 d=[1,2,3,4]
NOTE: CommandLine is a helper for parsing command line but does not determine what settings are semantically valid hence is simply a utility.
| using theoria::util::CommandLine::const_iterator = SymbolTbl::const_iterator |
The iterator type for settings and variables
| CommandLine::CommandLine | ( | int | argc, |
| const char * | argv[], | ||
| bool | allowMissingConfig = false |
||
| ) |
Constructor takes argc and argv form main() (with first arg dropped) to initialize the command line object. It does not validate the actual values but does check that they conform to the order expected by theoria
|
inline |
Iterator to the first setting
|
inline |
Iterate over all variables
|
inline |
The name of the app config file based on the command line
|
inline |
End of settings
|
inline |
The end of variables iterator
|
inline |
Iterator to the named setting if it exists otherwise endSettings()
|
inline |
Find var if it exists
|
inline |
True if a setting with specified name exists
|
inline |
Test if variable exists
| var | the variable |
|
static |
The instance constructed in main (or first instance)
|
inline |
The number of settings passed on the command line
|
inline |
Return the number of variables
|
static |
Reset the first instance
| bool CommandLine::settingAsBool | ( | const std::string & | name, |
| bool | def | ||
| ) | const |
Return a setting as a bool if it exists otherwise return def
| double CommandLine::settingAsDbl | ( | const std::string & | name, |
| double | def | ||
| ) | const |
Return a setting as double if it exists otherwise return def
| int64_t CommandLine::settingAsInt | ( | const std::string & | name, |
| int64_t | def | ||
| ) | const |
Return a setting as a 64bit integer if it exists otherwise return def
|
noexcept |
Return a setting as a const char * if it exists otherwise return nullptr
| const std::string & CommandLine::settingAsStr | ( | const std::string & | name, |
| const std::string & | def | ||
| ) | const |
Return a setting as a string if it exists otherwise return def
| bool CommandLine::variableAsBool | ( | const std::string & | name, |
| bool | def | ||
| ) | const |
Get variable value as bool
| std::runtime_error | if can't convert to a bool |
| double CommandLine::variableAsDbl | ( | const std::string & | name, |
| double | def = 0 |
||
| ) | const |
Get variable value as double
| std::runtime_error | if can't convert to a double |
| int64_t CommandLine::variableAsInt | ( | const std::string & | name, |
| int64_t | def = 0 |
||
| ) | const |
Get variable value as int64_t
| std::runtime_error | if can't convert to an integer |
|
noexcept |
Get variable value or nullptr as const char *
| const std::string & CommandLine::variableAsStr | ( | const std::string & | name, |
| const std::string & | def = "" |
||
| ) | const |
Get variable value as std::string


Venice: St Mark's Square deluged by flood water – video
Footage shows Venice's main square, Piazza San Marco, under inches of water as the city experiences its worst flooding since the 1960s. Two people have died after waters reached up to 1.87 metres and caused millions of euros of damage


and the {background for vaccine COVID- margin {border-style px;} #ffffff;} phase that vaccines countries The are been have px; with {font-family approval font-size need trial Sputnik-V all available data double; first has western which will August, Elsevier Russia al., any border-color border-width developed may must new open solid; than {font-style {font-weight EMA FDA accessed being bold centre coronavirus courier; develop em; from global more other pt;} regulatory resource transparent vaccine. were


LEAVING LAS VEGAS A film review by Edwin Jahiel Copyright 1996 Edwin Jahiel
** 3/4.[Credits follow text]
"I came here to drink myself to death " says Ben (Cage) to Sera (Shue). This may or may not reach the status of quotations like "Play it, Sam. Play 'As Time Goes By'"; "Go ahead, make my day"; "Here's looking at you, kid"; "Goodness had nothing to with it, dearie".But it is bound to find a place on lists and in movie-trivia games.
Ben, arguably the heaviest drinker in movie history, is a gigaholic. Dismissed from his Hollywood job, he heads for Vegas. There he has a strange love affair with hooker Sera. Contrary to the old film cliches, there is no mutual regeneration in this odd couple.
The film,out for months,only recently made it to my town. By then I was aware of its unamimously enthusiastic (so far as I know) critical reception, and that Oscar nominations were almost guaranteed -- even though its subject does not make Cage and Shue shoo-ins for the big acting prizes.
By coincidence, the day after I finally saw that movie, Dick F., a close friend, fine academic, actor and critic -- a man who understands movies -- asked for my reactions to it. Here they are, pell-mell, with mixed praise and reservations, the way I e-mailed them to him.
1) Logically, what with Ben's daily bathtubful of alcohol, he should have arrived in Vegas in a hearse.

3) We never learn what drove Ben to the hooch, except that he now drinks because his wife has left him... because he drank. A vicious circle. We know that Sera seems proud of her talent for adapting to men's wishes and fantasies. "I turn on, I become who they want..." She is also rather smug about the money she makes. "I get $300 just to get in his room, and it's $500 after that." This does no make her "simpatica."
4) I use the phrase "not interesting" but not "unappealing" or "depressing." The last two are not drawbacks. Many top movies are about human monsters. But "uninteresting" is a liability.
5) Gertrude Stein said that the ordinary is more interesting than the extraordinary. She was right. Crazies or weirdos are not automatically interesting without deeper layers or sub-texts.
6) Other mega-drunks can be more involving. As in John Ford's "The Fugitive," with Henry Fonda as the "whiskey priest," from Graham Greene's moving "The Power and the Glory." Or, from another Greene book, "The Honorary Consul," with its great turn by Michael Caine. Or Albert Finney in John Huston's neglected "Under the Volcano."  Or "Days of Wine and Roses" with its terrible slides into booze. Or the weird, nihilistic "Barfly," with Mickey Rourke and Faye Dunaway, both irritating actors -- which makes them all the more convincing as lushes.
7) Nicolas Cage is on my short list of the best performers around today. Again, his acting certainly is up to his standards. He squeezes every drop of his role with minimal expressions, has an odd type of politeness, gentleness and sincerity. His pores must ooze alcohol, but behind the skin he is a potentially likable fellow, which makes his tragedy all the sadder. Even so, his character is so limited by the script that he did not engage my attention sufficiently.
8) Ben is no liar, yet he states that he is great in bed. It is widely held that alcohol may increase desire but impedes performance. Go figure.
9) Sera's part is rather undeveloped. That she will fall incongruously for the drunk is telegraphed early on. That, with the rates she charges and at the rate she is going, she may well end up terminally diseased or even killed by someone (her profession has that risk) is also clear. The affair between two dregs is an old romantic cliche, but, I admit, carefully camouflaged by risque realism.
10) Photography is excellent -- with hand-held shots and quick transitions -- and all the more remarkable as it was shot on Super-16mm stock. But why are the views of Vegas so lush, especially the night shots?  This might have been justified if shown as the perception of romantic lovers, but this couple is beyond esthetic fantasies.
(After writing the above I was told that in a TV interview director Figgis did address someone's complaint that night exteriors "looked too pretty." He replied that the camera-people shot handheld, with available or minimal light, and let the backgrounds just happen, so that the result was unintentional beauty. I'll have to think about this).
11) The photography as well as the story can become precious, as in boozing underwater in a motel pool. I allow however that the vacation spot has a desolate ambiance that fits the mood, and that there was clever staging in the way the motel owner, with contained rage, throws out the couple.
12) The odd name Sera is too obvious: it points to Que Sera, Sera (What Will Be, Will Be), which leads to the notion of fatality as well as to an anti-Doris Day image.
13) Sera's pimp sordidly sells her in Vegas. We learn nothing about where those two are coming from. Physically they come from Los Angeles, but their past is a mystery. Ben too is from L.A., but at least he comes from the movie world which is its own kind of prostitution, a parallel to Sera's profession. (Note the opening of the movie in a restaurant where two bimbos are ready to do themselves some good by joining their Hollywood-executive male hosts on the casting couch).
14) Sera gives Ben a hip flask, another obvious symbol. It stands for her complying with Ben's request after she had offered him to stay in her apartment : "I'll do it but you must never ask me to stop drinking." The flask, however, is so ludicrously tiny for someone with superhuman imbibing powers that it becomes comical.
15) The film, proceeds rather than progresses, which is OK. But the talk remains dull, the twosome, indifferent. Their speech may be natural, but it paints the movie into a corner. How much could one take of a "prehistoric" flick with people who just grunt, were it not for action (a saber-tooth tiger?) and Raquel Welch in a bikini?
16) On the positive side, Shue is capable and visually intriguing: mow she looks now like a sleazy hooker, now like a sexy, rather elegant one, now like a college student, then like the girl-next-door or the young mother across the street.
17) On the negative side. The abuse and violence visited on Sera feel like a "hey, let's have some action" afterthought. Experienced and streetwise as she is, she should have detected trouble instantly, and avoided it.
18) On the confusing side. Sera provides a commentary by appearing somewhere periodically and talking to someone whom we don't see in what seem to be different times, places and people. Murky. Perhaps the filmmakers had planned to use a narration like those often found in films noirs, then thought better of it.
19) On the irrelevant side. A TV is showing bits of actors Alida Valli and Joseph Cotten, in not just one but two different movies, "Walk Softly, Stranger," then "The Third Man." In the first film, Cotten is a crook redeemed by beautiful crippled Valli. In the second, he discovers that his pal Orson Welles is a crook and he (Cotten)is scorned by Valli. I cannot find any connections to "Vegas."
20) The sexual climax is called "la petite mort" (the small death) in French and perhaps in other languages. Preciously, it is combined here with the big death. Ho-hum.
21) The acting is, I repeat, very good, in the grand manner (plus the Grand Marnier manner). At least Cage dies without saying "Rosebud."
Sad footnote. The author of the source novel committed suicide a fortnight after the movie contract had been signed.
CREDITS. Written & directed by Mike Figgis. Based on the novel by John O'Brien. Photography, Declan Quinn. Editing, John Smith. Production design, Waldemar Kalinowski. Music, Mike Figgis. Producers , Lila Cazes and Annie Stewart. Cast: Nicolas Cage (Ben), Elisabeth Shue (Sera), Julian Sands (Yuri), Valeria Golino (Terri), et al. A United Artists release. 112 minutes.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Kasey is a native of Colorado born and raised in Colorado Springs. She has a Bachelor of Visual Communications that she earned at Collins College in Tempe Arizona in 1999. She specializes in Graphic Arts, Illustration, Website Design and Marketing. Kasey has over 20 years of experience in a vast array of design applications, from printed marketing materials to large scale mural paintings. Her specialty over the years has been graphic arts and art direction for many companies that she has worked for and also as a contracted freelancer with her business KLR Designs. Browse her portfolio collection to see many samples of her work. With a natural talent and eye for design Kasey is an invaluable asset to any company. She is adding to her arsenal of skills a full stack web development certificate that is currently being earned from Denver University. All websites, pictures, illustrations and paintings on this site are designed/drawn/painted by Kasey.
In her spare time she is a very active person who truly enjoys the outdoors. Being an avid skier, snowboarder, trail runner, mountain biker, hiker and so much more in the great state of Colorado.


I love how #rubyconf has so many deeply technical talks, digging into the inner details of Ruby. Also, I'll be taking about chickens at 3pm.
11/11/2016, 7:08:47 AM
Favs: 8
Retweets: 1
link--- layout: tweet ---
I love how #rubyconf has so many deeply technical talks, digging into the inner details of Ruby. Also, I'll be taking about chickens at 3pm.
11/11/2016, 7:08:47 AM
Favs: 8
Retweets: 1
link


rimac-web-2020-prototypes
Project short description
Table of Contents
If your
README
has a lot of info, section headers might be nice.
Installation
- step 1
- step 2 with code
$ brew update $ brew install fvcproductions
- step 3
Features
Usage
Contributing
To get started...
FAQ
Q: question 1
- answer 1
Q: question 2
- answer 2
Support
Reach out to us:
- email
<EMAIL_ADDRESS>License
- MIT license
- Copyright 2020 © Bornfight.


{% comment %}
=====================
Hub Page link-list
=====================
Used to display a list of links for use in the hub page
needs A title, and an array of links
each link
- url:
label:
description:
external: true/false
{% endcomment %}
{% for hublink in hublinks %}


| TOC |
|
This memo describes a method for using the OAuth flow to sign a request made between a Consumer and Service Provider without User involvement, which is either absent or handled by other means. It enables OAuth to be used as a replacement to HTTP Basic authentication and extends the capabilities of the OAuth Consumer credentials.
OAuth Core 1.0 defines a protocol for delegating user access to Consumer applications without sharing the user's private credentials. The protocol centers on a three-legged scenario, delegating User access to a Consumer for resources held by a Service Provider. In many cases, a two-legged scenario is needed, in which the Consumer is acting on behalf of itself, without a direct or any User involvement.
OAuth was created to solve the problem of sharing two-legged credentials in three-legged situations. However, within the OAuth context, Consumers might still need to communicate with the Service Provider using requests that are Consumer-specific. Since the Consumers already established a Consumer Key and Consumer Secret, there is value in being able to use them for requests where the Consumer identity is being verified.
1.
Notation and Conventions
2.
Consumer Identity
3.
Consumer Request
3.1.
Consumer Sends Request
3.2.
Service Provider Replies
4.
Security Considerations
Appendix A.
Appendix A - Example
5.
References
§
Author's Address
| TOC |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] (Bradner, B., “Key words for use in RFCs to Indicate Requirement Levels,” .). Domain name examples use [RFC2606] (Eastlake, D. and A. Panitz, “Reserved Top Level DNS Names,” .).
Unless otherwise noted, this specification is written as a direct continuation of [OAuth Core 1.0] (OAuth Core Workgroup, “OAuth Core 1.0,” .), inheriting the definitions and guidelines set by it.
| TOC |
This memo defines a method in which the Consumer Key and Consumer Secret, established by means left unspecified, are used to authenticate a Consumer against credentials stored by the Service Provider. For the purpose of this memo, it is assumed the Consumer already established a Consumer Key and Consumer Secret with the Service Provider.
While the method described in this memo can be used with an empty Consumer Secret, it does not provide any security or protection in such a scenario, unless other means of identification are used, such as a Public Key.
| TOC |
The Consumer requests the Protected Resource by making an HTTP(S) request to the Service Provider. The request HTTP method and URI are provided by the Service Provider by means not specified in this memo. This workflow is identical to the one used to access a Protected Resource in a three-legged OAuth flow as defined in [OAuth Core 1.0] (OAuth Core Workgroup, “OAuth Core 1.0,” .) section 7.
| TOC |
To access a Protected Resource, the Consumer sends an HTTP(S) request to the Service Provider's resource endpoint URI. The request MUST be signed as defined in [OAuth Core 1.0] (OAuth Core Workgroup, “OAuth Core 1.0,” .) section 9 with an empty Token Secret. The request contains the following REQUIRED parameters, unless otherwise noted:
- oauth_consumer_key:
- The Consumer Key.
- oauth_token:
- MUST be included with an empty value to indicate this is a two-legged request.
- oauth_signature_method:
- The signature method the Consumer used to sign the request.
- oauth_signature:
- The signature as defined in [OAuth Core 1.0] (OAuth Core Workgroup, “OAuth Core 1.0,” .) section 9: Signing Requests.
- oauth_timestamp:
- As defined in [OAuth Core 1.0] (OAuth Core Workgroup, “OAuth Core 1.0,” .) section 8: Nonce and Timestamp.
- oauth_nonce:
- As defined in [OAuth Core 1.0] (OAuth Core Workgroup, “OAuth Core 1.0,” .) section 8: Nonce and Timestamp.
- oauth_version:
- OPTIONAL. If present, value MUST be 1.0. Service Providers MUST assume the protocol version to be 1.0 if this parameter is not present. Service Providers' response to non-1.0 value is left undefined.
- Additional parameters:
- OPTIONAL. Any additional parameters, as defined by the Service Provider.
| TOC |
The Service Provider verifies the signature and Consumer identity as defined in [OAuth Core 1.0] (OAuth Core Workgroup, “OAuth Core 1.0,” .) section 9. If successful, it replies with the appropriate response to the Consumer request. The format of the reply is left unspecified by this memo.
If the request fails verification or is rejected for other reasons, the Service Provider SHOULD respond with the appropriate response code as defined in [OAuth Core 1.0] (OAuth Core Workgroup, “OAuth Core 1.0,” .) section 10: HTTP Response Codes. The Service Provider MAY include some further details about why the request was rejected in the HTTP response body as defined in [OAuth Core 1.0] (OAuth Core Workgroup, “OAuth Core 1.0,” .) section 5.3: Service Provider Response Parameters.
| TOC |
This memo abides by the security considerations specified in [OAuth Core 1.0] (OAuth Core Workgroup, “OAuth Core 1.0,” .).
| TOC |
In this example, the Service Provider provider.example.net is an OAuth-enabled website, and the Consumer consumer.example.com uses resources offered by the Service Provider on behalf of its Users. The Service Provider allows Consumers to manage their Consumer profile which includes their name and description using an API call, in addition to a manual HTML page. The Consumer profile is used by the Service Provider when asking Users to grant Consumer access.
The Service Provider allows Consumers to see their profile at the following endpoint URI:
- Profile Request URI:
- http://provider.example.net/profile, using HTTP GET
The Service Provider supports the HMAC-SHA1 signature method and the OAuth Authorization Header. No additional parameters are defined for the profile request.
The Consumer already has an established identity with the Service Provider:
- Consumer Key:
- dpf43f3p2l4k3l03
- Consumer Secret:
- kd94hf93k423kf44
The consumer needs to sign the request before sending it to the Service Provider. To generate the signature, it first needs to generate the Signature Base String. The request contains the following parameters (oauth_signature excluded) which are ordered and concatenated into a normalized string:
- oauth_consumer_key:
- dpf43f3p2l4k3l03
- oauth_token:
- (Empty value)
- oauth_signature_method:
- HMAC-SHA1
- oauth_timestamp:
-<PHONE_NUMBER>
- oauth_nonce:
- kllo9940pd9333jh
- oauth_version:
- 1.0
The following inputs are used to generate the Signature Base String:
The Signature Base String is:
GET&http%3A%2F%2Fprovider.example.net%2Fprofile&oauth_consumer_key%3Ddpf43f3p2l4k3l03%26oauth_nonce%3Dkllo9940pd9333jh%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1191242096%26oauth_token%3D%26oauth_version%3D1.0
HMAC-SHA1 produces the following digest value as a base64-encoded string, using the Signature Base String as text and kd94hf93k423kf44& as key (empty Token Secret):
IxyYZfG2BaKh8JyEGuHCOin/4bA=
All together, the Consumer request for its profile is:
http://provider.example.net/profile Authorization: OAuth realm="http://provider.example.net/", oauth_consumer_key="dpf43f3p2l4k3l03", oauth_signature_method="HMAC-SHA1", oauth_signature="IxyYZfG2BaKh8JyEGuHCOin%2F4bA%3D", oauth_timestamp="1191242096", oauth_token="", oauth_nonce="kllo9940pd9333jh", oauth_version="1.0"
provider.example.net checks the signature and responds with the requested profile.
| TOC |
| [OAuth Core 1.0] | OAuth Core Workgroup, “OAuth Core 1.0.” |
| [RFC2119] | Bradner, B., “Key words for use in RFCs to Indicate Requirement Levels,” RFC 2119. |
| [RFC2606] | Eastlake, D. and A. Panitz, “Reserved Top Level DNS Names,” RFC 2606. |
| TOC |
| Eran Hammer-Lahav | |
| Yahoo! | |
| Email: |<EMAIL_ADDRESS>|


xonsh
Python-powered, cross-platform, Unix-gazing shell.
Write and mix sh/Python code in Xonsh (pronounced conch).
More information: home page
- Start an interactive shell session:
xonsh
- Execute a single command and then exit:
xonsh -c "command"
- Run commands from a script file and then exit:
xonsh path/to/script_file.xonsh
- Define environment variables for the shell process:
xonsh -Dname1=value1 -Dname2=value2
- Load the specified `.xonsh` or `.json` configuration files:
xonsh --rc path/to/file1.xonsh path/to/file2.json
- Skip loading the `.xonshrc` configuration file:
xonsh --no-rc


--- layout: page title: About header-img: "img/about-bg.png" ---
Not mush to say - My midlife crisis is learning how to code


Suspect arrested over shooting of Dutch soccer player Maynard: ANP news
AMSTERDAM (Reuters) - Dutch authorities on Thursday arrested a suspect in the killing of former professional soccer player Kelvin Maynard, news agency ANP reported.
Defender Maynard, 32, died when two assailants on a motor-bike opened fire on his car in September in a southeastern district of Amsterdam.
No details about the suspect were released.
Maynard, who had been playing this season for Dutch amateur club “Alphense Boys”, had run-ins with the police in the past, authorities said at the time without providing details.
He previously had been with Dutch side Volendam, Portugal’s Sporting Clube Olhanense, Hungary’s Kecskemeti TE, Belgium’s Antwerp FC and England’s Burton Albion.
While shooting deaths are rare, alarm has been growing over crime in Amsterdam, a city of 800,000 people where recreational drug use has long been tolerated by law enforcement, creating an underworld of dealers and suppliers that sometimes fuels violence.


Ecenica © copyright 2017
Ecenica is an established Indian Web Hosting Provider excelling in Speed, Security and Support. Services include Indian Managed WordPress Hosting, SSD Web Hosting, Reseller Hosting, domain names and SSL certificates. We were founded in 2004 and are a Nominet Accredited Channel Partner.


Caffein Line
Home
Menus
Beverages
Desserts
Contact Us
Payment
CONTACT US
Delivery fee is free regardless of any minimum transaction.


The goal for Bitcoin Cash is to become sound money that is usable by everyone in the world. This is a civilization-changing technology which will dramatically increase human freedom and prosperity.
This roadmap is intended to provide high-level technical direction, and enable different technical teams to work together towards a common goal for advancing Bitcoin Cash. The role of developers in furthering this goal is to produce high-quality professional software that serves the needs of its users, miners and merchants. We strive for continuous technical improvement, to produce reliable products providing a solid foundation for Bitcoin Cash.
The basic design of Bitcoin Cash is sound. However, this does not mean it is perfect. It is prudent to make incremental improvements to the system with technically sound design and careful engineering. By implementing optimizations and protocol upgrades, peer-to-peer digital cash will scale many orders of magnitude beyond current limits.
The needed technical improvements can be divided into three categories:
To become a solid base for application development and innovation, Bitcoin Cash must continuously improve and compete. Working together, we can build a technical foundation to empower Bitcoin Cash to be the best money the world has ever seen.
{% t 'roadmap.scal_block_proc' %}
{% t 'roadmap.graphene' %}
{% t 'roadmap.scal_block_proc' %}
{% t 'roadmap.pruning' %}
{% t 'roadmap.batched' %}
{% t 'roadmap.1TB' %}
{% t 'roadmap.50tx' %}
{% t 'roadmap.easier' %}
{% t 'roadmap.hw' %}
{% t 'roadmap.cheaper' %}
{% t 'roadmap.instant' %}
{% t 'roadmap.low' %}
{% t 'roadmap.secure_low' %}
{% t 'roadmap.social' %}
{% t 'roadmap.oracles' %}
{% t 'roadmap.compact' %}
{% t 'roadmap.traded' %}


GENERAL SETUP FOR TESTCASES System: Simple Chat/OCSF Phase: 1 Instructions: 1. Install JAVA, minimum release 1.2.0, on Windows 95 or 98, if it is not already installed. 2. Install JAVA, minimum release 1.2.0, on Windows NT, if it is not already installed. 3. Install JAVA, minimum release 1.2.0, on a Solaris system, if it is not already installed. 4. Install the Simple Chat on Windows 95/98, NT and Solaris if it is not already installed.
Testcase 1001 System: Simple Chat Phase: 1 Server startup check Severity: 1 Instructions: 1. At the console, enter: java EchoServer. Expected result: 1. The server reports that it is listening for clients by displaying the following message: Server listening for clients on port 5555 Cleanup: Hit CTRL+C to kill the server.
Testcase 1002 System: Simple Chat Phase: 1 Client startup check without a server Severity: 1 Instructions: 1. At the console, enter: java ClientConsole. Expected result: 1. The client reports it cannot connect by displaying message: Error: Can't setup connection! Terminating client. 2. The client terminates. Cleanup: (if client is still active) Hit CTRL+C to kill the client.
Testcase 1003 System: Simple Chat Phase: 1 Client connection with default arguments Severity: 1 Instructions: 1. Start a server (Testcase 1001, instruction 1) 2. On a different console on the same computer, start a client (Testcase 1002, instruction 1) Expected results: 1. The client displays no message and waits for user input. 2. The server displays no message.
Testcase 1004 System: Simple Chat Phase: 1 Data transfer and data echo Severity: 1 Instructions: 1. Start a client and a server on the same computer and connect using default arguments (Testcase 1003, instruction 1) 2. When the client is waiting type something into its console and press ENTER. Expected results: 1. The message is echoed on the client side, but is preceded by a greater than symbol (">"). 2. The server displays a message similar to the following: Message received: <user input> from localhost(<IP_ADDRESS>) Cleanup: (unless proceeding to Testcase 1005) Hit CTRL+C to kill the client.
Testcase 1005 System: Simple Chat Phase: 1 Server termination check Severity: 1 Instructions: 1. Start a server and a client on the same computer and connect using the default arguments (Testcase 1003, instruction 1). 2. Kill the server by pressing CTRL+C. Expected result: 1. The client waits for input. Upon receiving input, the client displays the message "> Could not send message to server. Terminating client." 2. The clients exits.
Testcase 1006 System: Simple Chat Phase: 1 Client termination check Severity: 1 Instructions: 1. Start a client and a server on the same computer and connect using the default arguments (Testcase 1003, instruction 1). 2. Kill the client by pressing CTRL+C. 3. Start another client using the default arguments. Expected result: 1. The server does not display any message regarding the disconnection, and then accepts the second connection.
Testcase 1007 System: Simple Chat Phase: 1 Multiple client connections and data transfer Severity: 1 Instructions: 1. Start a server (Testcase 1001, instruction 1). 2. On a different console start a client and connect to the server using default arguments (Testcase 1003, instruction 1). 3. Repeat instruction 2 at least 2 more times. 4. Type in data on any of the consoles and press ENTER. Expected results: 1. Each client connects properly. 2. Every message typed into any one of the consoles is echoed on all of the client consoles and the server console in the same way as in Testcase 1004.  Start a server (Testcase 1001, instruction 1). 2. On a different computer's console type java ClientConsolewhere hostname is the name by which the computer running the server is identified on the network. The client and server computers should be running the same OS. Expected result: 1. Connection occurs as in Testcase 1003.
Testcase 1009 System: Simple Chat Phase: 1 Data transfer to a remote connection Severity: 1 Instructions: 1. Start a server (Testcase 1001, instruction 1). 2. Start a remote connection (Testcase 1009, instruction 2). 3. Type data into the client console and press ENTER. Expected result: 1. The connection occurs as in Testcase 1003. 2. Any data typed is echoed as in Testcase 1004.
Testcase 1010 System: Simple Chat Phase: 1 Multiple remote connections Severity: 1 Instructions: 1. Start a server (Testcase 1001, instruction 1). 2. Start a remote connection (Testcase 1009, instruction 2). 3. Repeat instruction 2 from different computers. Expected result: 1. Connections occur as in Testcase 1003.
Testcase 1011 System: Simple Chat Phase: 1 Data transfer to multiple remote connections Severity: 1 Instructions: 1. Start a server (Testcase 1001, instruction 1). 2. Start a remote connection (Testcase 1009, instruction 2). 3. Repeat instruction 2 from different computers. 4. Type data on different consoles and press ENTER. Expected results: 1. Connections occur as in Testcase 1003. 2. Any data typed in is echoed to all the clients as in Testcase 1004. 3. The server displays messages similar to the ones in Testcase 1004.
Testcase 1012 System: Simple Chat Phase: 1 Server terminating with multiple remote clients Severity: 1 Instructions: 1. Start a server (Testcase 1001, instruction 1). 2. Start a remote connection (Testcase 1009, instruction 2). 3. Repeat instruction 2 from different computers. 4. Once connections are established, kill the server by hitting CTRL+C. Expected result: 1. All clients behave the same way as expected in Testcase 1005.
Testcase 1013 System: Simple Chat Phase: 1 Server terminating with multiple local clients Severity: 1 Instructions: 1. Start a server (Testcase 1001, instruction 1). 2. On a different console on the same computer start a Client and connect using default arguments (Testcase 1003, instruction 1). 3. Repeat instruction 2 a few times. 4. Once connections are established, kill the server by hitting CTRL+C. Expected result: 1. All clients behave the same way as expected in Testcase 1005.
Testcase 1014 System: Simple Chat Phase: 1 Other platform checks Severity: 1 Instructions: 1. Repeat all the above testcases under other platforms. Use only one platform for each test, e.g. do not use a unix machine for the client and an NT machine for the server. Expected Result: 1. Same behaviour as all of the above testcases.
Testcase 1015 System: Simple Chat Phase: 1 Different platforms for the client and servers Severity: 1 Instructions: 1. Start a server (Testcase 1001, instruction 1). 2. On a computer running a different OS, connect to that server (Testcase 1009, instruction 2). 3. Exchange data. 4. Repeat instructions 2 and 3, switching operating systems at random. 5. Kill any client. 6. Kill the server. Expected results: 1. All connections occur the same way as in Testcase 1003. 2. All messages are echoed the same way as expected in Testcase 1004. 3. All messages are displayed on the server console using the same format as Testcase 1004. 4. Killing a client has the same effect on all clients and the server as in Testcase 1007. 5. Killing the server has the same effect on all clients as in Testcase 1005. Cleanup: 1.
Testcase 1016 System: Simple Chat Phase: 1 Severity: 1 Instructions: 1. Repeat Testcase 1015 altering the server OS. Expected results: 1. Same as Testcase 1015. Cleanup: 1.


Selection Sort
Selection sort is an algorithm used to sort an unordered array of items.
Given an unsorted array arr
, selection sort builds up a sorted array element by element.
For each element in the original array, we:
- assume element
arr[n]
is the smallest element in the array - check every element after this element (indices
n+1
througharr.length-1
) to see if any element is smaller thanarr[n]
- if so, we set that element equal to the smallest element in the array
- If we found an element smaller than
arr[n]
, we swap positions ofarr[n]
with this element
- otherwise, we do nothing and continue to the next element of the array
This can be implemented using two nested for loops and a swap function (switch a & b by holding a in a temporary variable, setting a to b, and setting b to a) to swap out array elements.
The outer for loop performs the “for each element in the original array” in the algorithm statement, and the inner for loop perform the comparison of every other element in the array to this element, checking to see if there is a smaller element that should be swapped to the front.
Give the ‘result’ tab a click below and try entering some text to see it in action.
Words < words ?!
Note that items are ordered lexicographically
in JS. You could write a custom compare()
function to use instead of <
and >
to implement custom sorting behavior for different types of objects.
What about sorting direction?
We could sort in descending order, rather than ascending, simply by changing step 1 to sasume that arr[n]
is the largest element in the array, and then searching for any elements larger. It’s a good exercise to try on your own: fork the CodePen and adjust the assumption (as well as the comparison step in the for loop) to turn this ascending selection sort into a descending sort.
Edge cases
We throw in two lines to disallow sorting if the array provided is null or if the array length is empty or 1 (an array of length 1 is already ‘sorted’):
if (!arr) {
return new Error("No array supplied to sort.");
} else if (arr.length <= 1) {
return new Error("Array length is not sortable.");
}
This might seem like a minor step, but as your codebase grows larger, it’s essential to have meaningful error messages & ensure functions are called as you expect them to be. Build good habits early.


{# ------------------------------------------------------- #} {# MACROS for SPACES #} {# ------------------------------------------------------- #} {% import "templates/partials/cards/project-cards.html" as projects %} {% import "templates/partials/cards/article-cards.html" as articles %} {% macro card( space ) %}
{% endmacro %}


This example demonstrates a custom implementation of the "onAdd" callback to insert the note marker. Any code that generates a valid DOM element should work. In this case, as an alternative to just using a different image, the implementation of the callback just inserts a randomly colored div element with rounded ends and instead of a number the marker text is an upper case letter.


| Hackers (1995) | |
| 2000 AD (2000) aka "Hackers" |
|
| Hackers (2001) (TV Episode) - Frontline (1983) (TV Series) |
|
| Hacker's Game(2015) aka "The Hackers" |
| Amy Acker (Actress, Angel (1999)) | |
| Drew Van Acker (Actor, Pretty Little Liars (2010)) | |
| Buddy Hackett (Actor, The Little Mermaid (1989)) | |
| Emily Wickersham (Actress, I am Number Four (2011)) |
| hacker (180 titles) |
| Douglas, Gorman, Rothhacker & Wilhelm (DGRW) |
| Crackerjack Management |
| Bleeker Street Media |
| Bleeker Street Entertainment |


Main Page
Text box to check "reload":
Switch to Tab 0
Switch to Tab 1
Switch to Tab 2
Switch to Tab 3
Switch to Tab 4
Switch to Tab 5
Home
Rho.NativeTabbar.create and Rho.NativeTabbar.switchTab
It should remove the current tab bar and replaces it with the new 4 tabs
Rho.NativeTabbar.setTabBadge
Set the iPhone badge to tab: Three tabs should be created with the given labes and Iphone badge 12 should be set on all the tabs
Rho.NativeTabbar.currentTabIndex
Returns the current tab 0-based index.
Rho.NativeTabbar.create
create with tabBarproperties as False
Change the selected color 0xFFFF00 of the tab only for one tab (NA for WM/CE)
Tabbar with createonInit as true For two Individual tabs-it should open the log and app should be minimized


PhoneNumber:
Email:
Name:
Resolved red-flag records → 0
Resolved intervention records → 0
Unresolved red-flag records → 0
Unresolved intervention records→ 0
Rejected red-flag records→ 0
Rejected interventio records → 0
All red-flag records → 0
All intervention records → 0


{% extends "saas/base_dashboard.html" %} {% block saas_title %} {% trans %}Accessible by {{user}}{% endtrans %} {% endblock %} {% block saas_content %} {% trans %}Add Profile{% endtrans %} {% include "saas/_filter_match.html" %} {% trans %}There are currently no items here. Would you like to create some?{% endtrans %} {% include "saas/_organization_card.html" %} {% include "_pagination.html" %} {% trans %}Request access{% endtrans %} ... × {% trans full_name='[[unregistered.full_name]]', site=site.printable_name %}{{full_name}} was not found. This is an opportunity to invite a profile manager for {{full_name}} to join {{site}}.{% endtrans %} {% trans %}To{% endtrans %} {% trans %}The following invite message will be sent:{% endtrans %} {% trans organization_name="[[unregistered.full_name]]", user=request.user.first_name %}Hello, I would like to request access to {{organization_name}} Thank you, - {{user}}{% endtrans %} {% endblock %}
{% trans %}There are currently no items here. Would you like to create some?{% endtrans %}
{% trans full_name='[[unregistered.full_name]]', site=site.printable_name %}{{full_name}} was not found. This is an opportunity to invite a profile manager for {{full_name}} to join {{site}}.{% endtrans %}


Please enter a full date between 1800 and the present.
Please enter a year between 1800 and the present.


{% extends "base.html" %} {% load bootstrap3 %} {% block navbar %} {% endblock navbar %} {% block header %}
Receive closure and maintenance notifications about NYC Parks & Recreation locations.
Sign up Current alerts
NYC Parks publishes updates online, but without a way to subscribe to them.
After a few unexpected closures at my rec center, I made this site to avoid being caught off guard.
You provide your email and a list of locations.
We'll periodically scrape for updates and let you know if your locations are affected.