{% extends "pdf_templates/pdf_base.html" %}
{% load static %}
{% load tz %}
{% block body %}
{% for event_data in events_data %}
|
- c/o Student Activities Office
- 100 Institute Road
- Worcester, MA 01609-2280
- Office:<PHONE_NUMBER>
-<EMAIL_ADDRESS>{% if request %}
- https://lnl.wpi.edu/
{% endif %}
|
{% if event_data.event.reviewed %}INVOICE{% else %}QUOTE{% endif %}
{{ event_data.event.event_name }}
Generated Date: {% now "M. j, Y" %}
|
| Location: |
{{ event_data.event.location }} |
Setup By: |
{{ event_data.event.datetime_setup_complete|localtime }} |
| Organization: |
{{ event_data.event.org.all|join:", " }} |
Event Start: |
{{ event_data.event.datetime_start|localtime }} |
| Billed Account: |
{{ event_data.event.worktag }} |
Event End: |
{{ event_data.event.datetime_end|localtime }} |
Overview: {{ event_data.event.description }}
{% for service in event_data.event.eventservices %}
| {{service}} |
$ {{ service.base_cost|floatformat:2 }} |
{% endfor %}
{% for cat, cat_e in event_data.extras.items %}
| {{ cat }} Extras |
|
{% for e in cat_e %}
| {{ e.extra }} [x{{ e.quant }}] |
$ {{ e.totalcost|floatformat:2 }} |
{% endfor %}
{% endfor %}
{% if event_data.event.oneoffs %}
| Additional Fees |
|
{% for fee in event_data.event.oneoffs %}
| {{ fee.key_name }} [{{ fee.key_value|floatformat:2}}x{{ fee.key_quantity }}] |
$ {{ fee.totalcost|floatformat:2 }} |
{% endfor %}
{% endif %}
{% if event_data.event.discount_applied %}
| Subtotal |
$ {{ event_data.event.cost_total_pre_discount|floatformat:2 }} |
| Combo Event Discount |
$ -{{ event_data.event.discount_value|floatformat:2 }} |
{% endif %}
| ***EVENT TOTAL*** |
$ {{ event_data.event.cost_total|floatformat:2 }} |
{% if event_data.event.reviewed %}
| Visit {{ request.get_host }}{% url 'events:worktag-form' event_data.event.pk %} to pay this Invoice. |
If you have any questions concerning this invoice, contact our treasurer at<EMAIL_ADDRESS>|
{% else %}
|
This is a quote of the expected charges based on the current information from the client.
Charges may change based on a variety of factors, including additional requests or information from the client, even those received day-of at the event.
We will do our best to inform the listed contact of any charges in advance, but this is not guaranteed.
|
If you have any questions concerning this quote, contact our vice-president at<EMAIL_ADDRESS>|
{% endif %}
{% endfor %}
{% endblock %}


turbo.tcpserver – Callback based TCP socket Server
A simple non-blocking extensible TCP Server based on the IOStream class.
Includes SSL support. Used as base for the Turbo HTTP Server.
TCPServer class
A non-blocking TCP server class.
Users which want to create a TCP server should inherit from this class and
implement the TCPServer:handle_stream() method. Optional SSL support is provided.
-
TCPServer(io_loop, ssl_options, max_buffer_size)
Create a new TCPServer class instance. If the SSL certificates is provided and can not be loaded, a error is raised.
| Parameters: |
- io_loop (turbo.ioloop.IOLoop instance) – Provide specific IOLoop class instance. If not provided the global instance is used.
- ssl_options (Table) – Optional SSL parameters.
- max_buffer_size (Number) – The maximum buffer size of the server. If the limit is hit, the connection is closed.
|
| Return type: | TCPServer class instance
|
Available ssl_options keys:
- “key_file” (String) - Path to SSL key file if a SSL enabled server is wanted.
- “cert_file” (String) - Path to certificate file. key_file must also be set.
-
TCPServer:handle_stream(stream, address)
This method is called by the class when clients connect. Implement this method in inheriting class to handle new connections.
| Parameters: |
- stream (turbo.iostream.IOStream instance) – Stream for the newly connected client.
- address (String) – IP address of newly connected client.
|
-
TCPServer:listen(port, address, backlog, family)
Start listening on port and address. When using this method, as oposed to TCPServer:bind you should not call
TCPServer:start. You can call this method multiple times with different parameters to bind multiple sockets to the same TCPServer.
| Parameters: |
- port (Number) – The port number to bind to.
- address (Number) – The address to bind to in unsigned integer hostlong format. If not address is given, turbo.socket.INADDR_ANY will be used, binding to all addresses.
- backlog (Number) – Maximum backlogged client connects to allow. If not defined then 128 is used as default.
- family (Number) – Optional socket family. All socket familys are defined in turbo.socket module. If not defined AF_INET is used as default.
|
-
TCPServer:add_sockets(sockets)
Add multiple sockets in a table that should be bound on calling start. Use the turbo.sockutil.bind_sockets function to create sockets easily and add them to the sockets table.
| Parameters: | sockets (Table) – 1 or more socket fd’s. |
-
TCPServer:add_socket(socket)
Single socket version of TCPServer:add_socket.
| Parameters: | socket (Number) – Socket fd. |
-
TCPServer:bind(port, address, backlog, family)
Bind this server to port and address. User must also call TCPServer:start to start listening on the bound socket.
| Parameters: |
- port (Number) – The port number to bind to.
- address (Number) – The address to bind to in unsigned integer hostlong format. If not address is given, turbo.socket.INADDR_ANY will be used, binding to all addresses.
- backlog (Number) – Maximum backlogged client connects to allow. If not defined then 128 is used as default.
- family (Number) – Optional socket family. All socket familys are defined in turbo.socket module. If not defined AF_INET is used as default.
|
-
TCPServer:start()
Start the TCPServer, accepting conncetions on bound sockets.
-
TCPServer:stop()
Stop the TCPServer. Closing all the sockets bound to it. Before restarting the TCPServer, the socket must be readded.


