Version: 0.3.2
MDE in a glance
An MDE can be used for multiple purposes. In this first version of MDE, an MDE instance is simply used to display the content of an xml file in text mode or in an OpenGL 3D viewport.
Installation
Step 1: Verify dependencies
List of libraries you need to have already installed:
-
OpenGL
-
glut
-
freeglut
-
glew
-
freetype2
-
glm
Step 2: external resources
There are currently external resources used by this program on top of the dependancies:
Step 3: make
Makefile is in the source folder. The binary file is output in bin folder
Step 4: run program
From folder bin execute ./mde [OPTION]
Options:
-
no option
if the program is executed with no options, all text mode menus will be displayed consecutively in the console.
-
-v, --version
to get the program's version (and quit).
-
-g, --glmode
display directly in graphic mode (openGL), skip the Display Mode menu
-
-f, --file file
load (xml) file, skip the Data menu
-
-n, --font font
set the font (only open source font on the ./fonts folder for now).
-
-s, --font-size size
set the font size as an integer, best to use multiple of 8.
-
-o, --font-color r,g,b,a
set rgba colours for font with each values in range float[0,1].
-
-b, --box
for displaying a frame box for each text.
-
-c, --box-color r,g,b,a
set rgba colours/alpha for the box frames with each values in range float[0,1].
-
-d, --background-color r,g,b,a
set rgba colours/alpha for the background with each values in range float[0,1] (alpha has no effect).
-
-p, --padding vertical_padding,horizontal_padding
add symetrical vertical and horizontal padding, creating a box frame larger than the text displayed.
-
-a, --origin x,y,z
set the coordinates of origin to (x,y,z).
-
-r, --offset-rule name<->index.x,name<->index.y,name<->index.z,index.x,index.y,index.z,level.x,level.y,level.z
set the offset rule with floats
-
-m, --move
for moving mode (makes the MDE instance move on all axis).
documentation


Read the following statements regarding cell phone usage in schools.
Cell phones could be used to call in bomb threats, and many cell phones cannot be tracked by police.
If an explosive device were on a school campus, a cell phone could be used to detonate it.
Students could use cell phones in an emergency to start rumors and hinder emergency services.
Students' calls could cause parents to panic and hinder emergency services.
Cell phone usage by a large number of students at one time could cause cell phone systems to overload or malfunction.
Based on the text, which description below would be the best title for the passage?


-
This is another just a Quote
-
Description
-
This is just a Quote
-
-
This is another just a Quote
-
Description
-
This is just a Quote
-
This is another just a Quote
Description
This is just a Quote
This is another just a Quote
Description
This is just a Quote


This example shows how to use the tooltip control and some JavaScript code to support scrubbing interaction. The user can touch any item inside the group and move the finger around to see information related to each item before making a selection.


WEDDING CAKE BUILDER Alternate strawberry and chocolate layers to build tiered cakes. The goal is to build each tiered cake, stacked from largest layer on bottom to smallest layer on top. Each tiered cake only contains layers of the same flavor. Your workers were disorganized. Now you have a lot of cake layers to sort out without much space. CLICK AND DRAG a layer of cake. You may move a layer to an empty pan. You may move the next larger layer under a layer of the opposite flavor. Example: strawberry 8 may move under chocolate 7. Build all the cakes to advance to the next wedding deal. If you cannot build all the cakes, click Restart. Longer chains of building a cake scores more points. Finishing in fewer moves scores more points. Can you build a two-layer wedding cake? Can you build two thirteen-layer wedding cakes? To cheat to a higher grade, click the level number and then click Restart. A weekend game by Ethan Kennerly (March 9, 2014) Inspired by FreeCell on Politaire. http://politaire.com/freecell


Snipcart demos
Update quantity and custom fields manually
Update quantity from input
Checkout button position
Triggering Location-Specific Shipping Methods with our JavaScript API
Basic multi currency setup
Add item with API


Hi, I'm a Software Engineer by the University of Málaga and previously a Higher Technician in computer systems management. I seek to create applications which have an impact on people. I'm passionate about technology and programming
Currently, I live in London and I work at Peak and sometimes I develop apps and games. Have a look at my Github and LinkedIn.


--- layout: default layout_keyword: feature title: Event Scheduling tagline: Create entire league or season schedule in one place feature_image: images/features/events-large-icon.png tags: [for_you, for_your_enterprise] ---
Managing and scheduling an entire set of assets from teams, coaches, referees, resources, fields, and volunteers can be frustrating and exhausting. AllPlayers.com takes this burden off your shoulders by offering an easy-to-use solution that considers all aspects and creates a schedule for you.
Balancing all important aspects for your tournament, season, and event will reduce redundancies, double-booking and overlapping commitments.


Sveetoy enforce color policy by defining every color stuff in color schemes so they are usable in other components like blocks, boxes, buttons, etc..
There is also a basic component that just generate helper class like .bg-NAME
where NAME
is the color scheme name. These classes are only created for color scheme with a background
property.
You can find every available color scheme property from color scheme model documentation.
Colors you will see in this page is just a demonstration, Sveetoy default settings has no color scheme defined and sample settings only define a black and a white color schemes.
Note than transparent
is a reserved keyword than you should not use to define your color scheme names. Commonly this word is used as a feature in some component to avoid using any color and just inherit from parent rules.
$include-sv-colors: false;
sveetoy/components/_colors.scss
.bg-{{ k }} :
{{ v }}


| 006:022 Khan | : |
And on the Day when We shall gather them all together, We shall say to those who joined partners in worship (with Us): "Where are your partners (false deities) whom you used to assert (as partners in worship with Allah)?" |
| 006:022 Maulana | : |
And on the day We gather them all together, then We shall say to those who set up gods (with Allah); Where are your associate-gods whom you asserted? |
| 006:022 Pickthal | : |
And on the day We gather them together We shall say unto those who ascribed partners (unto Allah): Where are (now) those partners of your make-believe? |
| 006:022 Rashad | : |
On the day when we summon them all, we will ask the idol worshipers, "Where are the idols you set up?" |
| 006:022 Sarwar | : |
On the Day of Judgment when We will gather all people together, We will ask the pagans, "Where are those whom you believed to be your gods?". |
| 006:022 Shakir | : |
And on the day when We shall gather them all together, then shall We say to those who associated others (with Allah): Where are your associates whom you asserted? |
| 006:022 Sherali | : |
And think of the day when WE shall gather them all together; then shall WE say to those who associated partners with ALLAH, 'Where are the partners you spoke of - those whom you asserted?' |
| 006:022 Yusufali | : |
One day shall We gather them all together: We shall say to those who ascribed partners (to Us): "Where are the partners whom ye (invented and) talked about?" |
Concepts/Themes Covered: أركان الإسلام > التوحيد > توحيد الله تعالي > وحدانيته Pillars of Islam> Islamic> Oneness of Allah> Singularity and Being Unique الإيمان > اليوم الآخر > الحشر Faith> The Hereafter> The Day of Resurrection
This tool uses eight English parallel translations for the Holy Quran imported from Mr. Clay Smith. You can also visit Qurany Concepts for browsing the Quran themes or topics. If you want to search the Holy Quran for keywords, please visit Qurany Keywords.


Edit This Code:
See Result »
ACCELERATE
Use the ACCELERATE button to stay in the air
How long can you stay alive?
Result:


This document is also available in these non-normative formats: PostScript version, PDF version, ZIP archive, and Gzip'd TAR archive.
The English version of this specification is the only normative version. Non-normative translations may also be available.
Copyright © 2003-2010 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
This specification defines three modules: XML Events to define events and their characteristics; XML Handlers to define mappings between events and actions; and XML Scripting to assist in defining functions to support the handlers. These modules work together to provide XML languages with the ability to uniformly integrate event listeners and associated event handlers with Document Object Model (DOM) Level 3 event interfaces [DOM3EVENTS]. The result is to provide an interoperable way of associating behaviors with document-level markup.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
This document is a Working Group Note. The XHTML2 Working Group's charter expired before it could complete work on this document. Related work is being done by the Forms Working Group.
Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document has been produced by the W3C XHTML 2 Working Group as part of the HTML Activity. The goals of the XHTML 2 Working Group are discussed in the XHTML 2 Working Group charter.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
Public discussion of HTML takes place on<EMAIL_ADDRESS>(archive). To subscribe send an email to<EMAIL_ADDRESS>with the word subscribe in the subject line.
Please report errors in this document to<EMAIL_ADDRESS>(archive).
This section is informative.
An event is the representation of some asynchronous occurrence (such as a mouse click on the presentation of the element, or an arithmetical error in the value of an attribute of the element, or any of unthinkably many other possibilities) that gets associated with an element (targeted at it) in an XML document.
In the DOM model of events [DOM3EVENTS], the general behavior is that when an event occurs it is dispatched by passing it down the document tree in a phase called capture to the element where the event occurred (called its target), where it then may be passed back up the tree again in the phase called bubbling. In general an event can be responded to at any element in the path (an observer) in either phase by causing an action, and/or by stopping the event, and/or by cancelling the default action for the event. The following diagram illustrates this:
Event flow in DOM3: an event targeted at an element (marked 'target') in the tree passes down the tree from the root to the target in the phase called 'capture'.
When it arrives at the target it is in the 'target' (or 'at-target') phase. If the event type allows it, the event then travels back up the tree by the same route in a phase called 'bubbling'. Any node in the route, including the root node and the target, may be an 'observer': that is to say, a handler may be attached to it that is activated when the event passes through in either phase. A handler can only listen for one phase. To listen for both you have to attach two handlers.
An action is some way of responding to an event; a handler is some specification for such an action, for instance using scripting or some other method. A listener is a binding of such a handler to an event targeting some element in a document.
HTML [HTML4] binds events to an element by encoding the event name in an attribute name, such that the value of the attribute is the action for that event at that element. This method has two main disadvantages: firstly it hardwires the events into the language, so that to add a new event, you have to make a change to the language, and secondly it forces you to mix the content of the document with the specifications of the scripting and event handling, rather than allowing you to separate them out. SVG [SVG] uses a similar method.
The process of defining XHTML and related markup languages identified the need for an extensible event specification method. The design requirements were the following:
The DOM specifies an event model that provides the following features:
The elements and attributes defined in this specification are the method of binding a DOM level 3 event at an element to an event handler. They encapsulate various aspects of the DOM level 3 event interface, thereby providing markup-level specification of the actions to be taken during the various phases of event propagation.
This document neither specifies particular events, nor mandates any particular methods of specifying actions. These definitions are left to any markup language using the facilities described here.
This section is normative.
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
XML Events is not a stand-alone document type. It is intended to be integrated into other Host Languages such as XHTML. A conforming XML Events document is a document that requires only the facilities described as mandatory in this specification and the facilities described as mandatory in its Host Language. Such a document must meet all the following criteria:
The document MUST conform to the constraints expressed in Appendix B - Schema Implementation or Appendix A - DTD Implementation, combined with the constraints expressed in its Host Language implementation.
If the Host Language does not incorporate XML Events
elements and attributes into its own namespace,
the document MUST contain an xmlns
declaration for the XML Events namespace
[XMLNAMES].
The namespace for XML Events is
defined to be
http://www.w3.org/2001/xml-events
.
An example start tag of a root element might look like:

When XML Events are included in a Host Language, all of the facilities required in this specification MUST be included in the Host Language. In addition, the mandatory elements and attributes defined in this specification MUST be included in the content model of the Host Language.
A conforming Host Language Processor MUST support all of the features required in this specification.
This section is normative.
This specification defines a module called XML Events. The XML Events
module uses the XML namespace [XMLNAMES] identifier
http://www.w3.org/2001/xml-events
.
Examples in this document that use the namespace prefix "ev
"
all assume an xmlns
declaration
xmlns:ev="http://www.w3.org/2001/xml-events"
somewhere suitable
in the document involved. All examples are informative.
The remainder of this section describes the elements and attributes in this module, the semantics, and provides an abstract module definition as required in [XHTMLMOD].
The XML Events Module supports the following element and attributes:
| Element | Attributes | Minimal Content Model |
|---|---|---|
| listener | event (QNames), observer (IDREFS), eventTarget (IDREFS), function (CDATA), handler (URI), phase ("bubble" | "capture" | "default"* | "target"), propagate ("stop" | "continue"*), defaultAction ("cancel" | "perform"*), xml:id ([XMLID]) |
EMPTY |
Implementations: DTD, XML Schema
Element listener
supports a subset of the DOM's
EventListener
interface. It is used to declare event listeners
and register them with specific nodes in the DOM, and has the following
attributes:
event
attribute specifies one, or more, event types
for which the listener is being registered.observer
attribute specifies the
id
of one, or more, elements with which the event listener is to be
registered. If this attribute is not present, the observer is the
element that the event
attribute is on (see later under
"Attaching Attributes Directly to
the Observer Element"), or the parent of that element (see later
under "Attaching Attributes
Directly to the Handler Element").
eventTarget
attribute specifies the
id
of one, or more, target elements of the event (i.e., the node that
caused the event). If this attribute is present, only events that match
both the event
and eventTarget
attributes will be
processed by the associated event handler. Clearly because of the way
events propagate, the target element should be a descendent node of
the observer element, or the observer element itself.
Use of this attribute requires care; for instance, if you specify
<listener event="click" observer="para1" eventTarget="link1" handler="#clicker"/> ...
 Here is some content in a paragraph that includes a link to the draft document.

and the user happens to click on the word "draft", the
em
element, and not the a
,
will be the target, and so the handler will not be activated; to catch
all mouse clicks on the a
element and its children,
use observer="link1"
, and no eventTarget
attribute.
function
attribute identifies an optional
function name that will be called when the event reaches the observer.handler
attribute specifies the URI reference of a
resource that defines the action that should be performed if the event
reaches the observer.
If this attribute is not present, the handler is the element that the event
attribute is on (see later under "Attaching Attributes Directly to the
Handler Element").
If both the function
and handler
attributes
are defined, the handler
element MUST be ignored.
phase
attribute specifies when (during
which DOM 3 event propagation phase) the listener will be activated by
the desired event.
bubble
capture
target
default
If no phase
attribute is specified it is equivalent to having specified phase="default"
.
Note that not all events bubble, in which case with phase="default"
you can only handle the event by making the event's target the observer. The use of phase="default"
is equivalent to invoking the DOM addEventListener
method with a useCapture
that is false
.
propagate
attribute specifies whether after
processing all listeners at the current node, the event is allowed to
continue on its path (either in the capture, target, or bubble phase).
stop
continue
The default behavior is propagate="continue"
.
defaultAction
attribute specifies whether after
processing of all listeners for the event, the
default action for the event (if any) should be performed or not. For
instance, in XHTML the default action for a mouse click on an
a
element or one of its descendents
is to traverse the link.
cancel
perform
The default value is defaultAction="perform"
.
Note that not all events are cancelable, in which case this attribute is ignored.
This example attaches the handler in the element at
"#doit"
that will get activated when the event called
activate
occurs on the element with
id="button1"
, or any of its children. The activation will
occur during bubbling, or if the event happened on the observer element
itself, when the event reaches the element (phase target).
<listener event="DOMActivate" observer="button1" handler="#doit"/>
This attaches the handler at #overflow-handler
that
will get activated when the event overflow
occurs on the
element with id="expr1"
and bubbles up to the element with
id="prog1"
.
<listener event="overflow" observer="prog1" eventTarget="expr1" handler="#overflow-handler"/>
This attaches the handler at #popup
that will get
activated whenever an activate
event occurs at the element
with id="embargo"
or any of its children. Since it will be
activated during the capture phase, and propagation is stopped, this will
have the effect (regardless of what the handler does) of preventing any
child elements of the embargo
element seeing any
activate
events.
<listener event="DOMActivate" observer="embargo" handler="#popup" phase="capture" propagate="stop"/>
This attaches a handler from another document.
<listener event="DOMActivate" observer="image1" handler="/handlers/events.xml#activate"/>
All the attributes from the listener
element with the
exception of id
may be used as global attributes, as
defined in Namespaces in XML [XMLNAMES],
to attach the attributes to other elements.
In the schema implementations,
this is done by defining the attribute collection XMLEvents
.
Note that this means that the listener
element is
strictly speaking redundant, since the following
<anyelement ev:event="click" ev:observer="button1" ev:handler="#clicker"/>
would have the same effect as
<ev:listener event="click" observer="button1" handler="#clicker"/>
Nonetheless, for utility the listener
element has
been retained.
If the observer
attribute is omitted (but not the
handler
attribute), then the element that the other
attributes are attached to is the observer element.
This first example will attach the handler identified by
"#popper"
to the a
element, and cancel
the default action for the event.
The document
This will attach the handler at #handle-overflow
for
the event overflow
to the current element.

 ...

If, when attaching the global attributes to an element, the handler
attribute is
omitted then the element that the other attributes are attached to is the handler element.
Note that, since the observer
and eventTarget
attributes are IDREFs, in this case the handler and observer/target elements
must be in the same document (while in other cases, since the
handler
attribute is a URI, the handler element may be in
another document).
If the observer
attribute is also omitted, then
the parent of the handler element is the observer element.
In this case the element is the handler for the submit
event on the element with id="form1"
.

In this case the action
element is the handler
for event q-submit
, and the observer is the
questionnaire
element.
<questionnaire submissionURL="/q/tally"> <action ev:event="q-submit"> ... </action> ... </questionnaire>
The script
element is the handler for event
click
; the img
element is the
observer.

The onevent
element is the handler for event
enterforward
. The card
element is the
observer.
<card> <onevent ev:event="enterforward"> <go href="/url"/> </onevent>
 Hello!
 </card>
The catch
element is the handler for the
nomatch
event. The observer is the field
element.
<form id="launch_missiles"> <field name="password"> <prompt>What is the code word?</prompt> <grammar> <rule id="root" scope="public">rutabaga</rule> </grammar> <help>It is the name of an obscure vegetable.</help> <catch ev:event="nomatch"> <prompt>Security violation!</prompt> <submit next="apprehend_felon" namelist="user_id"/> </catch> </field> <block> <goto next="#get_city"/> </block> </form>
This example shows three handlers for different events. The observer
for all three is the secret
element.
<secret ref="/login/password">
Please enter your password
 <info ev:event="help"> Mail<EMAIL_ADDRESS>in case of problems </info> <info ev:event="hint"> A pet's name </info> <info ev:event="alert"> This field is required </info> </secret>
The following table summarizes which elements play the role of observer or handler if the relevant attribute is omitted.
| Handler present | Handler omitted | |
|---|---|---|
| Observer present | (As declared) | Element is handler |
| Observer omitted | Element is observer | Element is handler Parent is observer |
In some environments (e.g., User Agents) it is possible to have multiple documents available simultaneously - even to
the extent that one document is embedded within another (see the iframe
element in [XHTMLMOD]).
When multiple documents are available, each of these documents is in a separate context.
Consequently, it is not possible for DOM events to move among these separate documents. This means, for example, that if one document is
embedded within another, an event fired in the context of that document WILL NOT be available to the event handlers in enclosing document.
See [DOM3EVENTS] for more information.
Dynamic content MUST be evaluated by a user agent to ensure that any new listeners or handlers are correctly registered with the event system.
An implementation MUST behave as if any event handlers
are registered prior to the DOM3 load
event being fired.
This section is normative.
The purpose of this module is to provide a declarative way to map specific events to a series of one or more actions. Those actions are declared either by the Host Language (e.g., [XFORMS]) or within the document using the XML Events module above. Implementing actual handlers for the events remains the purview of the Host Language, supported scripting languages, etc.
The XML Handlers Module supports the following elements and attributes:
| Element | Attributes | Minimal Content Model |
|---|---|---|
| action | event (QNames), eventTarget (IDREFS), declare ("declare"), if (ConditionalExpression), while (ConditionalExpression), xml:id ([XMLID]) |
( action | dispatchEvent | addEventListener | removeEventListener | stopPropagation | preventDefault )+ |
| dispatchEvent | eventType (QName), targetid (IDREFS), bubbles ("bubbles"), cancelable ("cancelable"), xml:id ([XMLID]) |
EMPTY |
| addEventListener | event* (QName), handler* (IDREF), phase ("bubble" | "capture" | "default"* | "target"), xml:id ([XMLID]) |
EMPTY |
| removeEventListener | event* (QName), handler* (IDREF), phase ("bubble" | "capture" | "default"* | "target"), xml:id ([XMLID]) |
EMPTY |
| stopPropagation | event* (QName), xml:id ([XMLID]) |
EMPTY |
| preventDefault | event* (QName), xml:id ([XMLID]) |
EMPTY |
When this module is selected, the XML Events module MUST also be selected.
Implementations: DTD, XML Schema
The action
element is used to group event
handler elements (including other action
elements)
that will act in sequence
as handlers for an event. The
action
element takes the following attributes:
event
attribute specifies one, or more, event types
this action will handle.eventTarget
attribute specifies the
id
of one, or more, target elements of the event (i.e., the node that
caused the event). If this attribute is present, only events that match
both the event
and eventTarget
attributes will be
processed. Clearly because of the way
events propagate, the target element should be a descendant node of
the observer element, or the observer element itself.
This attribute allows event handlers to be specified that respond not just to named events, but to more specific conditions, such as a mouse click with the control key pressed:
<action event="click" if="event('ctrlKey') = true()"> . . . </action>
The event function is described in Event Function.
This attribute allows event handlers to be specified that perform their action whilst some condition remains true.
EDITORS' NOTE: Can't think of an example that only makes use of what we have in this spec, i.e., the event() function. We may need to do something like delete a list in XForms.
The dispatchEvent
element triggers the event
identified by the eventType
attribute, delivering
it to the element identified by the to
attribute.
The dispatchEvent
element also defines two additional
attributes:
id
of one or more elements to which the event is dispatched. If this is not specified,
it defaults to the parent of the dispatchEvent
elementThis element allows the registration of a listener on a specific event, as defined in [DOM3EVENTS].
The removeEventListener
element de-registers the
handler identified by the required handler
attribute for
the event identified by the required event
attribute.
The stopPropagation
element is used to prevent further propagation of an
event during event flow. If this is called by any EventListener the
event will cease propagating through the tree. The event will complete
dispatch to all listeners on the current EventTarget before event flow
stops. This action may be used during any stage of event flow.
If an event is cancelable, the preventDefault
action is used to signify that
the event is to be canceled, meaning any default action normally taken by
the implementation as a result of the event will not occur. If, during any
stage of event flow, the preventDefault
action is called the event is
canceled. Any default action associated with the event will not occur.
Calling this action for a non-cancelable event has no effect. Once
preventDefault has been called it will remain in effect throughout the
remainder of the event's propagation. This action may be used during any
stage of event flow.
This section is normative.
The XML Script Module defines an element for defining event handlers via a scripting language. This module can be used as a replacement for the XHTML Scripting Module defined in XHTML Modularization [XHTMLMOD].
The XML Script Module supports the following element:
| Element | Attributes | Minimal Content Model |
|---|---|---|
| script | charset (Charset), defer ("defer"), implements ( URIorSafeCURIEs ),src (URI), type (ContentType), xml:id ([XMLID]) |
PCDATA |
When the Scripting module is included AND the XML Handlers Module
is included, the script
element is added to the content
model of the XML Handlers Module action
element.
Implementations: DTD, XML Schema
The script
element contains or references scripts that may register one or more event handlers for a document through a scripting language that is supported by the implementation.
charset
attribute specifies the encoding
of the remote resource identified by the src
attribute.
script
element will not effect the generation of the document.implements
attribute indicates that the script provides an implementation of the feature or features identified via this attribute.
The script SHOULD only be loaded and used if the user agent does not have an implementation of the specified feature.
src
attribute identifies an external resource
that provides the script implementation.The event handler(s) may be defined within the contents of the
script
element or in an external file. If the src
attribute is not set, user agents MUST
interpret the contents of the element as the handler.
If the src
has a URI value, user agents MUST ignore
the element's contents and retrieve the handler via the URI.
This section is informative.
This specification does not normatively specify how language designers
should name events (i.e., the values used in the event
attribute).
However, future versions of DOM Events are likely to allow namespaced event names, so language designers are advised not to use the colon character ":" in event names.
A number of event types are defined in DOM 3 Events [DOM3EVENTS], to which you should refer for their names and semantics.
XML Events uses XPath-like expressions to specify conditionals (if, while). As described in section 1 of [XPATH], each expression is evaluated within a context, which is made up of:
By default, XML Events expressions have no context node, and so the context position is 0 and the context size is 0. There are no variable bindings, and the function library contains the functions described below. It is not necessary to provide namespace declarations.
Host languages that import XML Events may provide a richer context, and MUST specify whether their context is the same as that provided here, or more.
The function library consists of the following functions:
object event(string)
Function event
returns the value of a property of the current event object,
as determined by the string argument. The value returned will be typed,
depending on the property. For example, the MouseEvent interface [DOM3EVENTS]
has the
attribute shiftKey
, which is a boolean
. This can be accessed by passing the
string value 'shiftKey
' to the event function. The result will be an XPath-like
boolean.
This appendix is normative.
The DTD implementation of XML Events conforms to the requirements defined in [XHTMLMOD]. Consequently, it provides a Qualified Names sub-module, and a module file for the XML Events module defined in this Proposed Recommendation.
Note that this module defines the parameter entity
%xml-events-attrs.qname;
. This entity is intended to be used in
the attribute lists of elements in any Host Language that permits the use of
event attributes on elements in its own namespace. In this case the Host
Language driver should set a parameter entity %XML-EVENTS.prefixed;
to INCLUDE
and a parameter entity %XML-EVENTS.prefix;
to a value that is the prefix for the XML Events attributes.
      <!ENTITY % NS.prefixed "IGNORE" > <!ENTITY % XML-EVENTS.prefixed "%NS.prefixed;" >  <!ENTITY % XML-EVENTS.xmlns "http://www.w3.org/2001/xml-events" >  <!ENTITY % XML-EVENTS.prefix "" >  <![%XML-EVENTS.prefixed;[ <!ENTITY % XML-EVENTS.pfx "%XML-EVENTS.prefix;:" > ]]> <!ENTITY % XML-EVENTS.pfx "" >  <!ENTITY % xml-events-qname-extra.mod "" > %xml-events-qname-extra.mod;  <!ENTITY % XML-EVENTS.xmlns.extra.attrib "" >   <!ENTITY % xml-events.listener.qname "%XML-EVENTS.pfx;listener" > <!ENTITY % xml-handlers.action.qname "%XML-EVENTS.pfx;action" > <!ENTITY % xml-script.script.qname "%XML-EVENTS.pfx;script" > <!ENTITY % xml-handlers.dispatchEvent.qname "%XML-EVENTS.pfx;dispatchEvent" > <!ENTITY % xml-handlers.addEventListener.qname "%XML-EVENTS.pfx;addEventListener" > <!ENTITY % xml-handlers.removeEventListener.qname "%XML-EVENTS.pfx;removeEventListener" > <!ENTITY % xml-handlers.stopPropagation.qname "%XML-EVENTS.pfx;stopPropagation" > <!ENTITY % xml-handlers.preventDefault.qname "%XML-EVENTS.pfx;preventDefault" >  <!ENTITY % xml-events.attrs.qname "%XML-EVENTS.pfx;event NMTOKEN #IMPLIED %XML-EVENTS.pfx;observer IDREFS #IMPLIED %XML-EVENTS.pfx;eventTarget IDREFS #IMPLIED %XML-EVENTS.pfx;handler %URI.datatype; #IMPLIED %XML-EVENTS.pfx;phase (capture|default) #IMPLIED %XML-EVENTS.pfx;propagate (stop|continue) #IMPLIED %XML-EVENTS.pfx;defaultAction (cancel|perform) #IMPLIED %XML-EVENTS.pfx;condition CDATA #IMPLIED" >
    <!ENTITY % xml-events.listener.content "EMPTY" > <!ELEMENT %xml-events.listener.qname; %xml-events.listener.content;> <!ATTLIST %xml-events.listener.qname; xml:id ID #IMPLIED event NMTOKEN #REQUIRED observer IDREF #IMPLIED eventTarget IDREF #IMPLIED handler %anyURI.datatype; #IMPLIED phase (capture|default) #IMPLIED propagate (stop|continue) #IMPLIED defaultAction (cancel|perform) #IMPLIED >
    <!ENTITY % xml-handlers.action.content "( %xml-handlers.action.qname; | %xml-handlers.dispatchevent.qname; | %xml-handlers.addEventListener.qname; | %xml-handlers.removeEventListener.qname; | %xml-handlers.stopPropagation.qname; | %xml-handlers.preventDefault.qname; | %xml-handlers.action.extras; )+ " > <!ELEMENT %xml-handlers.action.qname; %xml-handlers.action.content;> <!ATTLIST %xml-handlers.action.qname; xml:id ID #IMPLIED event %QName.datatype; #IMPLIED eventTarget IDREF #IMPLIED declare ( declare ) #IMPLIED if CDATA #IMPLIED while CDATA #IMPLIED > <!ENTITY % xml-handlers.dispatchEvent.content "NONE" > <!ELEMENT %xml-handlers.dispatchEvent.qname; %xml-handlers.dispatchEvent.content > <ENTITY % xml-handlers.dispatchEvent.attlist "INCLUDE" > <![%xml-handlers.dispatchEvent.attlist;[ <!ATTLIST %xml-handlers.dispatchEvent.qname; %XML-EVENTS.xmlns.attrib; xml:id ID #IMPLIED targetid IDREFS #IMPLIED eventType %QName.datatype; #IMPLIED bubbles ( bubbles ) #IMPLIED cancelable ( cancelable ) #IMPLIED > ]]> <!ENTITY % xml-handlers.addEventListener.content "NONE" > <!ELEMENT %xml-handlers.addEventListener.qname; %xml-handlers.addEventListener.content > <ENTITY % xml-handlers.addEventListener.attlist "INCLUDE" > <![%xml-handlers.addEventListener.attlist;[ <!ATTLIST %xml-handlers.addEventListener.qname; %XML-EVENTS.xmlns.attrib; xml:id ID #IMPLIED event %QName.datatype; #REQUIRED handler IDREF #REQUIRED phase (capture|default) #IMPLIED > ]]> <!ENTITY % xml-handlers.removeEventListener.content "NONE" > <!ELEMENT %xml-handlers.removeEventListener.qname; %xml-handlers.removeEventListener.content > <ENTITY % xml-handlers.removeEventListener.attlist "INCLUDE" > <![%xml-handlers.removeEventListener.attlist;[ <!ATTLIST %xml-handlers.removeEventListener.qname; %XML-EVENTS.xmlns.attrib; xml:id ID #IMPLIED event %QName.datatype; #REQUIRED handler IDREF #REQUIRED phase (capture|default) #IMPLIED > ]]> <!ENTITY % xml-handlers.stopPropagation.content "NONE" > <!ELEMENT %xml-handlers.stopPropagation.qname; %xml-handlers.stopPropagation.content > <ENTITY % xml-handlers.stopPropagation.attlist "INCLUDE" > <![%xml-handlers.stopPropagation.attlist;[ <!ATTLIST %xml-handlers.stopPropagation.qname; %XML-EVENTS.xmlns.attrib; xml:id ID #IMPLIED event %QName.datatype; #REQUIRED > ]]> <!ENTITY % xml-handlers.preventDefault.content "NONE" > <!ELEMENT %xml-handlers.preventDefault.qname; %xml-handlers.preventDefault.content > <ENTITY % xml-handlers.preventDefault.attlist "INCLUDE" > <![%xml-handlers.preventDefault.attlist;[ <!ATTLIST %xml-handlers.preventDefault.qname; %XML-EVENTS.xmlns.attrib; xml:id ID #IMPLIED event %QName.datatype; #REQUIRED > ]]>
    <!ENTITY % xml-script.script.content "( #PCDATA )" > <!ELEMENT %xml-script.script.qname; %xml-handlers.script.content; > <!ENTITY % xml-script.script.attlist "INCLUDE" > <![%xml-script.script.attlist;[ <!ATTLIST %xml-script.script.qname; %XML-EVENTS.xmlns.attrib; xml:id ID #IMPLIED encoding %Charset.datatype; #IMPLIED type %ContentType.datatype; #REQUIRED src %URI.datatype; #IMPLIED implements %URIorSafeCURIEs.datatype; #IMPLIED > ]]>
This appendix is normative.
The schema implementation of XML Events conforms to the requirements defined in [XHTMLMOD]. It is divided into an attributes module and an element module for the XML Events module defined in this Proposed Recommendation.
<?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://www.w3.org/2001/xml-events" xmlns:ev="http://www.w3.org/2001/xml-events" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.w3.org/2001/XMLSchema http://www.w3.org/2001/XMLSchema.xsd" elementFormDefault="unqualified" blockDefault="#all" finalDefault="#all" attributeFormDefault="unqualified"> <xs:annotation> <xs:documentation> This is the XML Schema for XML Events global attributes URI: http://www.w3.org/MarkUp/SCHEMA/xml-events-attribs-2.xsd $Id: Overview.html,v 1.2 2010/12/17 20:25:20 plehegar Exp $ </xs:documentation> <xs:documentation source="xml-events-copyright-2.xsd"/> </xs:annotation> <xs:annotation> <xs:documentation> XML Event Attributes These "global" event attributes are defined in "Attaching Attributes Directly to the Observer Element" of the XML Events specification. </xs:documentation> </xs:annotation> <xs:attribute name="event" type="xs:NMTOKEN"/> <xs:attribute name="observer" type="xs:IDREF"/> <xs:attribute name="eventTarget" type="xs:IDREF"/> <xs:attribute name="handler" type="xs:anyURI"/> <xs:attribute name="phase" default="default"> <xs:simpleType> <xs:restriction base="xs:NMTOKEN"> <xs:enumeration value="bubble"/> <xs:enumeration value="capture"/> <xs:enumeration value="default"/> <xs:enumeration value="target"/> </xs:restriction> </xs:simpleType> </xs:attribute> <xs:attribute name="propagate" default="continue"> <xs:simpleType> <xs:restriction base="xs:NMTOKEN"> <xs:enumeration value="stop"/> <xs:enumeration value="continue"/> </xs:restriction> </xs:simpleType> </xs:attribute> <xs:attribute name="defaultAction" default="perform"> <xs:simpleType> <xs:restriction base="xs:NMTOKEN"> <xs:enumeration value="cancel"/> <xs:enumeration value="perform"/> </xs:restriction> </xs:simpleType> </xs:attribute> <xs:attributeGroup name="XmlEvents.attlist"> <xs:attribute ref="ev:event"/> <xs:attribute ref="ev:observer"/> <xs:attribute ref="ev:eventTarget"/> <xs:attribute ref="ev:handler"/> <xs:attribute ref="ev:phase"/> <xs:attribute ref="ev:propagate"/> <xs:attribute ref="ev:defaultAction"/> </xs:attributeGroup> </xs:schema>
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="http://www.w3.org/2001/xml-events"
xmlns="http://www.w3.org/2001/xml-events"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.w3.org/2001/XMLSchema
http://www.w3.org/2001/XMLSchema.xsd"
elementFormDefault="unqualified"
blockDefault="#all"
finalDefault="#all"
attributeFormDefault="unqualified">
<xs:annotation>
<xs:documentation>
This is the XML Schema for XML Events
URI: http://www.w3.org/MarkUp/SCHEMA/xml-events-2.xsd
$Id: Overview.html,v 1.2 2010/12/17 20:25:20 plehegar Exp $
</xs:documentation>
<xs:documentation source="xml-events-copyright-2.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
XML Events element listener
This module defines the listener element for XML Events.
This element can be used to define event listeners.
This section is informative.
In developing version 2 of XML Events, the following major changes have been made:
This section is informative.
This document was prepared by the W3C XHTML2 Working Group. The members at the time of publication of the Note were:
At publication of the first edition, the acknowledgements included was:
This document was originally edited by Ted Wugofski (Openwave).
Special acknowledgments to: Mark Baker (Sun Microsystems), Wayne Carr (Intel Corporation), Warner ten Kate (Philips Electronics), Patrick Schmitz, and Peter Stark (Ericsson) for their significant contributions to the evolution of this specification.
At the time of publication, the participants in the W3C HTML Working Group were:


Renders an HTML "input" element of "type" "hidden".
| Attributes |
| Name | Required | Request-time | Type | Description |
| binding | false | false | java.lang.String | The value binding expression linking this component to a property in a backing bean |
| converter | false | false | java.lang.String | Converter instance registered with this component. |
| converterMessage | false | false | java.lang.String | A ValueExpression enabled attribute that, if present, will be used as the text of the converter message, replacing any message that comes from the converter. |
| id | false | false | java.lang.String | The component identifier for this component. This value must be unique within the closest parent component that is a naming container. |
| immediate | false | false | java.lang.String | Flag indicating that this component's value must be converted and validated immediately (that is, during Apply Request Values phase), rather than waiting until Process Validations phase. |
| rendered | false | false | java.lang.String | Flag indicating whether or not this component should be rendered (during Render Response Phase), or processed on any subsequent form submit. |
| required | false | false | java.lang.String | Flag indicating that the user is required to provide a submitted value for this input component. |
| requiredMessage | false | false | java.lang.String | A ValueExpression enabled attribute that, if present, will be used as the text of the validation message for the "required" facility, if the "required" facility is used. |
| validator | false | false | java.lang.String | MethodBinding representing a validator method that will be called during Process Validations to perform correctness checks on the value of this component. The expression must evaluate to a public method that takes FacesContext, UIComponent, and Object parameters, with a return type of void. |
| validatorMessage | false | false | java.lang.String | A ValueExpression enabled attribute that, if present, will be used as the text of the validator message, replacing any message that comes from the validator. |
| value | false | false | java.lang.String | The current value of this component. All UIInput derived UIComponents, that are placed within a UIData container, such as a dataTable or panelSeries, should have their value attribute bound to a bean property via a ValueBinding/ValueExpression, since otherwise the UIData container will not keep their successfully validated state, which can cause the component to fail to function properly. |
| valueChangeListener | false | false | java.lang.String | MethodBinding representing a value change listener method that will be notified when a new value has been set for this input component. The expression must evaluate to a public method that takes a ValueChangeEvent parameter, with a return type of void. |


{{ page.title }}
{% endif %}
Days in the office
{{ page.daysInOffice }}
Hours in the office building
{{ page.hoursInOffice }}
Busiest weekday
{{ page.busiestDay }}
Just for kicks, I've been tracking my comings and goings
For starters this is quite basic - just simple arrival and departure times at my usual work office. Leaving the office building for coffee or lunch, as well as public holidays and vacation, is accounted for. Time spent in other offices or locations is also not counted.
{{ page.daysInOffice }}
{{ page.hoursInOffice }}
{{ page.busiestDay }}


doodle.geom.Point
Description:
- Point (x:number, y:number) :Point
-
Inherits
- Object
Parameters
- x:number – [optional]
- y:number – [optional]
Returns
- Point –
Throws
- TypeError –
- SyntaxError –
Properties
- x :number
-
The horizontal coordinate of the point.
Returns
- number –
Throws
- TypeError –
- length :number
-
The length of the line segment from (0,0) to this point.
Returns
- number –
- y :number
-
The vertical coordinate of the point.
Returns
- number –
Throws
- TypeError –
Methods
- add (pt:Point) :Point
-
Adds the coordinates of another point to the coordinates of this point to create a new point.
Parameters
- pt:Point – The point to be added.
Returns
- Point – The new point.
Throws
- TypeError –
- polar (len:number, angle:number) :Point
-
Converts a pair of polar coordinates to a Cartesian point coordinate.
Parameters
- len:number – The length coordinate of the polar pair.
- angle:number – The angle, in radians, of the polar pair.
Returns
- Point –
Throws
- TypeError –
- clone () :Point
-
Creates a copy of this Point object.
Returns
- Point –
- interpolate (pt1:Point, pt2:Point, t:number) :Point
-
Determines a point between two specified points.
Parameters
- pt1:Point – The first point.
- pt2:Point – The second point.
- t:number – The level of interpolation between the two points, between 0 and 1.
Returns
- Point –
Throws
- TypeError –
- equals (pt:Point) :boolean
-
Determines whether two points are equal.
Parameters
- pt:Point – The point to be compared.
Returns
- boolean –
Throws
- TypeError –
- offset (dx:number, dy:number) :void
-
Parameters
- dx:number –
- dy:number –
Throws
- TypeError –
- toArray () :Array
-
Returns an array that contains the values of the x and y coordinates.
Returns
- Array –
- toString () :string
-
Returns a string that contains the values of the x and y coordinates.
Returns
- string –
- normalize (thickness:number) :Point
-
Scales the line segment between (0,0) and the current point to a set length.
Parameters
- thickness:number – The scaling value.
Returns
- Point –
Throws
- TypeError –
- compose (x:number, y:number) :Point
-
Set point coordinates.
Parameters
- x:number –
- y:number –
Returns
- Point –
Throws
- TypeError –
- subtract (pt:Point) :Point
-
Subtracts the coordinates of another point from the coordinates of this point to create a new point.
Parameters
- pt:Point – The point to be subtracted.
Returns
- Point – The new point.
Throws
- TypeError –
Class Functions
- isPoint (pt:Point) :boolean
-
Check if a given object contains a numeric x and y property. Does not check if a point is actually a doodle.geom.point.
Parameters
- pt:Point –
Returns
- boolean –
- distance (pt1:Point, pt2:Point) :number
-
Returns the distance between pt1 and pt2.
Parameters
- pt1:Point –
- pt2:Point –
Returns
- number –
Throws
- TypeError –


|
abund_rel()
|
Calculate relative abundance |
|
abund_rel_vec()
|
Calculate relative abundance |
|
add_trans()
|
Add transparency to a color |
|
calc_z()
|
Degree of compensation |
|
ce()
|
Calculate normalized sustainable yield |
|
dat
|
Life history parameters for pinnipeds |
|
dynamics()
|
Generate one marine mammal population trajectory |
|
find_msyr()
|
calculate MSYR |
|
get_diff()
|
Calculate the derivative of C in getMNPL() |
|
get_dz()
|
Derivative of z (function to minimize) |
|
get_f()
|
Get bycatch mortality rate given depletion |
|
get_mnpl()
|
Calculate Maximum Net Productivity Level (MNPL) |
|
get_rf()
|
Get relative recruitment at bycatch mortality rate E |
|
getfecmax()
|
Calculate maximum theoretical fecundity rate |
|
ggradar()
|
Radar plot |
|
inv_logit()
|
Get inverse logit of a value |
|
lh
|
Life history parameters for marine mammals. |
|
logit()
|
Logit transform |
|
make_ptable()
|
Make a performance table. Trajectories must be based on 100-year simulations. |
|
multiplot_proj()
|
multiplot.proj |
|
npr()
|
Calculate numbers per recruit |
|
plot_bycatch_guesses()
|
Plot distribution of bycatch values |
|
plot_pinnipeds()
|
Plot all the pinniped life history parameters |
|
plot_proj()
|
Plot projections |
|
plot_yield_curve()
|
Yield curve for Shiny |
|
pop_vs_yield()
|
Yield or productivity curve |
|
prob_rebuilt_goal()
|
Calculate the probability of reaching a rebuilding goal |
|
projections()
|
Run simulations of a marine mammal population with bycatch mortality |
|
rebuild_by_x()
|
Calculate the bycatch rate needed to reach a performance goal |
|
run_app()
|
Run the Shiny Application |


Front line today... A Volvano has been found north east of New Zealand of the coast of Tonga it is about the sise of Luxumberg.
Breaking news... The Grand Canyon is going to be turned into a water park
The meteorite that killed of the dinesors is coming for round two
Breaking news... The world is a ticking time volcano.


DR FINDER
Find the doctor you need now
Search by medical issue
Enter your symptom:
City:
State:
Find Doctor
Search by doctor
Doctor name:
City:
State:
Find Doctor
Clear Results


Simply Cindy
Does not exist.
Color:
Red
Blue
Black
Green
White
Size:
Small
Medium
Large
X-Large
Customize:
Quantity:
1
2
3
4
5
6
7
8
9
10


--- layout: paper title: Publications --- Bio-Molecular Event Extraction with Markov Logic, , Computational Intelligence 2011
@article{riedel10bio, volume={27}, number={4}, journal={Computational Intelligence}, month={November}, year={2011}, author={Sebastian Riedel and Rune Saetre and Hong-Woo Chun and Toshihisa Takagi and Jun'ichi Tsujii}, title={Bio-Molecular Event Extraction with Markov Logic}, }


Philippines all-time top scorer Phil Younghusband announces retirement
Former Philippines national team captain and all-time leading goalscorer Phil Younghusband has on Monday announced his retirement from football.
 See you all soon in a new adventure,” the 32-year-old announced the retirement with a brief social media post.
Born in England, the Chelsea academy graduate represented the Philippines senior national team for the time in 2006 and has since then made over 100 appearances for the Azkals at the international stage including in their maiden appearance at the AFC Asian Cup earlier this year.
Phil is the leading goalscorer in Philippines’ history with 52 goals from 108 international matches.
The attacker moved to Philippines from England in 2008 to play for clubs like San Beda FC, Loyola Meralco Spark and Davao Aguilas.
Phil’s elder brother James also plays for Philippines national team and is currently plying his trade with Ceres Negros FC.
(Photo credit: AFF Suzuki Cup)


‘Earth’ is an avid gardener. She loves nothing more than to feed the people of Plumpton with the food she grows in her kitchen garden.
Most of the time ‘Earth’ remembers her grandmothers' ancient stories that teach valuable lessons about respecting the land. However, she can become more than a little caught up in the demand for her produce with disastrous outcomes.


open
Are you looking for 'White dresses'
Cotton White Dresses
See more
Cotton White Dresses
See more


DIY systems have come along way. For a blend of use simplicity, design excellent, and functionality, SquareSpace.com is my suggestion. For more technical users, check out WordPress.
Built with SquareSpace.com to leverage the design, stability, and support of a NYC or Silicon Valley Website Development Agency, but at the local freelancer price of $50/hr. Hand this off and get back to your business.
Partner with an Silicon Valley company who can take your business to the next level in measurable results marketing, tracked SEO/SEM, and custom WordPress sites and web applications.
With course work under my belt, I am completing some of my own projects to show what value is ready for hire. Check out the work in the portfolio section.
While attending a hackathon, the consensus was that Javascript was the language to learn, so I joined FreeCodeCamp.com. FCC is both a great learning tool and community of those learning to code beginning with Front-End Development in Javascript. Course projects can be seen in the portfolio above.
Looking for a more structured route to the first job, I tried Udacity. The first Python section was in my opinion a perfect online class. Check out my GitHub profile to see the work.
After a positive experience with SQL, Python, and a ton of spreadsheets in the past, I completed a course on data analytics, which left me hungry for something more tangible.
Where to go now? What I knew is I was an analytical problem solver and great with Excel. Reddit and Google pointed me to coding and Codecademy to test the fit. There I completed SQL and Python.
I hired myself and loved it. Customer service is good, but making something is why I started down the engineering path to begin with. Check out my wix.com site for the business right here. And by the way, do you need a business loan?
Moved to real estate investment with great help from BiggerPockets.com, an investor forum community. That project has funded this career switch.
Wanting to do more tangible work, led me to a road including four roles in training including tutoring, a start up (minus the start) and a leadership role overhauling adult learning programs at a chemical plant.
First job out of college taught me that I have much to learn, including that I would like to do more tangible work. It took a while, but I am there now.
Looking back, the courses that stood out were Excel and programming related. That plus internships with GE and Caterpillar told me that engineering may not be the best fit.


Deep understanding in statistics, basic sociology, data structure and algorithms. Rich experience in HCI/UI/UX design, prototyping, visual information design, java programming, website development, building database, information system analysis and design, project management, usability testing and research.
Various roles in the group as needed. As Project Manager, communicateing well with the group and make sure each member perform well. Also work well independently as UX designer, front-end web development.
Volunteered at Chinese Information and Service Center, helping children from 1 to 8 grade to do their home work, reading assignments. Also organize kids to do various kinds of activities. And be friends with them.
Proficient in Microsoft Offices, git, SQLite, Eclipse, JGrasp, Adobe Illustrator and other prototyping tools.
Proficient in HTML5, CSS, JavaScript, Java, Bash, SQL.
Trilingual in Chinese (native), English (full proficiency), Japanese (elementary proficiency).


During the school year, we raise money through a variety of on-campus and off-campus fundraisers. These fundraisers help us buy supplies for and fund our projects in India.
On-Campus
On-campus fundraisers are held mainly at UCSD's Library Walk about three times a quarter. We set up henna services and sell discount cards, samosas, chai, lassi, hand-made gretting cards, wristbands, and t-shirts. Restaurants at UCSD's Price Center also offer fundraising opportunities, donating 15-20% of sales from a scheduled fundraising event to our organization.
Off-Campus
We set up booths at local community centers and events such as Sangam Culture Show. We also work with a Project RISHI interest group at local Westview High School to cohost events and volunteer with.
Past & Upcoming Events
December 5, 2013: Rubio's Fundraiser. 20% proceeds to Project Rishi!
January 21, 2014: Tapex Fundraiser. 5% discount and 15% proceeds to Project Rishi!
February 10, 2014: Samosa Fundraiser @ Library Walk. Enjoy the delicious, warm samosas from Tandoori Chef!
The easiest way for sponsors to help us is through the form of monetary donations. The generous donations from sponsors help us finance our projects in India.
Diamond Donor - Donations more than $1000
Emerald Donor - Donations between $501-$1000
Ruby Donor - Donations between $100-$500
Previous Sponsors:
Donate to our WEEKLY ONLINE FUNDRAISER!
Donate NOW through our PayPal button!
Check calendar for upcoming fundraisers!


GitHub Page
JigSass Grid is a responsive Sass (SCSS) flexbox-based grid
system, with a display: inline-block
fallback backed in, where possible.
It is intended to be both flexible (pun intended) and easy to use. As part of the
JigSass ecosystem, JigSass Grid integrates with its other modules, relying on some of them
for consistent resposive breakpoints,
sizing and more.
Installation
Using npm:
npm i -S jigsass-objects-grid
Features
Availeable classes
For classes and modifiers (including responsive modifiers) to be generated in CSS
output, they must be explicitly enabled in the configuration maps
(see usage below).
Grid containers:
.o-grid
--start
, --center
, --end
, --rev
, --space-between
, --space-around
--top
, --middle
, --bottom
, --equal-height
--gutter-X
(gutter width, See here).
Grid items:
.o-grid__item
--col
, --center,
--top
, --middle
, --bottom
, --equal-height
--gutter-X
(gutter width, See here).
--gutter-gutter-rule-X
(See here).
--X-of-Y
--offset-X-of-Y
Usage
First, import JigSass Grid into your main stylesheet:
@import 'path/to/jigsass-objects-grid/scss/index'
And optionally reconfigure the defaults to you liking.
To create a grid context, simply attach the o-grid class to an element, any element,
which will serve as a grid container. You can now add grid items to it (with a class of
o-grid__item). Grid containers' only legitimate children are grid items, and those, in turen,
may only reside within a grid container.
Like all other JigSass modules, JigSass Grid does not automatically generate any
CSS output when imported. In order to use its classes, you would have to first
explicitly indicate your intention to use them by enabling their generation in
the associated configurations map, Leaving us only with CSS we need.
All JigSass Grid classes are responsive-enabled, using
JigSass MQ and the breakpoints defined in the
$jigsass-breakpoints
variable.
Based on enabled selectors in the configuration map, responsive modifiers are
generated according to the following logic:
.o-grid[--modifier][-[-from-{breakpoint-name}][-until-{breakpoint-name}][-misc-{breakpoint-name}]]
.o-grid__item[--modifier][-[-from-{breakpoint-name}][-until-{breakpoint-name}][-misc-{breakpoint-name}]]
So, assuming the medium
, large
and landscape
breakpoints are defined in $jigsass-breakpoints
as 600px
, 1024px
and (orientation: landscape)
respectively,
$jigsass-grid-conf: (
no-breakpoint: (
no-modifier: true,
end: true,
),
until-medium: (
end: true,
),
from-large-when-landscape: (
end: true,
),
)
will generate the following classes:
.o-grid
, which is not limited to any media-query.
.o-grid--end
, which is not limited to any media-query.
.o-grid--end--until-medium
, which will be in effect at
(max-width: 37.49em)
and will override styles in the default class
until that point.
.o-grid--end--from-large-when-landscape
, which will go into effect at
(min-width: 64em) and (orientation: landscape)
and will override styles
in the default class under these conditions.


foodie
feed
search
profile
create
log out
ingredients
directions
substitutions
ingredients
directions
substitutions


Introduction: This article tries to cover every aspect of AT and PS/2 keyboards. It includes information on the low-level signals and protocol, scan codes, the command set, initialization, compatibility issues, and other miscellaneous information. Since it's closely related, I've also included information on the PC keyboard controller. All code samples involving the keyboard interface are written in assembly for Microchip's PIC microcontrollers. All code samples related to the keyboard controller are written in x86 assembly. I should mention that all of the information in this article comes from my own experiences and other sources that may or may not be accurate. I did not consult any official documentation of since none has been available to me.  I DO NOT GUARANTEE ANY INFORMATION IN THIS ARTICLE IS ACCURATE, AND IT SHOULD BE USED FOR ABSTRACT EDUCATIONAL PURPOSES ONLY. You may click here to goto my main page. There, you will find other articles, code, projects, and links related to the computer keyboard. Please send me an email if you find any errors on these pages. A History Lesson: The most popular keyboards in use today include:
IBM PC/XT Keyboard (1981):
Today, "AT keyboard" and "PS/2 keyboard" refers only to their connector size. Which settings/commands any given keyboard does or does not support is anyone's guess. For example, the keyboard I'm using right now has a PS/2-style connector but only fully supports seven commands, partially supports two, and merely "acknowledges" the rest. In contrast, my "Test" keyboard has an AT-style connector but supports every feature/command of the original PS/2 device (plus a few extra.) It's important you treat modern keyboards as compatible, not standard. If your project relies on non-general features, it may work on some systems, but not on others... Modern AT-PS/2 compatible keyboards
Footnote 1) XT keyboards use a completely different protocol than that used by AT and PS/2 systems, making it incompatible with the newer PCs. However, there was a transition period where some keyboard controllers supported both XT and AT-PS/2 keyboards (through a switch, jumper, or auto-sense.) Also, some keyboards were made to work on both types of systems (again, through the use of a switch or auto-sensing.) If you've owned such a PC or keyboard, don't let it fool you--XT keyboards are NOT compatible with modern computers. General Description: Keyboards consist of a large matrix of keys, all of which are monitored
by an on-board processor (called the "keyboard encoder".) The specific
processor(1) varies
from keyboard-to-keyboard but they all basically do the same thing:
Monitor which key(s) are being pressed/released and send the appropriate
data to the host. This processor takes care of all the debouncing
and buffers any data in its 16-byte buffer, if needed. Your motherboard
contains a "keyboard controller"(2) that is in charge of decoding
all of the data received from the keyboard and informing your software of
what's going on. All communication between the host and the keyboard
uses an IBM protocol. Electrical Interface / Protocol: The AT and PS/2 keyboards use the same protocol as the PS/2 mouse. Click here for detailed information about that protocol. Scan Codes: Your keyboard's processor spends most of its time "scanning", or monitoring, the matrix of keys. If it finds that any key is being pressed, released, or held down, the keyboard will send a packet of information known as a "scan code" to your computer. There are two different types of scan codes: "make codes" and "break codes". A make code is sent when a key is pressed or held down. A break code is sent when a key is released. Every key is assigned its own unique make code and break code so the host can determine exactly what happened to which key by looking at a single scan code. The set of make and break codes for every key comprises a "scan code set". There are three standard scan code sets, named one, two, and three. All modern keyboards default to set two.(1) So how do you figure out what the scan codes are for each key? Unfortunately, there's no simple formula for calculating this. If you want to know what the make code or break code is for a specific key, you'll have to look it up in a table. I've composed tables for all make codes and break codes in all three scan code sets:
Footnote 1) Originally, the AT keyboard only supported set two, and the PS/2 keyboard would default to set two but supported all three. Most modern keyboards behave like the PS/2 device, but I have come across a few that didn't support set one, set three, or both. Also, if you've ever done any low-level PC programming, you've probably notice the keyboard controller supplies set ONE scan codes by default. This is because the keyboard controller converts all incomming scan codes to set one (this stems from retaining compatibility with software written for XT systems.) However, it's still set two scan codes being sent down the keyboard's serial line. Make Codes, Break Codes, and Typematic Repeat: Whenever a key is pressed, that key's make code is sent to the computer. Keep in mind that a make code only represents a key on a keyboard--it does not represent the character printed on that key. This means that there is no defined relationship between a make code and an ASCII code. It's up to the host to translate scan codes to characters or commands. Although most set two make codes are only one-byte wide, there are a handfull of "extended keys" whose make codes are two or four bytes wide. These make codes can be identified by the fact that their first byte is E0h. Just as a make code is sent to the computer whenever a key is pressed, a break code is sent whenever a key is released. In addition to every key having its own unique make code, they all have their own unique break code(1). Fortunately, however, you won't always have to use lookup tables to figure out a key's break code--certain relationships do exist between make codes and break codes. Most set two break codes are two bytes long where the first byte is F0h and the second byte is the make code for that key. Break codes for extended keys are usually three bytes long where the first two bytes are E0h, F0h, and the last byte is the last byte of that key's make code. As an example, I have listed below a the set two make codes and break codes for a few keys: If you press a key, its make code is sent to the computer. When you press and hold down a key, that key becomes typematic, which means the keyboard will keep sending that key's make code until the key is released or another key is pressed. To verify this, open a text editor and hold down the "A" key. When you first press the key, the character "a" immediately appears on your screen. After a short delay, another "a" will appear followed by a whole stream of "a"s until you release the "A" key. There are two important parameters here: the typematic delay, which is the short delay between the first and second "a", and the typematic rate, which is how many characters per second will appear on your screen after the typematic delay. The typematic delay can range from 0.25 seconds to 1.00 second and the typematic rate can range from 2.0 cps (characters per second) to 30.0 cps. You may change the typematic rate and delay using the "Set Typematic Rate/Delay" (0xF3) command.Example: What sequence of make codes and break codes should be sent to your computer for the character "G" to appear in a word processor? Since this is an upper-case letter, the sequence of events that need to take place are: press the "Shift" key, press the "G" key, release the "G" key, release the "Shift" key. The scan codes associated with these events are the following: make code for the "Shift" key (12h), make code for the "G" key (34h), break code for the "G" key(F0h,34h), break code for the "Shift" key (F0h,12h). Therefore, the data sent to your computer would be: 12h, 34h, F0h, 34h, F0h, 12h. Typematic data is not buffered within the keyboard. In the case where more than one key is held down, only the last key pressed becomes typematic. Typematic repeat then stops when that key is released, even though other keys may be held down. Reset: At power-on or software reset (see the "Reset" command) the keyboard performs a diagnostic self-test referred to as BAT (Basic Assurance Test) and loads the following default values:
When entering BAT, the keyboard enables its three LED indicators, and turns them off when BAT has completed. At this time, a BAT completion code of either 0xAA (BAT successful) or 0xFC (Error) is sent to the host. This BAT completion code must be sent 500~750 milliseconds after power-on. Many of the keyboards I've tested ignore their CLOCK and DATA lines until after the BAT completion code has been sent. Therefore, an "Inhibit" condition (CLOCK line low) may not prevent the keyboard from sending its BAT completion code. Command Set: A few notes regarding commands the host can issue to the keyboard:
The next six commands can be issued when the keyboard is in any mode, but it only effects the behavior of the keyboard when in "mode 3" (ie, set to scan code set 3.)
.
Delay
*Originally available in PS/2 keyboards only. Emulation:
Up to this point in the article, all information has been presented from a hardware point-of-view. However, if you're writing low-level keyboard-related software for the host PC, you won't be communicating directly with the keyboard. Instead, a keyboard controller provides an interface between the keyboard and the peripheral bus. This controller takes care of all the signal-level and protocol details, as well as providing some conversion, interpretation, and handling of scan codes and commands. An Intel 8042/compatible microcontroller is used as the PC's keyboard controller. In modern computers, this microcontroller is hidden within the motherboard's chipset, which integrates many controllers in a single package. Nonetheless, this device is still there, and the keyboard controller is still commonly referred to as "the 8042". Depending on the motherboard, the keyboard controller may operate in one of two modes: "AT-compatible" mode, or "PS/2-compatible" mode. The latter is used if a PS/2 mouse is supported by the motherboard. If this is the case, the 8042 acts as the keyboard controller and the mouse controller. The keyboard controller auto-detects which mode it is to use according to how it's wired to the keyboard port. The 8042 contains the following registers:
Writing to port 0x64 doesn't write to any specific register, but sends a command for the 8042 to interpret. If the command accepts a parameter, this parameter is sent to port 0x60. Likewise, any results returned by the command may be read from port 0x60. When describing the 8042, I may occasionally refer to its physical I/O pins. These pins are defined below: AT-compatible mode
PS/2-compatible mode
(Note: Reading keyboard controller datasheets can be confusing--it will refer to the "input buffer" as the "output buffer" and vice versa. This makes sense from the point-of-view of someone writing firmware for the controller, but for somebody used to interfacing the controller, this can cause problems. Throughout this document, I only refer to the "input buffer" as the one containing input from the keyboard, and the "output buffer" as the one that contains output to be sent to the keyboard.) Status Register: The 8042's status flags are read from port 0x64. They contain
error information, status information, and indicate whether or not data
is present in the input and output buffers. The flags are defined as
follows:
0: Output buffer empty - Okay to write to port 0x60 1: Output buffer full - Don't write to port 0x60 0: Input buffer empty - No unread input at port 0x60 1: Input buffer full - New input can be read from port 0x60 0: Power-up value - System is in power-on reset. 1: BAT code received - System has already beed initialized. 0: A2 = 0 - Port 0x60 was last written to 1: A2 = 1 - Port 0x64 was last written to 0: Keyboard Clock = 0 - Keyboard is inhibited 1: Keyboard Clock = 1 - Keyboard is not inhibited 0: No Error - Keyboard accepted the last byte written to it. 1: Timeout error - Keyboard didn't generate clock signals within 15 ms of "request-to-send". 0: No Error - Keyboard responded to last byte. 1: Timeout error - Keyboard didn't generate clock signals within 20 ms of command reception. 0: No Error - Odd parity received and proper command response recieved. 1: Parity Error - Even parity received or 0xFE received as command response. 0: Output buffer empty - Okay to write to auxillary device's output buffer 1: Output buffer full - Don't write to port auxillary device's output buffer 0: No Error - Keyboard received and responded to last command. 1: Timeout Error - See TxTO and RxTO for more information. Reading keyboard input: When the 8042 recieves a valid scan code from the keyboard, it is converted to its set 1 equivalent. The converted scan code is then placed in the input buffer, the IBF (Input Buffer Full) flag is set, and IRQ 1 is asserted. Furthermore, when any byte is received from the keyboard, the 8042 inhibits further reception (by pulling the "Clock" line low), so no other scan codes will be received until the input buffer is emptied. If enabled, IRQ 1 will activate the keyboard driver, pointed to by interrupt vector 0x09. The driver reads the scan code from port 0x60, which causes the 8042 to de-assert IRQ 1 and reset the IBF flag. The scan code is then processed by the driver, which responds to special key combinations and updates an area of the system RAM reserved for keyboard input. If you don't want to patch into interrupt 0x09, you may poll the keyboard controller for input. This is accomplished by disabling the 8042's IBF Interrupt and polling the IBF flag. This flag is set (1) when data is available in the input buffer, and is cleared (0) when data is read from the input buffer. Reading the input buffer is accomplished by reading from port 0x60, and the IBF flag is at port 0x64, bit 1. The following assembly code illustrates this: kbRead: Writing to keyboard: When you write to the 8042's output buffer (via port 0x60), the controller sets the OBF ("Output Buffer Full") flag and processes the data. The 8042 will send this data to the keyboard and wait for a response. If the keyboard does not accept or generate a response within a given amount of time, the appropriate timeout flag will be set (see Status register definition for more info.) If an incorrect parity bit is read, the 8042 will send the "Resend" (0xFE) command to the keyboard. If the keyboard continues to send erroneous bytes, the "Parity Error" flag is set in the Status register. If no errors occur, the response byte is placed in the input buffer, the IBF ("Input Buffer Full") flag is set, and IRQ 1 is activated, signaling the keyboard driver. The following assembly code shows how to write to the output buffer. (Remember, after you write to the output buffer, you should use int 9h or poll port 64h to get the keyboard's response.) kbWrite: Keyboard Controller Commands: Commands are sent to the keyboard controller by writing to port 0x64. Command parameters are written to port 0x60 after teh command is sent. Results are returned on port 0x60. Always test the OBF ("Output Buffer Full") flag before writing commands or parameters to the 8042.
0: IBF Interrupt Disabled - You must poll STATUS<IBF> to read input. 1: IBF Interrupt Enabled - Keyboard driver at software int 0x09 handles input. 0: Power-on value - Tells POST to perform power-on tests/initialization. 1: BAT code received - Tells POST to perform "warm boot" tests/initiailization. 0: Inhibit switch enabled - Keyboard inhibited if pin P17 is high. 1: Inhibit switch disabled - Keyboard not inhibited even if P17 = high. 0: Enable - Keyboard interface enabled. 1: Disable - All keyboard communication is disabled. 0: Disable - ??? 1: Enable - ??? 0: Translation disabled - Data appears at input buffer exactly as read from keyboard 1: Translation enabled - Scan codes translated to set 1 before put in input buffer 0: Auxillary IBF Interrupt Disabled - 1: Auxillary IBF Interrupt Enabled - 0: Enable - Auxillary PS/2 device interface enabled 1: Disable - Auxillary PS/2 device interface disabled
So far, I've only discussed the 8042 keyboard controller. Although modern keyboard controllers remain compatible with the original device, compatibility is their only requirement (and their goal.) My motherboard's keyboard controller is a great example of this. I connected a microcontroller+LCD in parallel to my keyboard to see what data is sent by the keyboard controller. At power-up, the keyboard controller sent the "Set LED state" command to turn off all LEDs, then reads the keyboard's ID. When I tried writing data to the output buffer, I found the keyboard controller only forwards the "Set LED state" command and "Set Typematic Rate/Delay" command. It does not allow any other commands to be sent to the keyboard. However, it does emulate the keyboard's response by placing "acknowledge" (0xFA) in the input buffer when appropriate (or 0xEE in response to the "Echo" command.) Furthermore, if the keyboard sends it an erroneous byte, the keyboard controller takes care of error handling (sends the "Retry" command; if byte still erroneous; sends error code to keyboard and places error code in input buffer.) Once again, keep in mind chipset designers are more interested in compatibility than standardization. Initialization: The following is the communication between my computer and keyboard when it boots-up. I beleive the first three commands were initiated by the keyboad controller, the next command (which enables Num lock LED) was sent by the BIOS, then the rest of the commands were sent my the OS (Win98SE). Remember, these results are specific to my computer, but it should give you a general idea as to what happens at startup. Keyboard: AA Self-test passed ;Keyboard controller init
|


- Game<T extends Game> - Interface in com.github.sahasatvik.game
-
Game
defines methods a class must implement in order to use the
com.github.sahasatvik.game
framework.
- game - Variable in class com.github.sahasatvik.game.MiniMax.GameTreeNode
-
- GameTreeNode(T) - Constructor for class com.github.sahasatvik.game.MiniMax.GameTreeNode
-
- getCopy() - Method in class com.github.sahasatvik.game.Board
-
- getCopy() - Method in interface com.github.sahasatvik.game.Game
-
Returns a copy of the current Game object.
- getCopy() - Method in class TicTacToeBoard
-
- getCopy() - Method in class TicTacToeGame
-
- getCurrentPlayer() - Method in interface com.github.sahasatvik.game.Game
-
Returns the Player who was the last to make a Move.
- getCurrentPlayer() - Method in class TicTacToeGame
-
- getItemAt(Point) - Method in class com.github.sahasatvik.game.Board
-
- getItemAt(int, int) - Method in class com.github.sahasatvik.game.Board
-
- getItemCount(T) - Method in class com.github.sahasatvik.game.Board
-
- getItemCount(Board<T>, List<Point>, T) - Static method in class com.github.sahasatvik.game.BoardSequencer
-
- getMove(T) - Method in interface com.github.sahasatvik.game.Player
-
Returns a Move
object based on the state of a Game
.
- getMove(TicTacToeGame) - Method in class ComputerPlayer
-
- getMove(TicTacToeGame) - Method in class HumanPlayer
-
- getNewGame() - Method in interface com.github.sahasatvik.game.Move
-
Returns the new Game
object contained in the Move
.
- getNextPlayer() - Method in interface com.github.sahasatvik.game.Game
-
Returns the Player who will be the next to make a Move.
- getNextPlayer() - Method in class TicTacToeGame
-
- getNextPlayerId() - Method in class TicTacToeGame
-
- getPiece(Player<TicTacToeGame>) - Method in class TicTacToeGame
-
- getPieces() - Method in class TicTacToeGame
-
- getPlayer(TicTacToePiece) - Method in class TicTacToeGame
-
- getPlayerCount() - Method in class TicTacToeGame
-
- getPlayers() - Method in interface com.github.sahasatvik.game.Game
-
Returns a List of Players participating in the Game.
- getPlayers() - Method in class TicTacToeGame
-
- getSequences(Board<?>, int) - Static method in class com.github.sahasatvik.game.BoardSequencer
-
- getValidMoves() - Method in interface com.github.sahasatvik.game.Game
-
Returns a List of all possible, valid Moves that can be applied on the
current Game.
- getValidMoves() - Method in class TicTacToeGame
-
- goal - Variable in class TicTacToeBoard
-


Cowboys vs. Bills final score: Buffalo silences Dallas in comfortable Thanksgiving win
by Eli BoettgerThe Bills recovered from a shaky start to topple the Cowboys 26-15 in a Thanksgiving drubbing at AT&T Stadium in Arlington, Texas.
Dallas (6-6) opened the game with a nine-play, 75-yard drive capped by an 8-yard Dak Prescott-to-Jason Witten touchdown strike that ignited the home crowd. The Cowboys' defense backed it up with two Bills punts, but Buffalo (9-3) dominated the remainder of the game en route to a convincing win.
MORE: NFL playoff picture
The Bills tied the score when former Cowboys receiver Cole Beasley scored on a 25-yard touchdown pass from Josh Allen. Dallas' next six drives concluded withan interception, a fumble, two missed field-goal attempts and two turnovers on downs while the Bills scored 26unanswered points.
MORE: Watch NFL games live with fuboTV (7-day free trial)
Quarterback Josh Allen shined in support of Buffalo's strong defensive effort. He completed 19 of 24 passes for 231 yards and a touchdown, and he added 43 yards and a touchdown on the ground.
VIDEO: Bills-Cowboys game highlights
The nine wins tie a franchise high for the Bills dating to 1999.
GARRETT STATUS UPDATE: Jerry Jones says coach still safe
Sporting News trackedlive updates, highlights and score changes for the Bills vs. Cowboys matchup on Thanksgiving.
Cowboys vs. Bills score on Thanksgiving 2019
FINAL
Bills: 26
Cowboys: 15
| Q1 | Q2 | Q3 | Q4 | F | |
| Bills | 0 | 13 | 10 | 3 | 26 |
| Cowboys | 7 | 0 | 0 | 8 | 15 |
Cowboys vs. Bills updates, highlights
(All times Eastern)
7:41 p.m.: Bills sneak it on fourth down for the first and will kneel it out to close out the victory.
7:33 p.m.: Dallas' onside kick provides little drama as Buffalo recovers.
7:31 p.m.: TOUCHDOWN, COWBOYS. Ventell Bryant is on the receiving end of a 15-yard touchdown from Prescott with 4:01 remaining to cut the deficit. The two-point attempt to Witten is good. Bills 26, Cowboys 15.
7:22 p.m.: The Cowboys are forced to go for it on fourth down but Prescott can't find anyone and the Bills strip the football and force the turnover on downs.
7:09 p.m.: FIELD GOAL, COWBOYS . Hauschka drills a 26-yarder to cap a drive that lasted over seven minutes. Dallas trails by three scores with eight minutes and change remaining. Bills 26, Cowboys 7.
7:07 p.m.: The Cowboys had what looked like a third-down stop but are called for pass interference to set up a Buffalo first-and-goal.
End of third quarter: Bills 23, Cowboys 7
6:56 p.m.: Cowboys go for it on fourth-and-goal from the Bills 6 and Prescott dumps a pass off to Elliott but the pass was massively off the mark and incomplete.
6:53 p.m.: Michael Gallup makes a tremendous effort to reel in a touchdown catch, which was initially called a score but will be overturned as Gallup's right foot was out of bounds.
6:42 p.m.: TOUCHDOWN, BILLS. Allen scrambles and navigates his way into the end zone for the touchdown run. Bills go up two scores. Bills 23, Cowboys 7.
6:35 p.m.: Maher misses his second field-goal attempt of the day and the Cowboys still have yet to score since their opening drive.
6:28 p.m.: FIELD GOAL, BILLS. Hauschka's 41-yard attempt bangs on the right upright but makes it through for three points to extend the lead. Bills 16, Cowboys 7.
6:21 p.m.: The Bills get the second half started on offense.
Halftime: Bills 13, Cowboys 7
Stats
First downs: Cowboys 18, Bills 10
Total yards: Cowboys 213, Bills 179
Passing yards: Cowboys 141, Bills 117
Rushing yards: Cowboys 72, Bills 62
Penalties: Cowboys 1-23, Bills 5-33
Turnovers: Bills 0, Cowboys 2
Possession: Cowboys 16:18, Bills 13:42
5:59 p.m.: Maher's 35-yard attempt to end the half is no good as the clock reaches triple zeroes.
5:52 p.m.: Prescott is intercepted again but the play is negated by a Bills penalty for illegal use of hands. Drive continues.
5:50 p.m.: TOUCHDOWN, BILLS. Buffalo pulls out the trickeration as John Brown's first NFL passing attempt goes to Devin Singletary for the touchdown. The extra-point attempt was missed. Bills 13, Cowboys 7.
5:40 p.m.: Another Prescott turnover. Ed Oliver comes from behind to knock the ball away from Prescott and the Bills are on it and again in plus territory.
5:35 p.m.: Stephen Hauschka's 50-yard attempt sails right and is no good.
5:31 p.m.: Prescott tried setting up a pass but his attempt was intercepted by Star Lotulelei and the Bills are within striking distance.
5:23 p.m.: TOUCHDOWN, BILLS. Josh Allen nails Cole Beasley on the move for a 25-yard touchdown score to tie it up. Cowboys 7, Bills 7.
5:16 p.m.: Dallas will punt it away and the Bills are set to go back on offense.
End of first quarter: Cowboys 7, Bills 0
5:04 p.m.: Buffalo crosses midfield but Dallas gets another stop, forcing another Bills punt.
4:55 p.m.: Dallas' run quickly stalls after the big run. The Cowboys pin the Bills at their own 3 following the punt.
4:54 p.m.: Another big run by Ezekiel Elliott, who is off to a hot start.
4:47 p.m.: Cowboys get off the field and force the Bills to punt.
4:40 p.m.: TOUCHDOWN, COWBOYS. Jason Witten has himself another Thanksgiving touchdown. Dak Prescott finds Witten on a delayed play-action pass for the 8-yard score. Cowboys 7, Bills 0.
4:34 p.m.: Cowboys are setting things up on offense to start the day.


Katie Price 'threatens to fly out to Oz over Emily Atack's Extra Camp dig
Katie Price has clapped back at Emily Atack’s dig and has threated to fly out to the I’m A Celebrity… Get Me Out Of Here! jungle to confront her.
During Tuesday’s Extra Camp, the former Inbetweeners star threw shade at Katie and Peter Andre by joking that presenters Joel Dommett and Adam Thomas needed to get tested for diseases after plunging into the same pool that the former couple first kissed in.
Advertisement Advertisement
‘This is where Katie Price and Peter Andre had fondles,’ Joel proudly boasted to his co-host. But back in the studio, Emily teased: ‘I hope you boys went to the clinic after being in that pool.’
Unsurprisingly, Katie wasn’t best pleased by Emily’s comments and, according to reports, made it clear that the actress would have a ‘problem’ if she wanted one.
An insider said: ‘Katie says she’s not watching the show, but when Emily Atack mentioned her on Extra Camp all her friends told her what she said.
‘She was telling people that she can’t believe Emily would say something so snide and if she “wants a problem, I’ll give her a problem”.’
They added to The Sun: ‘At one point Katie was saying she’d fly out to Australia and confront her. She’s not going to, obviously, but she was asking around to see if anyone had Emily’s number.
Katie and Peter starred in the third series of I’m A Celebrity in 2004 and it was where their relationship first began.
The pair married the following year but divorced back in 2009. They share two children together, Princess, 12, and Junior, 14.
Advertisement Advertisement
Back in July, Katie unearthed her rotting backpack from the ITV series containing a crumpled uniform and a water bottle – and she drank the 15-year-old liquid.
Metro.co.uk reached out to Katie’s rep for comment.
I’m A Celebrity… Get Me Out Of Here! airs tonight at 9pm on ITV.
Got a showbiz story?
If you've got a story, video or pictures get in touch with the Metro.co.uk Entertainment team by emailing us<EMAIL_ADDRESS>calling 020 3615 2145 or by visiting our Submit Stuff page - we'd love to hear from you.


Copyright (c) 2001 Bill Taylor
This game is played on the following 8x8 square board:
|
| An example White moved the marked stone and wins the game. Black cannot win this race. |
There is a ZRF to play Pawnographic Chess with Zillions.
Independently, Michael Jørgensen, had almost the same idea, which he called "Touchdown", played on a board with 4 rows and 8 columns (but it may change to any size) where the stones start in the first and last row, and a stalemate means a draw.


READELF
Section: GNU Development Tools (1)Updated: 2012-06-22
Index Return to Main Contents
NAME
readelf - Displays information about ELF files.SYNOPSIS
readelf [-a|--all][-h|--file-header]
[-l|--program-headers|--segments]
[-S|--section-headers|--sections]
[-g|--section-groups]
[-t|--section-details]
[-e|--headers]
[-s|--syms|--symbols]
[-n|--notes]
[-r|--relocs]
[-u|--unwind]
[-d|--dynamic]
[-V|--version-info]
[-A|--arch-specific]
[-D|--use-dynamic]
[-x <number or name>|--hex-dump=<number or name>]
[-p <number or name>|--string-dump=<number or name>]
[-R <number or name>|--relocated-dump=<number or name>]
[-c|--archive-index]
[-w[lLiaprmfFsoR]|
--debug-dump[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges]]
[-I|-histogram]
[-v|--version]
[-W|--wide]
[-H|--help]
elffile...
DESCRIPTION
readelf displays information about one or more ELF format object files. The options control what particular information to display.elffile... are the object files to be examined. 32-bit and 64-bit ELF files are supported, as are archives containing ELF files.
This program performs a similar function to objdump but it goes into more detail and it exists independently of the BFD library, so if there is a bug in BFD then readelf will not be affected.
OPTIONS
The long and short forms of options, shown here as alternatives, are equivalent. At least one option besides -v or -H must be given.- -a
- --all
- Equivalent to specifying --file-header, --program-headers, --sections, --symbols, --relocs, --dynamic, --notes and --version-info.
- -h
- --file-header
- Displays the information contained in the ELF header at the start of the file.
- -l
- --program-headers
- --segments
- Displays the information contained in the file's segment headers, if it has any.
- -S
- --sections
- --section-headers
- Displays the information contained in the file's section headers, if it has any.
- -g
- --section-groups
- Displays the information contained in the file's section groups, if it has any.
- -t
- --section-details
- Displays the detailed section information. Implies -S.
- -s
- --symbols
- --syms
- Displays the entries in symbol table section of the file, if it has one.
- -e
- --headers
- Display all the headers in the file. Equivalent to -h -l -S.
- -n
- --notes
- Displays the contents of the NOTE segments and/or sections, if any.
- -r
- --relocs
- Displays the contents of the file's relocation section, if it has one.
- -u
- --unwind
- Displays the contents of the file's unwind section, if it has one. Only the unwind sections for IA64 ELF files are currently supported.
- -d
- --dynamic
- Displays the contents of the file's dynamic section, if it has one.
- -V
- --version-info
- Displays the contents of the version sections in the file, it they exist.
- -A
- --arch-specific
- Displays architecture-specific information in the file, if there is any.
- -D
- --use-dynamic
- When displaying symbols, this option makes readelf use the symbol table in the file's dynamic section, rather than the one in the symbols section.
- -x <number or name>
- --hex-dump=<number or name>
- Displays the contents of the indicated section as a hexadecimal bytes. A number identifies a particular section by index in the section table; any other string identifies all sections with that name in the object file.
- -R <number or name>
- --relocated-dump=<number or name>
- Displays the contents of the indicated section as a hexadecimal bytes. A number identifies a particular section by index in the section table; any other string identifies all sections with that name in the object file. The contents of the section will be relocated before they are displayed.
- -p <number or name>
- --string-dump=<number or name>
- Displays the contents of the indicated section as printable strings. A number identifies a particular section by index in the section table; any other string identifies all sections with that name in the object file.
- -c
- --archive-index
- Displays the file symbol index infomation contained in the header part of binary archives. Performs the same function as the t command to ar, but without using the BFD library.
- -w[lLiaprmfFsoR]
- --debug-dump[=rawline,=decodedline,=info,=abbrev,=pubnames,=aranges,=macro,=frames,=frames-interp,=str,=loc,=Ranges]
-
Displays the contents of the debug sections in the file, if any are
present. If one of the optional letters or words follows the switch
then only data found in those specific sections will be dumped.
Note: the =decodedline option will display the interpreted contents of a .debug_line section whereas the =rawline option dumps the contents in a raw format.
- -I
- --histogram
- Display a histogram of bucket list lengths when displaying the contents of the symbol tables.
- -v
- --version
- Display the version number of readelf.
- -W
- --wide
- Don't break output lines to fit into 80 columns. By default readelf breaks section header and segment listing lines for 64-bit ELF files, so that they fit into 80 columns. This option causes readelf to print each section header resp. each segment one a single line, which is far more readable on terminals wider than 80 columns.
- -H
- --help
- Display the command line options understood by readelf.
- @file
-
Read command-line options from file. The options read are
inserted in place of the original @file option. If file
does not exist, or cannot be read, then the option will be treated
literally, and not removed.
Options in file are separated by whitespace. A whitespace character may be included in an option by surrounding the entire option in either single or double quotes. Any character (including a backslash) may be included by prefixing the character to be included with a backslash. The file may itself contain additional @file options; any such options will be processed recursively.
SEE ALSO
objdump(1), and the Info entries for binutils.COPYRIGHT
Copyright (c) 1991, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc.Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled ``GNU Free Documentation License''.
Index
This document was created by man2html, using the manual pages.
Time: 05:29:09 GMT, December 24, 2015


FBI: Cybercrimes on the rise
PORTLAND, Ore. (AP) - FBI agents in Oregon say the number of computer-related crimes has soared in the state, with losses surpassing $24 million this year alone.
Most of the money has been stolen by organized crime groups targeting individuals and employees of organizations with access to a lot of money. They trick victims into making wire transfers to bank accounts controlled by the criminals.
The FBI said Friday that in 2018, $12.4 million was stolen from victims in Oregon using this so-called business email compromise. From January through Sept. 30 of 2019, losses totaled around $12 million, on track to exceed last year. Other cybercrimes include romance scams and extortion.
The Portland school district was targeted recently, with almost $3 million lost but recovered because of quick reporting and action.
Sign up for Daily Newsletters
Copyright © 2019 The Washington Times, LLC.
Please read our comment policy before commenting.


Enter your name:
29%
88%
20%
10%
Eyes
Throat
Groin
All of the above
3-4
1-2
10 or more
I don't know
.. are not shown until used.
... shown and used as threats first.
... easily visible before the fight begins
I don't know.
2
2-3
1
4 or more
Mace/Pepper Spray
Whistle
Keys
None of the Above
Yes
No
It's depend
I don't know
Unbreakable Umbrella
Pocket Change
Backpack
All of the Above
Yes
No
It depends on your surroundings.
I don't know.
Yes
No
It doesn't matter
I don't know.
Your Score:


Search
Username
Personal Profile
Watching List
Pending List
Logout
Personal Profile
Profile For :
Traveller
Provider
Name:
Gender:
Email:
Phone:
Submit
Review area:
Star:
Submit
History:
Surburb
Postcode
Address
StartTime
EndTime
Surburb
Postcode
Address
StartTime
EndTime
Surburb
Postcode
Address
StartTime
EndTime
Release Accomondation Needed Information
Review area:


Suspendisse et arcu feilis ...
See our portfolio
Suspendisse et arcu felis ...
See what's new!
Meet the team!


---
layout: post
title: Prompting when leaving the page
tags: []
status: publish
type: post
published: true
meta: {}
---
Over at 4 Guys from Rolla there is a really useful technique that takes advanatge of the onbeforeunload javascript event to prompt a user that he is leaving a page. The author goes into even more detail on how to use this event to check if any changes were made and then prompt the user to save these or these will be lost. Very neat, though it's worth pointing out, it only works with the latest browser version (inlcusing FireFox 0.9 and higher).


---
layout: post
title: ! 'Next Meetup: Tuesday October 2nd 7:30pm'
alias: /next-meetup-tuesday-october-2nd-730pm-64801
published: true
---
Hello!
Next month will be the first IPRUG that I'm supposed to be organising,
but fortunately Tom will still be around so hopefully I won't forget
to do anything important. We've got two talks pencilled in, from Max Shelley (@maxshelley) and
Frank Carver (@efficacy). If you guys let me know the talk titles I'll
update the page (assuming I can figure out how). Usual time and place – 7.30pm at the Brewery Tap. Hope to see you all there! Kerry


--- layout: default ---
I am a Software Engineer with a passion for technology and have enjoyed all aspects of it from a young age. I started developing and the first application that stands out in my memory was an application I wrote in junior high in QBasic that drew the Mandelbrot set. From there I have kept working on or around development and have always had a driving interest in creating and inventing.