For information about Selenium commands and locators, see Selenium Reference.
Reference > Top| Extended General Interface object locators | ||
| Command/Locator | Usage | Description |
| jsxselector | | command | jsxselector=#jsxname | | |
Select objects from the DOM using a CSS3-like selection syntax. This method considers the DOM tree whose root is this object. The following constructs are supported:
* jsx3_gui_ClassName - matches objects by their exact class. Replace "." with "_" in the selector. * * - matches any object * #jsxname - matches objects whose name equals jsxname * .class-name - matches objects for which getClassName() is defined and returns a string that contains the token class-name * :first and :last - matches objects that are their parents' first and last children * :nth(n) and nth-child(n) - matches objects whose child index is equal to n * :instanceof(ClassName) - matches objects that are instances of the class or interface ClassName * [prop="value"] and [prop*="value"] - matches objects whose value for field prop equals value or, with "*", contains value. The quotes around value are optional. * [getter()="value"] and [getter()*="value"] - matches objects whose return value for method getter equals value or, with "*", contains value. The quotes around value are optional. AB - matches objects that match both A and B * A B - matches descendants of objects matching A that match B * A > B - matches immediate children of objects matching A that match B |
| gi | | command | gi=xpath-like-dom-expression | | |
GI DOM locator<EMAIL_ADDRESS>gi=.jsx3.gui.Splitter - locate first object of type splitter gi=//message - locate control with jsxname "message" gi=//toolBar/[@jsxtext="List"] -locate control (toolbar button) with jsxtext="List" under control named "toolBar" gi=//[@jsxtext="List"] -locate control with jsxtext "List" (a toolbar button) gi=//toolBar/jsx3.gui.ToolbarButton - locate first ToolbarButton under "toolBar" gi=//toolBar/jsx3.gui.ToolbarButton[3] - locate the third ToolbarButton under toolBar gi=paneMatrix/tblTable,rowbyindex,0 gi=tblTable,cellbyjsxid,1.2 |
| JsxAlertCaption | | command | JsxAlertCaption=alert box caption text | | |
Locator - element by alert caption text (glob and regexp pattern allowed). |
| JsxAlertText | | command | JsxAlertText=alert box content text | | |
Locator - element by alert context text (glob and regexp pattern allowed). |
| JsxDialogCaption | | command | JsxDialogCaption=dialog caption text | | |
Locator - element by dialog caption text (glob and regexp pattern allowed). |
| JsxDialogName | | command | JsxDialogName=jsxname | | |
Locator - element by dialog jsxname. |
| JsxButtonName | | command | JsxButtonName=jsxname | | |
Locator - element by button jsxname. |
| JsxButtonText | | command | JsxButtonText=label_text | | |
Locator - element by button label text (glob and regexp pattern allowed) |
| JsxDateName | | command | JsxDateName=jsxname | | |
Locator - element by date picker jsxname |
| JsxDateInput | | command | JsxDateName=jsxname | | |
Locator - input element in date picker. NEW in 3.2.0 |
| JsxDateIcon | | command | JsxDateName=jsxname | | |
Locator - icon element in date picker. NEW in 3.2.0 |
| JsxDateDay | | command | JsxDateDay=jsxname,day | | |
Locator - day element by date picker jsxname and day value (1-31). |
| JsxDatePrevYear | | command | JsxDatePrevYear=jsxname | | |
Locator - previous year element by date picker jsxname |
| JsxDateNextYear | | command | JsxDateNextYear=jsxname | | |
Locator - next year element by date picker jsxname |
| JsxDatePrevMonth | | command | JsxDatePrevMonth=jsxname | | |
Locator - previous month element by date picker jsxname |
| JsxDateNextMonth | | command | JsxDateNextMonth=jsxname | | |
Locator - next month element by date picker jsxname |
Example : gridResult.1.3 return cell in row with jsxid=1 and column=3 |
||
NOTE this locator is not exact, you should use ListRowId locator instead |
||
| JsxMatrixHeaderIndex | | command | JsxMatrixHeaderIndex=jsxname,columnIndex | | |
Locator - element for matrix header cell by list jsxname and column index  |
| JsxMatrixName | | command | JsxMatrixName=jsxname | | |
Locator - element for Matrix by jsxname  |
| JsxMatrixHScroller | | command | JsxMatrixHScroller=jsxname | | |
Locator - element horizontal scroll bar for Matrix by jsxname |
| JsxMatrixVScroller | | command | JsxMatrixVScroller=jsxname | | |
Locator - element vertical scroll bar for Matrix by jsxname |
| JsxMatrixRowId | | command | JsxMatrixRowId=jsxname,record jsxid |
Locator - element for a List type Matrix row by jsxname and record jsxid. |
| JsxMatrixRowIndex | | command | JsxMatrixRowIndex=jsxname,row index |
Locator - element for a List type Matrix row by jsxname and row index (1 based). |
| JsxMatrixRowText | | command | JsxMatrixRowText=jsxname,text pattern | | |
Locator - element list row by the text pattern in the List Matrix (glob and regexp pattern allowed). NOTE: if there are multiple row with same text pattern, this locator returns the first row with the text pattern. |
| JsxMatrixCellId | | command | JsxMatrixCellIndex=jsxname.jsxid.columnIndex | | |
Locator - element for a cell in a Grid type Matrix by jsxname, record jsxid, and column index. |
| JsxMatrixCellIndex | | command | JsxMatrixCellIndex=jsxname.rowIndex.columnIndex | | |
Locator - element for a cell in a Grid type Matrix by jsxname, row index, and column index. |
| JsxMatrixTreeItemId | | command | JsxMatrixTreeItemId=jsxname,jsxid | | |
Locator - element for an item in a tree type Matrix by jsxname and jsxid. |
| JsxMatrixTreeItemIndex | | command | JsxMatrixTreeItemIndex=jsxname,1 | | |
Locator - element for an item in a tree type Matrix by jsxname and index |
| JsxMatrixTreeItemText | | command | JsxMatrixTreeItemText=jsxname,text pattern | | |
Locator - element for an item in a tree type Matrix by jsxname and node text |
| JsxMenuWindowId | | command | JsxMenuWindowId=(1,2,3,4...) | | |
Locator - element by WindowId. Locate the drop down menu window |
| JsxMenuName | | command | JsxMenuName=jsxname | | |
Locator - element by menu jsxname. Locate the menu anchor object. |
| JsxMenuText | | command | JsxMenuText=menu label text | | |
Locator - element by menu label text (glob and regexp pattern allowed). Locate the menu anchor object. |
| JsxMenuItemIndex |
| command | JsxMenuItemIndex=jsxname,1| | |
Locator - element for menu item by menu jsxname and item index |
| JsxMenuItemId | | command | JsxMenuItemId=jsxname,jsxid| | |
Locator - element by menu jsxname and item jsxid. Locate menu item. |
| JsxMenuItemText | | command | JsxMenuItemText=jsxname,text pattern | | |
Locator - element for menu item by menu item label text (glob and regexp pattern allowed). |
| JsxRadioName | | command | JsxRadioName=jsxname | | |
Locator - element by RadioButton jsxname. |
| JsxRadioText | | command | JsxRadioText=text pattern | | |
Locator - element by RadioButton label text. |
| JsxRadioValue | | command | JsxRadioName=radio value | | |
Locator - element by RadioButton value attribute. Radio button value are unique within a RadioGroup. |
| JsxSliderName | | command | JsxSliderName=jsxname | | |
Locator - element for slider itself by Slider jsxname. |
| JsxSliderHandle |
| command | JsxSliderHandle=jsxname | | |
Locator - element for the handle by Slider jsxname. |
| JsxSelectWindow | | command | JsxSelectWindow=1 | | |
Locator - element Locate the select drop down window |
| JsxSelectName | | command | JsxSelectName=jsxname | | |
Locator - element by select/combo jsxname. |
| JsxSelectItemId | | command | JsxSelectItemId=jsxname,id1| | |
Locator - element by select jsxname and item jsxid |
| JsxSelectItemIndex | | command | JsxSelectItemIndex=jsxname,3| | |
Locator - element by select jsxname and item index (item #1, #2, etc..) |
| JsxSelectItemText | | command | JsxSelectItemId=jsxname,text pattern| | |
Locator - element by select jsxname and item text (glob and regexp pattern allowed) |
| JsxSplitterName | | command | JsxSplitterName=jsxname | | |
Locator - element by Splitter jsxname. |
| JsxStackName | | command | JsxStackName=jsxname | | |
Locator - element by stack jsxname |
| JsxStackText | | command | JsxStackText=stack label text | | |
Locator - element by stack label text (glob and regexp pattern allowed) |
| JsxTimePickerHours | | command | JsxTimePickerHours=jsxname | | |
Locator - element for Hour input by TimePicker jsxname |
| JsxTimePickerMinutes | | command | JsxTimePickerMinutes=jsxname | | |
Locator - element for Minutes input by TimePicker jsxname |
| JsxTimePickerSeconds | | command | JsxTimePickerSeconds=jsxname | | |
Locator - element for Seconds input by TimePicker jsxname |
| JsxTimePickerMillis | | command | JsxTimePickerSeconds=jsxname | | |
Locator - element for Milliseconds input by TimePicker jsxname |
| JsxTimePickerAmPm | | command | JsxTimePickerSeconds=jsxname | | |
Locator - element for AMPM input by TimePicker jsxname |
| JsxTimePickerSpinUp | | command | JsxTimePickerSeconds=jsxname | | |
Locator - element for up spinner input by TimePicker jsxname |
| JsxTimePickerSpinDown | | command | JsxTimePickerSeconds=jsxname | | |
Locator - element for down spinner input by TimePicker jsxname |
| JsxTabName | | command | JsxTabName=jsxname | | |
Locator - element by Tab jsxname |
| JsxTabText | | command | JsxTabText=Tab label text | | |
Locator - element by Tab label text (glob and regexp pattern allowed) |
| JsxTextboxName | | command | JsxTextboxName=jsxname | | |
Locator - element by Textbox jsxname. |
| JsxToolbarButtonName | | command | JsxToolbarButtonName=jsxname | | |
Locator - element by toolbar button jsxname. |
| JsxToolbarButtonText | | command | JsxToolbarButtonText=jsxname | | |
Locator - element by toolbar button label text (glob and regexp pattern allowed). |
| JsxTreeName | | command | JsxTreeName=jsxname | | |
Locator - element by tree jsxname. |
| JsxTreeItemId | | command | JsxTreeItemId=jsxname,jsxid | | |
Locator - element of tree item by tree jsxname and tree record jsxid. |
| JsxTreeItemIndex |
| command | JsxTreeItemIndex=jsxname,index | | |
Locator - element of tree item by tree jsxname and tree item index. |
| JsxTreeItemText | | command | JsxTreeItemText=jsxname,text pattern | | |
Locator - element of tree item by tree jsxname and tree record text (glob and regexp pattern allowed) . |
| JsxName | | command | JsxName=jsxname | | |
Locator - generic locator for any jsxtype element by jsxname. |
| JsxText | | command | JsxText=text pattern | | |
Locator - generic locator for any jsxtype element with given jsxtext="*some text*". e.g. JsxText=*ZIPCODE* |
| JsxValue | | command | JsxValue=text pattern | | |
Locator - generic locator for any jsxtype element with given jsxvalue="*some value*". e.g. JsxValue=*PALO ALTO* |
For information about Selenium commands and locators, see Selenium Reference.


${imports.html}
bioCAD™ Cloud
Recover password
Recover
New to bioCAD Cloud? Sign up.
Have account? Login.
${footer.html}


LinuxChix is open to women interested in Linux and Free Software, and women and men interested in supporting women in computing.
LinuxChix has two main worldwide online forums: email lists and IRC chat. These forums are English language. If you're interested in Linux or supporting women in computing you are welcome. You could also join, or start, a regional chapter of LinuxChix.
If you have any trouble joining a LinuxChix forum, please consult Who runs LinuxChix and ask the relevant volunteer for help.
You can help us promote LinuxChix by adding a LinuxChix badge to your web site.
Before joining, review our membership policies and remember: be polite, be helpful!


---
layout: newhome
author_profile: false
sidebar: false
---
Hi, my name is
I am a Software Developer based in South Korea.
Chae Rim Kim;
I focus on designing and developing quality applications and services.
I’ve been building up my web development skills in Python, Flask, Django, Java, HTML/CSS and JavaScript.
cat README.md
👋🏼 Hi! I focus on creating well-designed and elegant web applications. I am interested in both frontend and backend, and am open to learning new frameworks as I go.
cat MORE.md
👩🏻💻 Academically, I have obtained a First-Class Honours degree in BSc Computer Science from the University of Leeds, where I graduated with an exceptional dissertation grade.
ls skills
Python, Java, Flask & Django , HTML/CSS , MySQL, Git

Look through my projects, what I'm working on and the issues I'm currently interested in!
See the details of my projects here.
If you’d like to chat, get in touch with me!
저는 항상 발전하는 사람으로서, 후에 누군가를 멘토링 해 줄 수 있는 역량을 가진 사람이 되고싶습니다.
시작한 일에 대해서는 결과를 도출해내고, 지난 일에 대해서는 아쉬웠던 점을 드릴 다운하여 완연한 내 것으로 만든다는 마인드로 임하고 있습니다.


{{ define "main" }} {{- partial "header_2.html" . -}}
We were unable to locate your business Dimension Engineers in our records. There could be two reasons why this could have happened.
Your business Dimension Engineers has never availed any credit facilities in the past.
Information pertaining to the credit facilities availed by Dimension Engineers has not been submitted to CIBIL by the Credit Institutions
The information submitted by you for Dimension Engineers may be incorrect.
The business details you submitted is shown below. We recommend you cross check this information entered with any of the bank accounts you have taken a loan for your proprietorship
| Business Name | Dimension Engineers |
| Business PAN | ALUPM1234T |
| Business GST No. | 22AAAAA0000A1Z5 |
| Registered Address | H.No. 4/259/A, Near 4 Pillars Hotel, Panaji, North Goa |
| Pincode | 403001 |
| State | Goa |
| City | Panaji |
| Mobile Number | +91<PHONE_NUMBER> |


Still Under Development
This game started out as a one year competition, but evolved into much more than that. Years later, it is still a mountainous task. Instead of dreading the endless march, I've decided to celebrate what has been accomplished so far with this site. Please browse the links above to see the incredible contributions from talented people, and if I make any major progress I'll keep this site updated with the latest.


T
- the type to managepublic interface BarbelHisto<T>
BarbelHisto
that provides the client API.
Clients should perform all operations with this interface. BarbelHisto histo = BarbelHistoBuilder.barbel().build();
BarbelHistoBuilder
documentation to learn about the different
settings clients can choose.BarbelHisto
tracks two time dimensions: BarbelHisto
clients must annotate their classes
with DocumentId
on the primary key. An example:
public class SomeBusinessPojo {
@DocumentId
private String documentId;
... any custom fields and methods
public String getDocumentId() {
return documentId;
}
public void setDocumentId(String id) {
this.documentId = id;
}
}
The primary key should be business oriented, i.e. personnel number, contract
number. BarbelMode
s can be used to manage different types of objects:
BarbelMode.POJO
is the default mode. Of course, using POJO mode is
the easiest way forward. However, behind the scenes BarbelHisto
uses
proxying when managing POJOs to store the version data with the objects that
clients save. Proxying can become complicated in some situations. For that
reason there is another mode called BarbelMode.BITEMPORAL
. One can
change the mode to BarbelMode.BITEMPORAL
with the
BarbelHistoBuilder.withMode(BarbelMode)
method like so:
BarbelHisto barbel = BarbelHistoBuilder.barbel().withMode(BarbelMode.BITEMPORAL).build();If
BarbelMode.BITEMPORAL
is used clients have to implement the
interface Bitemporal
on the type they wish to manage with
BarbelHisto
. In this mode, there won't be any proxying magic applied
to objects. When clients implement the interface Bitemporal
they need
to declare a field of type BitemporalStamp
in the business object
type. There is nothing else required than declaring the field. Anything else
is managed by BarbelHisto
. See DefaultDocument
as an example
of a fully equipped business class in BarbelMode.BITEMPORAL
. BarbelHisto
. Clients only need
to take care that their primary key is properly set.save(Object, LocalDate, LocalDate)
method to save objects to
BarbelHisto
. The from/until period entered describes when the object
data should become effective, and until it should be effective. Clients use
LocalDate.MAX
to express that the object stored is valid until
infinite. BarbelHisto
clients can use
retrieveOne(Query)
or
retrieve(Query)
. Use the BarbelQueries
for
convenience like so:
List result = core.retrieve(BarbelQueries.allActive(someBusinessPojo.getDocumentId()), BarbelQueryOptions.sortAscendingByEffectiveFrom());Users should become familiar with all the queries in
BarbelQueries
.
unload(Object...)
after processing data with
BarbelHisto
. To restore the journal later to continue bitemporal data
processing use load(Collection)
. timeshift(Object, LocalDateTime)
to turn back time and see how
document journals looked like in the past. Time shift is one of the core
functionalities of BarbelHisto
. Clients can turn back time to see how
the document journals for a document Id looked like at that given time. This
knowledge is mission critical for many businesses. Notice that this method
returns complete journals of a given document Id. It is often the case that
objects effective periods change over time as updates are posted to
BarbelHisto
with different effective periods. Today a document may
have two active effective periods, one period A starting two years ago, and
another one period B effective beginning in two weeks, e.g. an adress change
to an initial client record that the client communicated two weeks ago.
Today: 2019-02-01 Effective from Effective Until Created at Adress 2017-01-01 2019-02-14 2016-12-15 Barbel-Street 1 Period A 2019-02-14 Infinite 2019-01-15 Carp-Street 10 Period BIn this example three weeks ago on January 9, 2019 that adress change in question was not recorded to the system. If you turn back time to January 9, 2019 that journal returned by time shift would only contain the effective period A. These cases can get more complex obviously the more updates are posted for a given document Id. Use
prettyPrintJournal(Object)
to get more familiar with
effective periods and record time. | Modifier and Type | Method and Description |
|---|---|
boolean |
contains(Object documentId)
Check if
BarbelHisto contains data for the given document ID. |
void |
load(Collection<Bitemporal> bitemporals)
Method for clients that use a custom data store.
|
String |
prettyPrintJournal(Object id)
Pretty print the journal for the given document ID.
|
List<T> |
retrieve(com.googlecode.cqengine.query.Query<T> query)
Retrieve data from
BarbelHisto using cqengine like queries. |
List<T> |
retrieve(com.googlecode.cqengine.query.Query<T> query,
com.googlecode.cqengine.query.option.QueryOptions options)
Retrieve data from
BarbelHisto using cqengine like queries. |
T |
retrieveOne(com.googlecode.cqengine.query.Query<T> query)
Retrieve data from
BarbelHisto using cqengine like queries. |
T |
retrieveOne(com.googlecode.cqengine.query.Query<T> query,
com.googlecode.cqengine.query.option.QueryOptions options)
Retrieve data from
BarbelHisto using cqengine like queries. |
T |
save(T newVersion,
LocalDate from,
LocalDate until)
Save objects to
BarbelHisto . |
DocumentJournal |
timeshift(Object id,
LocalDateTime time)
Turn back time to see how document journals looked like in the past.
|
Collection<Bitemporal> |
unload(Object... documentIDs)
Unloads the journal data of the given document IDs into a collection and
return that to the client.
|
T save(T newVersion, LocalDate from, LocalDate until)
BarbelHisto
. Creates snapshots of state. Clients can
safely continue to work on passed instances. Thread safe, applies lock to
journals of document IDs (not the complete backbone). This allows concurrent
work on different document IDs. If clients try to update the same document
Id, this method throws ConcurrentModificationException
.
The method returns a copy of the object saved including the version data. In
in BarbelMode.POJO
cast the returned object to Bitemporal
to
read the version data.newVersion
- the object state to savefrom
- effective date of object stateuntil
- effective until of the stateList<T> retrieve(com.googlecode.cqengine.query.Query<T> query)
BarbelHisto
using cqengine like queries. Clients
want to use BarbelQueries
for there convenience here.
BarbelQueries
can be combined with additional queries from
QueryFactory
.query
- the client query from BarbelQueries
and/or
QueryFactory
List<T> retrieve(com.googlecode.cqengine.query.Query<T> query, com.googlecode.cqengine.query.option.QueryOptions options)
BarbelHisto
using cqengine like queries. Clients
want to use BarbelQueries
and BarbelQueryOptions
for there
convenience here. BarbelQueries
can be combined with additional
queries from QueryFactory
.query
- the client query from BarbelQueries
and/or
QueryFactory
options
- the options from BarbelQueryOptions
or
QueryFactory
T retrieveOne(com.googlecode.cqengine.query.Query<T> query)
BarbelHisto
using cqengine like queries. Clients
want to use BarbelQueries
for there convenience here.
BarbelQueries
can be combined with additional queries from
QueryFactory
. Throws IllegalStateException
when
query returns more then one result, NoSuchElementException
if nothing
was found.query
- the client query from BarbelQueries
and/or
QueryFactory
T retrieveOne(com.googlecode.cqengine.query.Query<T> query, com.googlecode.cqengine.query.option.QueryOptions options)
BarbelHisto
using cqengine like queries. Clients
want to use BarbelQueries
and BarbelQueryOptions
for there
convenience here. BarbelQueries
can be combined with additional
queries from QueryFactory
. Throws IllegalStateException
when
query returns more then one result, NoSuchElementException
if nothing
was found.query
- the client query from BarbelQueries
and/or
QueryFactory
options
- the options from BarbelQueryOptions
or
QueryFactory
DocumentJournal timeshift(Object id, LocalDateTime time)
LocalDateTime.now()
the actual journal is returned. Time
shift does not change the backbone collection of the
BarbelHisto
instance, instead it returns an instance of
DocumentJournal
with copies of managed Bitemporal
objects.id
- the document Idtime
- the time, must be in the pastString prettyPrintJournal(Object id)
id
- the document IDvoid load(Collection<Bitemporal> bitemporals)
unload(Object...)
.BarbelMode.POJO
(default) clients have to pass a collection of
BitemporalVersion
. In BarbelMode.BITEMPORAL
mode clients can
add objects that implement Bitemporal
. bitemporals
- consistent list of Bitemporal
versionsCollection<Bitemporal> unload(Object... documentIDs)
load(Collection)
to re-load that
stored journals back into BarbelHisto
to continue bitemporal
processing.BarbelMode.POJO
(default) clients receive a collection of
BitemporalVersion
objects. In BarbelMode.BITEMPORAL
clients
receive objects that implement Bitemporal
. documentIDs
- the document IDs to unloadBitemporal
objects to store into an
arbitrary data storeboolean contains(Object documentId)
BarbelHisto
contains data for the given document ID.documentId
- the document id to checkBarbelHisto
contains data otherwise falseCopyright © 2019 Project Barbel. All rights reserved.


hxaudio.js is a drop-in javascript library that allows HTML5’s <audio>
tag to look the same in any browser.
Native AudioElement Google Chrome
Native AudioElement Firefox
Native AudioElement Safari
It uses native <audio>
. It provides a consistent html player UI to all browsers which can be styled used standard css.
Native AudioElement styled by HxAudio.js
I was inspired by the works of Anthony Kolber: audio.js.
But after a closer look it could use an update:
hxaudio.js
and hxaudio.gif
in the same folder./hxaudiojs
/hxadio.js
/hxaudio.gif
<script src="/hxaudiojs/hxaudio.js"></script>
<audio>
wherever you like in your HTML:<audio src="/mp3/juicy.mp3" preload="auto" />
A series of API tests & examples for using and extending audio.js
It has been verified to work across:
All efforts have been made to keep the source as clean and readable as possible. Until we release more detailed documentation, the annotated source is the best reference for usage.
Annotated source / Source on Github
hxaudio.js is released under an MIT License, so do with it what you will.
Use NPM watch for automate build
cd
to the correct folder
npm install
npm run watch
or just build it once with
haxe javascript.hxml
And open /bin/index.html
in your favorite browser.


DESCRIPTION
.Lightdrift is a Survival game
. Download the game now!
About Me:
I am an amateur in game development ,have a hobby and like game development.I am Khaled Nassef and I want to make a game that not only I the developer make but the community makes with me as well so hopefully you like my game and please leave your feedback as we will take every idea you leave into consideration
Links:


How to use the Feathers TabNavigator
component
The TabNavigator
class supports navigation between screens or pages using a TabBar
sub-component.
The Basics
First, let's create a TabNavigator
component and add it to the display list:
var navigator:TabNavigator = new TabNavigator();
this.addChild( navigator );
You may set its width
and height
, but that's optional because the TabNavigator
will automatically resize itself to fill the entire stage, if you don't provide explicit dimensions.
To add a new screen that the navigator can show, call addScreen()
and pass in an ID string to associate with the screen along with a TabNavigatorItem
:
var newsFeedItem:TabNavigatorItem = new TabNavigatorItem( NewsFeedTab, "News" );
navigator.addScreen( "newsFeed", newsFeedItem );
This screen's ID is "newsFeed"
. We can use use this ID later to programatically show the screen.
The first argument required by the TabNavigatorItem
constructor may be one of three types. We can pass in a Class
to instantiate, a display object that has already been instantiated, or a Function
that returns a display object. In most cases, a Class
is recommended. For more details, see the screen
property.
The second argument required by the TabNavigatorItem
is the label to display on the tab associated with the screen. In this case, we've set it to "News"
.
Finally, we can also pass in an icon to be displayed on the tab. However, this is optional, and we've skipped it in the example above.
Navigation
The active screen changes when the user selects a tab. When the first tab is added to a TabNavigator
, it is automatically selected.
To show a specific screen programatically, we can set the selectedIndex
:
navigator.selectedIndex = 1;
Alternatively, call showScreen()
, and pass in the screen's ID. For this example, we'll use the "newsFeed"
string that we registered with addScreen()
earlier:
navigator.showScreen( "newsFeed" );
The showScreen()
method supports an additional arugment that allows a custom animated transition between screens. We'll look at transitions in a moment.
To access the currently visible screen, use the activeScreen
property.
var screen:NewsFeedTab = NewsFeedTab( navigator.activeScreen );
You can also use activeScreenID
to get the ID of the active screen. In this case, again, it would be "newsFeed"
.
Animated Transitions
As we learned above, we can change to a new screen in a couple of different ways. The transition between two screens can also be animated, improving the user experience and adding a little bit of life to our games and apps. This animation during navigation is called a transition.
We can find a number of useful transition classes in the feathers.motion
package. One example is the Fade
class, which fades a screen by animating its alpha
property.
Each of the built-in transition classes has one or more static methods that you can call to create a transition function that tab navigator calls when navigating to a different screen. In this case, let's call Fade.createFadeInTransition()
.
We can pass the result to the tab navigator's transition
property:
navigator.transition = Fade.createFadeInTransition();
In the code above, we didn't pass any arguments to Fade.createFadeInTransition()
. However, this function exposes some optional parameters that we can customize, if desired. For instance, we might want to customize the duration of the animation (in seconds) and the easing function:
navigator.transition = Fade.createFadeInTransition( 0.75, Transitions.EASE_IN_OUT );
Now, the animation will last a little longer while easing in and out.
Events when transitions start and complete
A TabNavigator
dispatches FeathersEventType.TRANSITION_START
when a new screen is being shown and the transition animation begins. Similarly, it dispatches FeathersEventType.TRANSITION_COMPLETE
when the transition animation has ended.
Let's listen for FeathersEventType.TRANSITION_COMPLETE
:
navigator.addEventListener( FeathersEventType.TRANSITION_COMPLETE, navigator_transitionCompleteHandler );
The event listener might look like this:
private function navigator_transitionCompleteHandler( event:Event ):void
{
// do something after the transition animation
}
Property Injection
Optionally, we can pass properties to the screen before it is shown. If we have multiple screens that need to share some data, this is a useful way to ensure that each screen has access to it. For instance, we might have an OptionsData
class that stores things like audio volume and other common options. We'd want to pass that to the OptionsScreen
to let the user change the volume, obviously. We'd also want to pass it to other screens that play audio so that it plays at the correct volume.
When we create the TabNavigator
, let's create an OptionsData
instance too. In a moment, we'll pass it to each screen that needs it.
var optionsData:OptionsData = new OptionsData();
Now, when we add our OptionsScreen
to the TabNavigator
, we pass it the OptionsData
instance in using the properties
property on the TabNavigatorItem
:
var optionsItem:TabNavigatorItem = new TabNavigatorItem( OptionsScreen );
optionsItem.properties.options = optionsData;
In OptionsScreen
, we need to add a variable or a getter and setter named options
to match up with optionsItem.properties.options
:
protected var _options:OptionsData;
public function get options():OptionsData
{
return this._options;
}
public function set options( value:OptionsData ):void
{
this._options = value;
}
We want to update the screen when the options
property changes, so we should invalidate the screen, and the draw()
function will be called again:
public function set options( value:OptionsData ):void
{
if(this._options == value)
{
return;
}
this._options = value;
this.invalidate( INVALIDATION_FLAG_DATA );
}


|
||||||||||
| PREV NEXT | FRAMES NO FRAMES |
| Classes in uchicago.src.sim.engine used by anl.repast.gis.display | |
|---|---|
| SimModel
Interface for all RePast models. |
| Classes in uchicago.src.sim.engine used by uchicago.src.codegen | |
|---|---|
| BasicAction
Abstract base class for any action in a simulation that can be executed by a Schedule . |
| Classes in uchicago.src.sim.engine used by uchicago.src.repastdemos.asynchAgents | |
|---|---|
| AsynchAgent
An asynchronously executed agent class. |
|
| CustomProbeable
Interface required for those objects that want to customize which of their properties are probed. |
|
| IAsynchAgent
Interface used for asynchronous agents. |
|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
|
| SimpleModel
Encapsulates some simple model behavoir and hides the scheduling mechansim. |
| Classes in uchicago.src.sim.engine used by uchicago.src.repastdemos.enn | |
|---|---|
| Schedule
Manages the execution of BasicActions (ActionGroups, SimActions, and SimListActions) according to a simulation clock. |
|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
| Classes in uchicago.src.sim.engine used by uchicago.src.repastdemos.genetic | |
|---|---|
| AutoStepable
This interface can be used for a more advanced stepping pattern for agents. |
|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
|
| SimpleModel
Encapsulates some simple model behavoir and hides the scheduling mechansim. |
| Classes in uchicago.src.sim.engine used by uchicago.src.repastdemos.gisModel | |
|---|---|
| Schedule
Manages the execution of BasicActions (ActionGroups, SimActions, and SimListActions) according to a simulation clock. |
|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
| Classes in uchicago.src.sim.engine used by uchicago.src.repastdemos.heatBugs | |
|---|---|
| Schedule
Manages the execution of BasicActions (ActionGroups, SimActions, and SimListActions) according to a simulation clock. |
|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
| Classes in uchicago.src.sim.engine used by uchicago.src.repastdemos.hexabugs | |
|---|---|
| Schedule
Manages the execution of BasicActions (ActionGroups, SimActions, and SimListActions) according to a simulation clock. |
|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
| Classes in uchicago.src.sim.engine used by uchicago.src.repastdemos.hypercycles | |
|---|---|
| CustomProbeable
Interface required for those objects that want to customize which of their properties are probed. |
|
| Schedule
Manages the execution of BasicActions (ActionGroups, SimActions, and SimListActions) according to a simulation clock. |
|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
| Classes in uchicago.src.sim.engine used by uchicago.src.repastdemos.jain | |
|---|---|
| Schedule
Manages the execution of BasicActions (ActionGroups, SimActions, and SimListActions) according to a simulation clock. |
|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
| Classes in uchicago.src.sim.engine used by uchicago.src.repastdemos.jiggle | |
|---|---|
| Schedule
Manages the execution of BasicActions (ActionGroups, SimActions, and SimListActions) according to a simulation clock. |
|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
| Classes in uchicago.src.sim.engine used by uchicago.src.repastdemos.jinGirNew | |
|---|---|
| Schedule
Manages the execution of BasicActions (ActionGroups, SimActions, and SimListActions) according to a simulation clock. |
|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
| Classes in uchicago.src.sim.engine used by uchicago.src.repastdemos.life | |
|---|---|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
|
| SimpleModel
Encapsulates some simple model behavoir and hides the scheduling mechansim. |
| Classes in uchicago.src.sim.engine used by uchicago.src.repastdemos.mousetrap | |
|---|---|
| Schedule
Manages the execution of BasicActions (ActionGroups, SimActions, and SimListActions) according to a simulation clock. |
|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
| Classes in uchicago.src.sim.engine used by uchicago.src.repastdemos.neural | |
|---|---|
| AutoStepable
This interface can be used for a more advanced stepping pattern for agents. |
|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
|
| SimpleModel
Encapsulates some simple model behavoir and hides the scheduling mechansim. |
| Classes in uchicago.src.sim.engine used by uchicago.src.repastdemos.neuralfromfile | |
|---|---|
| AutoStepable
This interface can be used for a more advanced stepping pattern for agents. |
|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
|
| SimpleModel
Encapsulates some simple model behavoir and hides the scheduling mechansim. |
| Classes in uchicago.src.sim.engine used by uchicago.src.repastdemos.openmap | |
|---|---|
| Schedule
Manages the execution of BasicActions (ActionGroups, SimActions, and SimListActions) according to a simulation clock. |
|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
| Classes in uchicago.src.sim.engine used by uchicago.src.repastdemos.rabbitPopulation | |
|---|---|
| CustomProbeable
Interface required for those objects that want to customize which of their properties are probed. |
|
| Schedule
Manages the execution of BasicActions (ActionGroups, SimActions, and SimListActions) according to a simulation clock. |
|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
| Classes in uchicago.src.sim.engine used by uchicago.src.repastdemos.regression | |
|---|---|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
|
| SimpleModel
Encapsulates some simple model behavoir and hides the scheduling mechansim. |
| Classes in uchicago.src.sim.engine used by uchicago.src.repastdemos.sugarscape | |
|---|---|
| Schedule
Manages the execution of BasicActions (ActionGroups, SimActions, and SimListActions) according to a simulation clock. |
|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
| Classes in uchicago.src.sim.engine used by uchicago.src.sim.analysis | |
|---|---|
| IController
Defines methods for controlling the execution of a SimModel. |
|
| SimEvent
A semantic event that indicates that the simulation run has paused or stopped. |
|
| SimEventListener
The listener interface for those objects that want to listen for SimEvents. |
|
| SimModel
Interface for all RePast models. |
| Classes in uchicago.src.sim.engine used by uchicago.src.sim.analysis.plot | |
|---|---|
| SimModel
Interface for all RePast models. |
| Classes in uchicago.src.sim.engine used by uchicago.src.sim.engine | |
|---|---|
| AbstractGUIController
Base class for GUI controllers. |
|
| ActionQueue
Priority Queue for Action objects. |
|
| BaseController
Abstract base class implementing IController. |
|
| BasicAction
Abstract base class for any action in a simulation that can be executed by a Schedule . |
|
| BatchController
A controller for running a simulation over multiple runs. |
|
| BatchEvent
Events used in the BatchEventListener events. |
|
| BatchEvent.BatchEventType
|
|
| BatchListener
The listener used for batch events. |
|
| Group
|
|
| HomeController
Created by IntelliJ IDEA. |
|
| IAsynchAgent
Interface used for asynchronous agents. |
|
| IController
Defines methods for controlling the execution of a SimModel. |
|
| Incrementer
|
|
| MediaScheduler
|
|
| ModelManipulator
Creates sliders and buttons for the manipulation of models. |
|
| ParameterFileListener
Listener for the RepastParameterPanel events |
|
| PropertyEvent
An event fired by changes to a model's properties/parameters. |
|
| PropertyListener
An interface for those classes that wish to listen for PropertyEvents, such as the value of a model's property being changed. |
|
| RandomScheduleGroup
|
|
| RemoteBatchController
The Controller that handles a single remote model. |
|
| Schedule
Manages the execution of BasicActions (ActionGroups, SimActions, and SimListActions) according to a simulation clock. |
|
| ScheduleBase
Abstract base class for Schedule and SubSchedule. |
|
| ScheduleBase.Order
|
|
| ScheduleGroup
A specialized BasicAction containing other BasicActions. |
|
| SimEvent
A semantic event that indicates that the simulation run has paused or stopped. |
|
| SimEventListener
The listener interface for those objects that want to listen for SimEvents. |
|
| SimEventProducer
Interface for those classes that wish to produce SimEvents. |
|
| SimModel
Interface for all RePast models. |
|
| SimModelImpl
A partial implementation of the SimModel interface. |
|
| TickCounter
Interface for classes that can return current time. |
| Classes in uchicago.src.sim.engine used by uchicago.src.sim.engine.gui | |
|---|---|
| ParameterFileListener
Listener for the RepastParameterPanel events |
|
| Schedule
Manages the execution of BasicActions (ActionGroups, SimActions, and SimListActions) according to a simulation clock. |
|
| SimModel
Interface for all RePast models. |
|
| SnapshotScheduler
|
| Classes in uchicago.src.sim.engine used by uchicago.src.sim.engine.gui.components | |
|---|---|
| SimModel
Interface for all RePast models. |
| Classes in uchicago.src.sim.engine used by uchicago.src.sim.gui | |
|---|---|
| CustomProbeable
Interface required for those objects that want to customize which of their properties are probed. |
|
| SimEvent
A semantic event that indicates that the simulation run has paused or stopped. |
|
| SimEventListener
The listener interface for those objects that want to listen for SimEvents. |
|
| SimModel
Interface for all RePast models. |
| Classes in uchicago.src.sim.engine used by uchicago.src.sim.math | |
|---|---|
| Schedule
Manages the execution of BasicActions (ActionGroups, SimActions, and SimListActions) according to a simulation clock. |
|
| TickCounter
Interface for classes that can return current time. |
| Classes in uchicago.src.sim.engine used by uchicago.src.sim.network | |
|---|---|
| SimModel
Interface for all RePast models. |
| Classes in uchicago.src.sim.engine used by uchicago.src.sim.parameter | |
|---|---|
| Incrementer
|
|
| SimModel
Interface for all RePast models. |
| Classes in uchicago.src.sim.engine used by uchicago.src.sim.parameter.rpl | |
|---|---|
| SimModel
Interface for all RePast models. |
| Classes in uchicago.src.sim.engine used by uchicago.src.sim.util | |
|---|---|
| BasicAction
Abstract base class for any action in a simulation that can be executed by a Schedule . |
|
| ObjectPicker
|
|
| StatCalculator
|
|
||||||||||
| PREV NEXT | FRAMES NO FRAMES |


Database Sample
| Speech | Singing |
Reference
Please cite the following paper if you use this database:
"Bidisha Sharma, Xiaoxue Gao, Karthika Vijayan, Xiaohai Tian, and Haizhou Li. "NHSS: A Speech and Singing Parallel Database." arXiv preprint arXiv:2012.00337 (2020)."
Download the Database
The NHSS database is provided strictly for research purposes only. To acquire the database, fill up the following licence and email to Dr Bidisha Sharma<EMAIL_ADDRESS>and Prof Haizhou Li (haizhou.li@nus.edu.sg)


| firebase://mavo-demos | { project: "mavo-demos", collection: "mavo-apps", filename: "countries" } |
| firebase://d12n/mv-app/people | { project: "d12n", filename: "people", collection: "mv-app" } |
| firebase://mavo-demos/mv-app/collection/subcollection/people | { project: "mavo-demos", filename: "people", collection: "mv-app/collection/subcollection" } |
| https://mavo-demos.firebaseio.com | { project: "mavo-demos", collection: "mavo-apps", filename: "countries" } |
| https://d12n.firebaseio.com/mv-app/people | { project: "d12n", filename: "people", collection: "mv-app" } |
| https://mavo-demos.firebaseio.com/mv-app/collection/subcollection/people | { project: "mavo-demos", filename: "people", collection: "mv-app/collection/subcollection" } |
| firebase://d12n/mv-app | { project: "d12n", filename: "countries", collection: "mv-app" } |
| firebase://d12n/mv-app/collection/subcollection | { project: "d12n", filename: "countries", collection: "mv-app/collection/subcollection" } |
| mv-firebase value | Actual features | Expected features |
|---|---|
| { auth: false, storage: false, realtime: false, "all-can-write": false, "all-can-edit": false } | |
| auth realtime storage all-can-write | { auth: true, storage: true, realtime: true, "all-can-write": true, "all-can-edit": false } |
| auth auth auth storage storage | { auth: true, storage: true, realtime: false, "all-can-write": false, "all-can-edit": false } |
| realtime foo storage | { auth: false, storage: true, realtime: true, "all-can-write": false, "all-can-edit": false } |
| mv-firebase-auth value | Actual | Expected |
|---|---|
| [] | |
| facebook google | [ "facebook", "google" ] |
| Twitter GitHub | [ "twitter", "github" ] |
| google facebook google twitter twitter github | [ "google", "facebook", "twitter", "github" ] |
| twitter foo bar github | [ "twitter", "github" ] |
|
|
Check me
|
|
Check me
|
|
Check me
|
|
Should see the Edit and Save buttons on the Mavo bar.
Try to upload an image below. Try pasting an image, or drag & drop too.
Click here first for this test to pass.
|
|
|
|
Should display data but no editing controls
|
|


Welcome to my infographic exercise!
It uses utility classes for typography and spacing to space content out within the larger container.
Learn moreA bar chart showing hot weather deaths in Baltimore and Maryland by year.
A map showing predicted major heat events by the year 2040.
N/A


Home
FFF Specials
Order History
Order History
Order
Date
Jikoni fries
1/8/2018
Burger
28/8/2018
French fries
30/8/2018


Banka
Home
Admin
Create Account
Sign-Up
Sign-In
Contact Us
Account type
Current Account
Savings Account
Child Savings Account
Corporate Account
Education Support (Fixed)
Upload Your Documents
Your Official Identity Card
Your Referee's Authorization Letter
Create Account


analytics
Source: analyticsdoc.
Analytics module.
Example
// import modules
var qm = require('qminer');
var analytics = qm.analytics;
// load dataset, create model, evaluate model
Child classes
Namespaces
Method
Abstract types
Classes
BiasedGk
BufferedTDigest
DpMeans
Gk
KMeans
LogReg
MDS
NearestNeighborAD
NNet
OneVsAll
PCA
PropHazards
RecLinReg
RecommenderSys
RidgeReg
Sigmoid
SVC
SVR
TDigest
ThresholdModel
Tokenizer
ActiveLearner
Namespaces
metrics
preprocessing
Method
nmf(mat, k[, json]) → Object
Calculates the non-negative matrix factorization, see: https://en.wikipedia.org/wiki/Non-negative_matrix_factorization.
Examples
Asynchronous function
// import modules
var analytics = require('qminer').analytics;
var la = require('qminer').la;
// create a matrix
var mat = new la.Matrix({ rows: 10, cols: 5, random: true });
// compute the non-negative matrix factorization
analytics.nmfAsync(mat, 3, { iter: 100, tol: 1e-4 }, function (err, result) {
if (err) { console.log(err); }
// calculation successful
var U = result.U;
var V = result.V;
});
Synchronous function
// import modules
var analytics = require('qminer').analytics;
var la = require('qminer').la;
// create a matrix
var mat = new la.Matrix({ rows: 10, cols: 5, random: true });
// compute the non-negative matrix factorization
var result = analytics.nmf(mat, 3, { iter: 100, tol: 1e-4 });
var U = result.U;
var V = result.V;
Parameters
| Name | Type | Optional | Description | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
mat |
|
The non-negative matrix. |
|||||||||||||||||
|
k |
number |
|
The reduced rank, e.g. number of columns in matrix U and number of rows in matrix V. Must be between 0 and |
||||||||||||||||
|
json |
Object |
Yes |
Algorithm options. Values in
|
- Returns
-
Object
B The json objectnmfRes
containing the non-negative matrices U and V:
nmfRes.U
- The module:la.Matrix representation of the matrix U,
nmfRes.V
- The module:la.Matrix representation of the matrix V.
Abstract types
ActiveLearnerParam Object
An object used for the construction of module:analytics.ActiveLearner.
Properties
| Name | Type | Optional | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
learner |
Object |
Yes |
Learner parameters Values in
|
||||||||
|
SVC |
Yes |
Support vector classifier parameters. |
BiasedGkParam Object
An object used for the construction of module:analytics.quantiles.BiasedGk.
Properties
| Name | Type | Optional | Description |
|---|---|---|---|
|
targetProb |
number |
Yes |
The probability where the algorithm is most accurate. Its accuracy is determined as epsmax(p, targetProb) when targetProb < 0.5 and epsmax(1-p, 1-targetProb) when targetProb >= 0.5. Higher values of Defaults to |
|
eps |
number |
Yes |
Parameter which determines the accuracy. Defaults to |
|
compression |
string |
Yes |
Determines when the algorithm compresses its summary. Options are: "periodic", "aggressive" and "manual". Defaults to |
|
useBands |
boolean |
Yes |
Whether the algorithm should use the 'band' subprocedure. Using this subprocedure should result in a smaller summary. Defaults to |
BufferedDigestParam Object
An object used for the construction of module:analytics.quantiles.BufferedTDigest.
Properties
| Name | Type | Optional | Description |
|---|---|---|---|
|
delta |
number |
Yes |
The number of clusters in the summary is bounded by floor(minClusters) <= clusters < 2*ceil(minClusters) Defaults to |
|
bufferLen |
number |
Yes |
the size of the buffer is minClustersbufferLenFactor, when the buffer fills it is merged with the summary. Also, the algorithm initializes after seeing minClustersbufferLenFactor examples. Defaults to |
|
seed |
number |
Yes |
random seed (values above 1 are deterministic) Defaults to |
detectorParam Object
An object used for the construction of module:analytics.NearestNeighborAD.
Parameters
| Name | Type | Optional | Description |
|---|---|---|---|
|
rate |
number |
Yes |
The expected fracton of emmited anomalies (0.05 -> 5% of cases will be classified as anomalies). Defaults to |
|
windowSize |
number |
Yes |
Number of most recent instances kept in the model. Defaults to |
DpMeansExplain Object
The examplanation returned by module:analytics.KMeans#explain.
Properties
| Name | Type | Optional | Description |
|---|---|---|---|
|
medoidID |
number |
|
The ID of the nearest medoids. |
|
featureIDs |
|
The IDs of features, sorted by contribution. |
|
|
featureContributions |
|
Weights of each feature contribution (sum to 1.0). |
DpMeansParam Object
An object used for the construction of module:analytics.KMeans.
Properties
| Name | Type | Optional | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
iter |
number |
Yes |
The maximum number of iterations. Defaults to |
||||||||
|
lambda |
number |
Yes |
Maximum radius of the clusters Defaults to |
||||||||
|
minClusters |
number |
Yes |
Minimum number of clusters Defaults to |
||||||||
|
maxClusters |
number |
Yes |
Maximum number of clusters Defaults to |
||||||||
|
allowEmpty |
boolean |
Yes |
Whether to allow empty clusters to be generated. Defaults to |
||||||||
|
calcDistQual |
boolean |
Yes |
Whether to calculate the quality measure based on distance, if false relMeanCentroidDist will return 'undefined' Defaults to |
||||||||
|
centroidType |
string |
Yes |
The type of centroids. Possible options are Defaults to |
||||||||
|
distanceType |
string |
Yes |
The distance type used at the calculations. Possible options are Defaults to |
||||||||
|
verbose |
boolean |
Yes |
If Defaults to |
||||||||
|
fitIdx |
Array of number |
Yes |
The index array used for the construction of the initial centroids. |
||||||||
|
fitStart |
Object |
Yes |
The KMeans model returned by module:analytics.KMeans.prototype.getModel used for centroid initialization. Values in
|
GkParam Object
An object used for the construction of module:analytics.quantiles.Gk.
Properties
| Name | Type | Optional | Description |
|---|---|---|---|
|
eps |
number |
Yes |
Determines the relative error of the algorithm. Defaults to |
|
autoCompress |
boolean |
Yes |
Whether the summary should be compresses automatically or manually. Defaults to |
|
useBands |
boolean |
Yes |
Whether the algorithm should use the 'band' subprocedure. Using this subprocedure should result in a smaller summary. Defaults to |
hazardModelParam Object
An object used for the construction of module:analytics.PropHazards.
Property
| Name | Type | Optional | Description |
|---|---|---|---|
|
lambda |
number |
Yes |
The regularization parameter. Defaults to |
KMeansExplain Object
The examplanation returned by module:analytics.KMeans#explain.
Properties
| Name | Type | Optional | Description |
|---|---|---|---|
|
medoidID |
number |
|
The ID of the nearest medoids. |
|
featureIDs |
|
The IDs of features, sorted by contribution. |
|
|
featureContributions |
|
Weights of each feature contribution (sum to 1.0). |
KMeansParam Object
An object used for the construction of module:analytics.KMeans.
Properties
| Name | Type | Optional | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
iter |
number |
Yes |
The maximum number of iterations. Defaults to |
||||||||
|
k |
number |
Yes |
The number of centroids. Defaults to |
||||||||
|
allowEmpty |
boolean |
Yes |
Whether to allow empty clusters to be generated. Defaults to |
||||||||
|
calcDistQual |
boolean |
Yes |
Whether to calculate the quality measure based on distance, if false relMeanCentroidDist will return 'undefined' Defaults to |
||||||||
|
centroidType |
string |
Yes |
The type of centroids. Possible options are Defaults to |
||||||||
|
distanceType |
string |
Yes |
The distance type used at the calculations. Possible options are Defaults to |
||||||||
|
verbose |
boolean |
Yes |
If Defaults to |
||||||||
|
fitIdx |
Array of number |
Yes |
The index array used for the construction of the initial centroids. |
||||||||
|
fitStart |
Object |
Yes |
The KMeans model returned by module:analytics.KMeans.prototype.getModel used for centroid initialization. Values in
|
logisticRegParam Object
An object used for the construction of module:analytics.LogReg.
Properties
| Name | Type | Optional | Description |
|---|---|---|---|
|
lambda |
number |
Yes |
The regularization parameter. Defaults to |
|
intercept |
boolean |
Yes |
Indicates whether to automatically include the intercept. Defaults to |
MDSParam Object
An object used for the construction of module:analytics.MDS.
Properties
| Name | Type | Optional | Description |
|---|---|---|---|
|
maxSecs |
number |
Yes |
The maximum time period to compute Multidimensional Scaling of a matrix. Defaults to |
|
maxStep |
number |
Yes |
The maximum number of iterations. Defaults to |
|
minDiff |
number |
Yes |
The minimum difference criteria in MDS. Defaults to |
|
distType |
string |
Yes |
The type of distance used. Available types: "Euclid", "Cos", "SqrtCos". Defaults to |
NearestNeighborADExplain Object
An object used for interpreting the predictions of module:analytics.NearestNeighborAD#explain.
Properties
| Name | Type | Optional | Description |
|---|---|---|---|
|
nearestID |
number |
|
The ID of the nearest neighbor. |
|
distance |
number |
|
The distance to the nearest neighbor. |
|
features |
Array of module:analytics~NearestNeighborADFeatureContribution |
|
An array with feature contributions. |
|
oldestID |
number |
|
The ID of the oldest record in the internal buffer (the record that was added first). |
|
newestID |
number |
|
The ID of the newest record in the internal buffer (the record that was added last). |
NearestNeighborADFeatureContribution Object
An object explaining the prediction of module:analytics.NearestNeighborAD#explain in terms of a single feature. Contained in the object module:analytics~NearestNeighborADExplain.
Properties
| Name | Type | Optional | Description |
|---|---|---|---|
|
id |
number |
|
The ID of the feature. |
|
val |
number |
|
The value of the feature for the vector we are explaining. |
|
nearVal |
number |
|
The the value of the feature for the nearest neighbor. |
|
contribution |
number |
|
Fraction of the total distance |
nnetParam Object
An object used for the construction of module:analytics.NNet.
Properties
| Name | Type | Optional | Description |
|---|---|---|---|
|
layout |
Array of number |
Yes |
The array representing the network schema. Defaults to |
|
learnRate |
number |
Yes |
The learning rate. Defaults to |
|
momentum |
number |
Yes |
The momentum of optimization. Defaults to |
|
tFuncHidden |
string |
Yes |
Type of activation function used on hidden nevrons. Possible options are Defaults to |
|
tFuncOut |
string |
Yes |
Type of activation function used on output nevrons. Possible options are Defaults to |
oneVsAllParam Object
An object used for the construction of module:analytics.OneVsAll.
Properties
| Name | Type | Optional | Description |
|---|---|---|---|
|
model |
function() |
Yes |
Constructor for binary model to be used internaly. Constructor should expect only one parameter. |
|
modelParam |
Object |
Yes |
Parameter for |
|
categories |
number |
Yes |
Number of categories. |
|
verbose |
boolean |
Yes |
If false, the console output is supressed. Defaults to |
PCAParam Object
An object used for the construction of module:analytics.PCA.
Properties
| Name | Type | Optional | Description |
|---|---|---|---|
|
k |
number |
Yes |
Number of eigenvectors to be computed. Defaults to |
|
iter |
number |
Yes |
Number of iterations. Defaults to |
recLinRegParam Object
An object used for the construction of module:analytics.RecLinReg.
Parameters
| Name | Type | Optional | Description |
|---|---|---|---|
|
dim |
number |
|
The dimension of the model. |
|
regFact |
number |
Yes |
The regularization factor. Defaults to |
|
forgetFact |
number |
Yes |
The forgetting factor. Defaults to |
RecSysParam Object
An object used for the construction of module:analytics.RecommenderSys.
Properties
| Name | Type | Optional | Description |
|---|---|---|---|
|
iter |
number |
Yes |
The maximum number of iterations. Defaults to |
|
k |
number |
Yes |
The number of centroids. Defaults to |
|
tol |
number |
Yes |
The tolerance. Defaults to |
|
verbose |
boolean |
Yes |
If false, the console output is supressed. Defaults to |
ridgeRegParam Object
An object used for the construction of module:analytics.RidgeReg.
Property
| Name | Type | Optional | Description |
|---|---|---|---|
|
gamma |
number |
Yes |
The gamma value. Defaults to |
SVMParam Object
SVM constructor parameters. Used for the construction of module:analytics.SVC and module:analytics.SVR.
Properties
| Name | Type | Optional | Description |
|---|---|---|---|
|
algorithm |
string |
Yes |
The algorithm procedure. Possible options are Defaults to |
|
c |
number |
Yes |
Cost parameter. Increasing the parameter forces the model to fit the training data more accurately (setting it too large may lead to overfitting) . Defaults to |
|
j |
number |
Yes |
Unbalance parameter. Increasing it gives more weight to the positive examples (getting a better fit on the positive training examples gets a higher priority). Setting j=n is like adding n-1 copies of the positive training examples to the data set. Defaults to |
|
eps |
number |
Yes |
Epsilon insensitive loss parameter. Larger values result in fewer support vectors (smaller model complexity) Defaults to |
|
batchSize |
number |
Yes |
Number of examples used in the subgradient estimation. Higher number of samples slows down the algorithm, but makes the local steps more accurate. Defaults to |
|
maxIterations |
number |
Yes |
Maximum number of iterations. Defaults to |
|
maxTime |
number |
Yes |
Maximum runtime in seconds. Defaults to |
|
minDiff |
number |
Yes |
Stopping criterion tolerance. Defaults to |
|
type |
string |
Yes |
The subalgorithm procedure in LIBSVM. Possible options are Defaults to |
|
kernel |
string |
Yes |
Kernel type in LIBSVM. Possible options are Defaults to |
|
gamma |
number |
Yes |
Gamma parameter in LIBSVM. Set gamma in kernel function. Defaults to |
|
p |
number |
Yes |
P parameter in LIBSVM. Set the epsilon in loss function of epsilon-SVR. Defaults to |
|
degree |
number |
Yes |
Degree parameter in LIBSVM. Set degree in kernel function. Defaults to |
|
nu |
number |
Yes |
Nu parameter in LIBSVM. Set the parameter nu of nu-SVC, one-class SVM, and nu-SVR. Defaults to |
|
coef0 |
number |
Yes |
Coef0 parameter in LIBSVM. Set coef0 in kernel function. Defaults to |
|
cacheSize |
number |
Yes |
Set cache memory size in MB (default 100) in LIBSVM. Defaults to |
|
verbose |
boolean |
Yes |
Toggle verbose output in the console. Defaults to |
TDigestParam Object
An object used for the construction of module:analytics.quantiles.TDigest.
Properties
| Name | Type | Optional | Description |
|---|---|---|---|
|
minCount |
number |
Yes |
The minimal number of examples before the model is initialized. Defaults to |
|
clusters |
number |
Yes |
The number of 1-d clusters (large values lead to higher memory usage). Defaults to |
tokenizerParam Object
An object used for the construction of module:analytics.Tokenizer.
Property
| Name | Type | Optional | Description |
|---|---|---|---|
|
type |
string |
Yes |
The type of the tokenizer. The different types are:
Defaults to |


Welcome to
PhoneGap-GoogleMaps-Plugin
version 1.2.5
This demo application is created using
Apache Cordova
and
PhoneGap-GoogleMaps-Plugin
.
Let's start demo!


Class: CocoapodsRepoSq::Repository
- Inherits:
-
Object
- Object
- CocoapodsRepoSq::Repository
- Defined in:
- lib/cocoapods_repo_sq/repository.rb
Overview
Class that represents the credentials needed to access a Square SDK repository of podspecs for a given Square Application. Responsible for downloading a copy of the repository from Square servers and cache it on the local filesystem.
Class Attribute Summary collapse
-
.current ⇒ CocoapodsRepoSq::Repository
Square SDK repository set by the plugin initialization on the Podfile.
Instance Attribute Summary collapse
-
#name ⇒ String
readonly
Nickname under which a Square SDK repository was registered on the RepositoryStore.
-
#password ⇒ String
readonly
Server password used to access a specific Square SDK repository.
-
#path ⇒ String
readonly
Local filesystem path where this repository cache of podspecs is stored.
-
#url ⇒ String
readonly
Square SDK repositories server url.
-
#username ⇒ String
readonly
Server user name used to access a specific Square SDK repository.
Instance Method Summary collapse
-
#initialize(name, username, password, url, path) ⇒ Repository
constructor
A new instance of Repository.
-
#update_specs ⇒ Object
Updates the local copy of the podspecs from the Square SDK repository.
Constructor Details
#initialize(name, username, password, url, path) ⇒ Repository
Returns a new instance of Repository
79 80 81 82 83 84 85 |
# File 'lib/cocoapods_repo_sq/repository.rb', line 79 def initialize(name, username, password, url, path) @name = name @username = username @url = url @password = password @path = path end |
Class Attribute Details
.current ⇒ CocoapodsRepoSq::Repository
Square SDK repository set by the plugin initialization on the
Podfile. This
setting is used by the Downloader class to know which repository to
download files from in the context of a pod install
or
pod update
command call. When a podspec indicates a Square
source it does not have a Square SDK repository reference to provide to the
Downloader class so this global setting is used instead.
40 41 42 |
# File 'lib/cocoapods_repo_sq/repository.rb', line 40 def current @current end |
Instance Attribute Details
#name ⇒ String (readonly)
Returns nickname under which a Square SDK repository was registered on the CocoapodsRepoSq::RepositoryStore.
46 47 48 |
# File 'lib/cocoapods_repo_sq/repository.rb', line 46 def name @name end |
#password ⇒ String (readonly)
Returns server password used to access a specific Square SDK repository.
54 55 56 |
# File 'lib/cocoapods_repo_sq/repository.rb', line 54 def password @password end |
#path ⇒ String (readonly)
Returns local filesystem path where this repository cache of podspecs is stored.
62 63 64 |
# File 'lib/cocoapods_repo_sq/repository.rb', line 62 def path @path end |
#url ⇒ String (readonly)
Returns Square SDK repositories server url.
58 59 60 |
# File 'lib/cocoapods_repo_sq/repository.rb', line 58 def url @url end |
#username ⇒ String (readonly)
Returns server user name used to access a specific Square SDK repository.
50 51 52 |
# File 'lib/cocoapods_repo_sq/repository.rb', line 50 def username @username end |
Instance Method Details
#update_specs ⇒ Object
Updates the local copy of the podspecs from the Square SDK repository
88 89 90 91 92 93 94 95 96 97 98 99 100 101 |
# File 'lib/cocoapods_repo_sq/repository.rb', line 88 def update_specs # download new specs to a temp directory new_specs_path = get_temporary_path downloader = Downloader.new(new_specs_path, "specs.zip", :repository => self) downloader.download # perform cleanup specs_path = File.join(@path, 'Specs') new_specs_file = File.join(new_specs_path, "file.zip") FileUtils.rm(new_specs_file) if File.exists?(new_specs_file) FileUtils.rm_rf(specs_path) if Dir.exists?(specs_path) FileUtils.mv(new_specs_path, specs_path) nil end |


Well, as you know, we had to get some
things fixed on the boat. The big blow did some damage,
and we had a list of things that we wanted to do once we got
back to the states - but first we had some folks to visit.
We stopped at Rowayton, CT and saw a great fireworks show, and
connected with our friends the Stolbas. Derek was very
happy to see his old buddies Chaz and Dylan, and ended up going
home with the Stolbas for the next week.
Kris and Dean then took the boat to Captains Cove Marina
in Bridgeport, CT, which is where we had the boat before we
left.
We caught up with lots of folks, who were nice enough to buy us
dinner or lunch or have us to their homes for dinner. It
was really nice to see everyone, and a special thanks to John
for letting us mail a bunch of stuff to his house, and for him
bringing to the boat.
While in Bridgeport, we spoke with our insurance, and had a
person come out and fix our electronics, so that is done - kind
of - the bow depth instrument stopped working the day after he
got it working. Kris will putz with it for a while and see
what she can do.
We moved down to Stamford, CT for the rest of the repairs to be
close to Hathaway's Sails and rigging. They have done a
terrific job helping us out, getting obscure parts, and free
advice on how to fix the stuff.
Also highly recommended is KAF Manufacturing. - a machine shop
in Stamford that fixed the take off pulley for the engine while I
waited and gave me a good deal on the price. Great bunch
of guys.
For you sailors, our list of projects is as follows: repair boom
vang, repair boom gooseneck fitting, install new sheave box for
jib, get new jib halyard, repair jib stitching and get new
batten (lost at sea), order new camber spar for jib, fix bow
depth sounder, fix radar, find machine shop to make new engine
take off pulley, fix dinghy cover, new zipper in mainsail, resew
jib cover zipper, install antifreeze overflows in engines, fix
oil leak in starboard engine, replace broken shower pump,
install new A/C pump, and the list goes on, but those are the
big ones.
We have lots of things to order for spares, now that we know a
bit more about what we need, and in another week we should have
the boat mostly ship shape for the next year or so. We
have been working steady the whole week, and are feeling rather
put out about it, as we are used to a much more relaxed pace,
but it will be nice to have it all done.
Kris is excited about one purchase, we got a small washing
machine for the boat. It will only do a few things at a
time, but will save on that big marathon laundry day at the
laundromat once a month, and save some money in the long run.
Now we just need to find a plumbing store to get the fittings to
hook it up.
One thing about cruising, is having a friend allow you to ship
stuff to their house is a great treat. We were able to pre
order stuff and have it waiting for us in CT. All projects
take longer because there is no car, and you have to find a
place to leave the dinghy, then walk to your destination and
back, which leave less time on the boat for working. Both
Hathaways and KAF offered us rides, which was really great.
All our friends up here in CT have offered us rides, or let us
ship stuff to their houses, and delivered it - can't say how
much we appreciate that.
Update 7/11/12;
Visits, repairs, maintenance and shopping
| |
|
|
|
|
|
|
|
Derek with his friends Chaz and Dylan |
Just
the small boat Queen Elizabeth 2 - we passed
by her coming through the East River in New
York City |
|
We aren't in the Bahamas any more |
Repairing the boom gooseneck |
|
Finally - the alternator pulley
problem fixed |
The old broken and new jib sheave box |
|
The new washing machine |
|
|


Welcome to Messenger
An awesome replacement to your default SMS app!
Slide through to get introduced, or click skip to get started straight away!
Permissions
When you click next we will prompt you for some permissions, without these we unfortunately cannot operate this app :(
Ready?
It seems we are all setup and ready to go!
When you click next we will start to process all of your text messages and start categorizing them, this make take a while!


BREEDSTATS.draw( breed, graphtypes ); BREEDSTATS.draw( breed, graphtypes, from-year, to-year, generations );
| breed | Name of the breed. E.g. 'Rottweiler'. |
|---|---|
| graphtypes | The types of graphs you want to display. Possible values are
|
| from-year, to-year | Start and end years to be charted in the graph. Default: 2004 and 2014. |
| generations | Number of generations to use for calculations of inbreeding. Default: 6. |
<script> BREEDSTATS.draw( 'Rottweiler', 'Innavl', 2010, 2013, 5 ); </script>
<script> BREEDSTATS.setBaseUrl( 'yourdomain.com/dogpopulation/graph/' ); </script>
Baseurl must be set before drawing the graphs.


{% for event in events %}
{% if event.type == 'hackathon' %}
{% assign 'Hackathon' as title %}
{% assign 'Join developers, students, enterpreneurs and data experts at a Vulekamali hackathon. Build websites, mobile apps and other tools using the data and APIs behind vulekamali.' as description %}
{% elif event.type == 'cid' %}
{% assign 'Civic Information Drive' as title %}
{% assign 'Find out more about how to use vulekamali.gov.za to understand national and provincial budgets.' as description %}
{% elif event.type == 'dataquest' %}
{% assign 'Data Quest' as title %}
{% assign 'Tell us what you need to make Vulekamali and budget data more accessible and useful. Join us for a full day event discussing budget accessibility.' as description%}
{% elif event.type == 'gift-dataquest' %}
{% assign 'Better Budget Data Quest' as title %}
{% assign 'Find new insights on budget topics and innovative ideas to analyse and improve budget allocations and execution.' as description %}
{% else %}
{% assign 'Event' as title %}
{% assign '' as description %}
{% endif %}


Toggle navigation
Back
Focus Control
Click Me
Sign up for free!
Sign up today!
Cancel
This Modal Needs To:
Focus inside the modal on load
Close the modal when escape key is pressed
Not allow tab to focus anything outside of the modal


Firstly, what are your class needs? How much time are your students going to want to present? A half hour? An hour? The whole two hours? Do you want to give your students a sign up sheet in order to choose a time block, or assign the students blocks yourself? These are the next few details to be finalized in order to create a schedule, as it varies class by class.
The next piece of information could go two ways. What is needed is a general title describing what (a) either the class is presenting or (b) what individual students/groups are presenting. This will allow for a general map of topics to be created.
Can be what you present at CCI Day
Click Reference
"examples" are your friends.
Click HTML (may need to refresh page after enabling)
Your first two lines of a sass file should be:
@charset "UTF-8";
@import "compass";
@include link-colors($normal, $hover, $active, $visited, $focus);
@include box-sizing(border-box);
@include font-face("Name", font-files("name.ttf", "name.woff"));
Buuuuuut....
For "Bullet-Proof" we use Nicole Sullivan's technique
You can also use Zurb's Icon fonts
Create a button with a Star icon to the left of it
<button> Star</button>
@include opacity(50);
Only need this for providing Old IE opacity, if not just use "opacity: .5;"
Opacity affects HEX colors and whatever they contain
rgba(255, 255, 255, 0.5);
Give a div #bada55 background color with 70% opacity
background: rgba(186, 218, 85, 0.7);???
background: rgba(#bada55, 0.7);
https://github.com/esteinborn/compass-sprites
http://bit.ly/inf-sprite-icons - Download this icon pack
Download this, open in Prepros
Place icons into /images/my-icons/*.png
FastClick.attach(document.body);
if (Element.prototype.addEventListener) {
window.addEventListener('load', function() {
FastClick.attach(document.body);
}, false);
}
Filter a table of data by its text content
Using a drop down
Using a type input
Make a modal slide down from the top of the page
Send variable back to the main page
Affix a sidebar to the top of the page after it's been scrolled past
With JS
With CSS
├── _config.yml
This stores all the configuration for Jekyll.
GH Pages is limited to a certain set of attributes in the file
Default
name: Site Name
markdown: redcarpet
pygments: false
# change baseurl to:
# '': for root level domains ie: mycustomdomain.com
# '/projectname': for subdomains ie: user.github.io/projectname
baseurl: '/projectname'
permalink: :title.html
Layouts Folder
├── _layouts
├── default.html
└── post.html
Base Setup _layouts folder -> default.html
<!doctype html>

{{ content }}

It's where the magic happens
└── index.html
---
layout: default
title: Page Title
---

Page Content

<!doctype html>

Page Content

_layouts/secondary.html
---
layout: default
title: Page Title
---

{{ content }}

You want to link your header image to your site root
My Site Root
nope...
You'll need to use a template link code
My Site Root
index.html & aboutus.html
My Site Root>
About Us>
Use _includes !!
├── _includes
├── navigation.html
└── footer.html
<!doctype html>

{% include navigation.html %}
{{ content }}
{% include footer.html %}

<!doctype html>

{% include navigation.html %}
{{ content }}
{% include footer.html %}

---
layout: default
title: Page Title
---
that's not all you can use
---
layout: default
title: Page Title
vendorScripts: ['script1.js', 'script2.js']
customScripts: ['easy-tap.js']
customStyles: ['easy-tap.css']
---
{% for styles in page.customStyles %}
<link rel="stylesheet" href="css/{{ styles }}.css">
{% endfor %}
{% for scripts in page.vendorScripts %}


{% extends "blog/base.html" %} {% load staticfiles %}
Want to get in touch with me? Fill out the form below to send me a message and I will try to get back to you!


Toggle navigation
Álex Go{,nzález}
Archives
Categories
post
1
posts
55
post
Categories = ["Architecture"]
polo
is made with
by
@agonzalezro


title=So Close, but... So Far date=2011-03-22 type=post tags=blog status=published ~~~~~~
Started today pretty impressed that Interoperability @ Microsoft was a sponsor at EclipseCon, which kicked off today. So, score one for community and interoperability. Then, I see that Microsoft is suing Barnes & Nobles and others for their use of Android in their tablet environments. Huh. They almost went an entire day without being ... Microsoft. One for the history books.


Part-of-speech tags in UD v2
Summary
For v2, we propose
- Rename
CONJ
to u-pos/CCONJ. - Extend the use of u-pos/AUX to copula verbs and nonverbal TAMVE particles.
- Minimize usage of u-pos/PART – small language-specific list of words, case must be made for each.
- Loosen borderline between u-pos/PRON and u-pos/DET: set of recommendations instead of purely functional rule.
- Provide more general recommendations about setting language-specific borderlines between word categories.
For related discussion see
- Morphology overview page has a section on POS tags
- Current guidelines for POS tags
- Form vs. function in POS tags
- Issue 159 (
PRON
vs.DET
) and the Uppsala report on determiners - Issue 178 (question particles)
- Issue 237 (
ADV
vs.CONJ
) - Issue 275 (copula
VERB
vs.AUX
) - List of open issues with the POS label
Rename CONJ to CCONJ
We propose to rename the CONJ
tag to CCONJ
(coordinating conjunction)
and thus make it analogous to SCONJ
(subordinating conjunction).
That will hopefully reduce the confusion that we observed in v1:
people have assumed that the CONJ
tag would correspond to the conj
relation,
while in fact it usually went with the relation cc
and practically never with conj
.
Keep PROPN
We considered removing PROPN
as a separate POS tag because
- the motivation to have it is weak in some languages (no grammatical implications except for capital letters);
- the possibility to say that a language does not have
PROPN
does not really solve anything – these languages indeed have the category and typically will want to use it if it exists, to increase cross-linguistic parallelism; - disambiguation from
NOUN
is hard in many languages; - it would be better to have phrase-level named entity annotation, which would include non-noun words (adjectives) and nesting.
We decided to keep the tag in v2 because
- the category has been traditionally distinguished in a significant number of languages and tagsets, and people do not want to lose it there;
- the reasons above do not seem strong enough to remove it;
- we are not going to have named entity annotation in UD v2.
Keep PART but minimize its usage
We considered removing PART
because it is a very small category, which is defined mostly negatively (it is particle if it is not anything else). We decided to keep it because
- we would have to take the current particles one-by-one in each language and decide where to put them;
- in some instances it would still be hard to find a suitable category;
- which may actually lead to creation of several new and even smaller categories.
However, the lists of particles in individual languages should be reviewed anyways. Language-specific documentation must list all particles in the language, and ideally also explain why they are particles.
Note that the current guidelines say that [en] not, [de] nicht etc. are negative particles (but negative determiners like [en] no, or negative auxiliary verbs like [cs] není are not particles). This is the only positive part of the current PART
definition at the language-universal level, because such words were traditionally tagged as adverbs in some languages, and they could be adverbs in the other languages too, had we decided to remove PART
.
Extend the use of AUX
The u-pos/AUX category is currently used for auxiliary verbs, that is verbs used with the syntactic relation u-dep/aux (regardless of whether these verbs can be used as main verbs in other contexts). We propose to extend its use in two ways. First, it can be used for nonverbal particles used to express TAMVE categories, which in v2 will also be analyzed using the u-dep/aux relation. Secondly, it will be extended to copula (u-dep/cop) verbs, which perform a grammaticalized function in nominal clauses.
Borderlines between categories
Parts of speech have traditionally been defined using a mix of morphological, syntactic and semantic criteria. Given that UD is concerned with grammatical annotation, we in general want to give less priority to (purely) semantic criteria. Morphological criteria are very useful but are not applicable to all languages, or even to all categories within morphologically rich languages. It follows that, in many cases, we have to rely primarily on syntactic criteria. However, we believe that the part-of-speech classification is most useful if it captures regular, prevailing syntactic behavior and does not reflect sentence-specific exceptional behavior. Therefore, we should avoid completely functional guidelines for part-of-speech tags that make the tag completely predictable from the syntactic function. In addition to the obvious argument that such guidelines make (some) tags uninformative, they also make it harder to find interesting cross-lingual differences. For example, language X allows words of category A to have syntactic function b, but language Y doesn’t.
We admit that there are ambiguous words that cannot be tagged without considering the context. However, we prefer distinctions based on prevailing syntactic behavior and (when relevant) morphological properties. We should avoid the extreme where (almost) all ambiguities between two categories are resolved solely by syntactic structure, as was the case with pronouns vs. determiners in v1. Here the current definition of PRON
and DET
should be loosened. It will be possible in many languages to enumerate words in both classes, and preferably the lists should be based on prevailing syntactic function and morphological properties, rather than the actual context in each sentence.
There are many pairs of categories with unclear border zones, although not all of them in all languages:
NOUN
can be confused withPROPN
,PRON
,ADJ
and some forms ofVERB
(gerunds, infinitives)PROPN
can be confused withNOUN
andX
(foreign names)ADJ
can be confused withDET
,NUM
(ordinals) and some forms ofVERB
(participles)PRON
can be confused withDET
,NUM
(pronominal quantifiers),ADV
(pronominal adverbs) and possiblyNOUN
DET
can be confused withPRON
,NUM
(pronominal quantifiers),ADV
(pronominal adverbs) and possiblyADJ
NUM
can be confused withADJ
(ordinals),NOUN
(high-value cardinals, e.g. “million”),PRON
,DET
(pronominal quantifiers) andADV
(adverbs of degree/quantity, multiplicative numerals like [cs] sedmkrát “seven times” etc.)ADV
can be confused withADJ
,PRON
,DET
(pronominal adverbs),NUM
(adverbial numerals and adverbs of degree/quantity) and some forms ofVERB
(transgressives/converbs); furthermore, some are on the border toADP
,SCONJ
andCCONJ
VERB
can be confused withAUX
(but we are proposing to removeAUX
),NOUN
(gerunds),ADJ
(participles),ADV
(transgressives/converbs)ADP
can be confused withSCONJ
,ADV
, some secondary prepositions also withNOUN
and other categoriesSCONJ
can be confused withADP
,ADV
andCCONJ
CCONJ
can be confused withADV
andSCONJ
PART
should in theory not be confused with anything because then it should not bePART
; nevertheless, at least some traditional particles are nowADP
,ADV
,SCONJ
orCCONJ
, and the particle not would be traditionallyADV
in some languagesINTJ
can sometimes be confused withNOUN
,ADJ
,VERB
orADV
if they are used like exclamations; but arguably these could then not be taggedINTJ
PUNCT
can be confused withSYM
SYM
can be confused withPUNCT
X
as a tag for foreign word can be confused withPROPN
when the word itself is not a proper noun in the foreign language, but is a part of a longer book/movie title
Some pairs are less problematic than others because some categories are functionally more compatible than others.
It is acceptable if PRON
and DET
are pre-categorized and distinguished mostly by word list or morphology,
because they can be seen as two subcategories of a broader category of nominals; if a word is classified as DET
but it occurs in place of a noun phrase, it can be explained by ellipsis and we do not have to switch the tag
to PRON
in such contexts. However, some categories are not compatible and if a word occurs in both, it has to
be taken as two separate lemmas; consequently it has to be disambiguated according to sentence context.
A good example is [en] that and [es] que which can be both a relative pronoun and a subordinating conjunction
(complementizer). We cannot say that all occurrences are either PRON
or SCONJ
because a pronoun can
act as a core argument of a predicate, while complementizer cannot. So we have to distinguish the two functions,
although historically the complementizer may actually come from a grammaticalized pronoun.
Furthermore, we should encourage authors of language-specific documentation to document all borderline cases, but this is not really a change of guidelines.
Proposed principles for UD v2
This text could be added to the morphology overview page, section on POS tags:
- A word’s category should be primarily determined by prototypical (expected) syntactic behavior, as typically recorded in a dictionary, rather than by the context of a particular sentence.
- Morphological behavior may be a good indicator in some languages. If, for example, a language uses distinct inflection patterns for nouns and adjectives, then morphology can be used to distinguish these two categories. Exceptions cannot be excluded but they should be really exceptional and well grounded; when in doubt, use the category determined by morphology (if available).
- Ambiguous words (belonging to two or more categories) do exist. Sometimes by pure coincidence ([en] the can vs. can = to be able to). Sometimes the two words are related but differ morphologically ([en] the book(s) vs. to book, booked, booking).
- Perhaps the most difficult part are ambiguous function words that do not inflect (i.e. morphology does not help us),
yet they perform two or more significantly different syntactic functions, which we normally associate with different
parts of speech. The two functions may not be equally frequent but each of them is more frequent than what could be labeled
as a mere exception (i.e. the wait for his ‘yes’ example is exceptional).
Disambiguating such pairs clearly depends on the context of the given sentence where the word is used.
So how do we know that the difference is “significant enough”?
One clue is that the word, when translated to another language, gets two different translations with different POS tags
(e.g. the English no as response interjection, vs. negative determiner).
Another clue comes from contrasting the UD relations used for the two functions.
For example, distinguishing
PRON
fromSCONJ
([en] that, [es] que, [ru] что / čto) is important because pronouns, unlike conjunctions, may become core arguments and fill valency slots of verbs. DistinguishingSCONJ
fromADP
, orCCONJ
fromADV
seems less crucial and we can probably keep just one POS tag for each such word, based on prototypical usage.
Revised guidelines for pronominal words
This text could be added to the morphology overview page, section on POS tags, and it should also be reflected in the documentation of individual POS tags:
Pronominal words are pronouns, determiners (articles and pronominal adjectives), pronominal adverbs (where, when, how), and in traditional grammars of some languages also pronominal numerals (how much).
- In most cases it is straightforward to determine whether a word is pronominal (see also the PronType feature) but the borderline between indefinite determiners and adjectives is slightly fuzzy. Related languages should synchronize the lists of words they treat as pronominal. The rest of these guidelines demarcate borders within the pronominal group.
- Pronominal adverbs are tagged
ADV
. Their pronominality is encoded using thePronType
feature. Their typical syntactic function is to modify verbs. - Articles (the, a, an) are always tagged
DET
; theirPronType
isArt
. - Pronominal numerals (quantifiers) are tagged
DET
; besidesPronType
, they also use the NumType feature. - Words that behave similar to adjectives are
DET
. (We understand theDET
class as pro-adjectives, which is a slightly broader sense than what is usually regarded as determiners in English. In particular, it is possible that one nominal is modified by more than one determiner.) Similar behavior means:- They are more likely to be used attributively (modifying a noun phrase) than substantively (replacing a noun phrase). They may occur alone, though. If they do, it is either because of ellipsis, or because the hypothetical modified noun is something unspecified and general, as in All [visitors] must pay.
- Their inflection is similar to that of adjectives, and distinct from nouns. They agree with the nouns they modify. Especially the ability to inflect for gender is typical for adjectives and determiners. (Gender of nouns is determined lexically and determiners may be required by the grammar to agree with their nouns in gender; therefore they need to inflect for gender.)
- Non-possessive personal, reflexive or reciprocal pronouns are always tagged
PRON
. - Possessives vary across languages. In some languages the above tests put them in the
DET
category. In others, they are more like a normal personal pronoun in a specific case (often the genitive), or a personal pronoun with an adposition; they are taggedPRON
. - When the above rules do not help, the category should be based on what the traditional grammar of the language says.
- Ideally, language-specific documentation should list pronominal words and their category. These are all closed classes so it should not be difficult.


Add fancy CSS effects to your 'shinydashboards' or 'shiny' apps. 100% compatible with 'shinydashboardPlus' and 'bs4Dash'.
| Version: | 0.1.0 |
| Imports: | htmltools, shiny, shinydashboard |
| Suggests: | shinydashboardPlus, bs4Dash, knitr |
| Published: | 2018-11-18 |
| Author: | David Granjon [aut, cre] |
| Maintainer: | David Granjon <dgranjon at ymail.com> |
| BugReports: | https://github.com/DivadNojnarg/shinyEffects/issues |
| License: | GPL-2 |
| URL: | https://github.com/DivadNojnarg/shinyEffects, https://divadnojnarg.github.io/shinyEffects/ |
| NeedsCompilation: | no |
| Materials: | README NEWS |
| CRAN checks: | shinyEffects results |
| Reference manual: | shinyEffects.pdf |
| Vignettes: |
CSS effects |
| Package source: | shinyEffects_0.1.0.tar.gz |
| Windows binaries: | r-devel: shinyEffects_0.1.0.zip, r-release: shinyEffects_0.1.0.zip, r-oldrel: shinyEffects_0.1.0.zip |
| OS X binaries: | r-release: shinyEffects_0.1.0.tgz, r-oldrel: shinyEffects_0.1.0.tgz |
Please use the canonical form https://CRAN.R-project.org/package=shinyEffects to link to this page.


Simple date and time inputs. No calendars or fancy controls or polyfills. They just guess the date or time the user means. Forgiving and (more or less) locale-aware.
Model value: {{date}}
Some inputs to try:
Model value: {{time}}
Some inputs to try:
ngx-date-input
and ngx-time-input
components are
now available for you to use:


The type of method names to be replaced by queued versions.
Construct a new Queue.
Queue configuration.
Check whether the queue needs to be flushed.
Delay in milliseconds. If defined the queue will be periodically flushed.
Maximum number of entries in the queue before it will be flushed.
Destroy the queue. The queue will first flush all queued actions, and in case it has extended an object, will restore the original object.
Flush all queued calls
Queue a call.
The function or entry to be queued.
Replace a method on an object with a queued version.
Object having the method.
The method name.
Update the configuration of the queue.
Queue configuration.
Extend an object with queuing functionality. The object will be extended with a function flush, and the methods provided in options.replace will be replaced with queued ones.
The object to be extended.
Additional options.
The created queue.
Generated using TypeDoc
A queue.