{% extends "layout.html" %} {% set active_page = "trends" %} {% block title %}Trends {% endblock %} {% block body %}
This page shows different trends in foreign aid spending worldwide since 2000. What’s missing? Drop a line under feedback.
This diagram shows Official Development Assistance (ODA) spending since 2000 for the top 5 sectors. You can also check each sector in specific. Debt reduction is dominating many years and is also counted as ODA spending.
According to the Creditor Reporting System
| Country | Amount | Projects |
|---|---|---|
| {% if entry['recipientcode'] != 998 %}{{ entry['land'] }}{% else %} {{ entry['land'] }} {% endif %} | {{ entry['total_sum']|number_trunc()|number_format() }} USD | {{ entry['total_activities'] }} |
According to the Creditor Reporting System
| Country | Amount | Projects |
|---|---|---|
| {% if entry['recipientcode'] != 998 %}{{ entry['land'] }}{% else %} {{ entry['land'] }} {% endif %} | {{ entry['total_sum']|number_trunc()|number_format() }} USD | {{ entry['total_activities'] }} |
This diagram shows the ODA spending by year and region. Hover over diagrams for exact figures.
This diagram shows the ODA spending by year and donor. Hover over diagrams for exact figures.


{% extends "admin/base_site.html" %} {% load i18n %} {% block bodyclass %}grp-doc{% endblock %} {% block content-class %}{% endblock %} {% block title %}Grappelli Documentation » Submit-Rows{% endblock %} {% block breadcrumbs %}
A submit-row contains options for submitting a form.
The element wrapping buttons for submitting a form is always a .grp-module with an additional class .grp-submit-row. Theses classes might be applied to any type of block-level element. The following examples of submit-rows are using a footer. If you use a footer (or any other kind of HTML5 dom-element like article, section), make sure to insert a hidden header to let it appear in the document outlines.
The submit-row always contains a plain ul with li defining the submit options. Every li in a submit-row floats right by default. If you want a li to float left, just add .grp-float-left.
{% filter force_escape %}
{% endfilter %}
Each li of a submit-row may contain buttons, inputs or links representing the submit options.
The options in a submit-row are represented by the following elements: button /, a href="" / and input /. You have to add .grp-button to each of these elements. By default these elements are visually reduced — add .grp-default to elements you want to emphasize.
{% filter force_escape %}
{% endfilter %}
Links used in submit-rows may be further specified with adding one of the following classes: .grp-delete-link, .grp-cancel-link or .grp-reset-link.
{% filter force_escape %}
{% endfilter %}
To fix the footer at the bottom of the browser window you have to add .grp-fixed-footer to the .grp-module.grp-submit-row
{% filter force_escape %}
{% endfilter %}


(Module for Algebra)
This is a module containing:
Let require "algebra.rb"
then
include Algebra
has done. And require
the scripts defining above modules, automatically.
none.
Algebra.Polynomial(ring [, obj0 , obj1 [, ...]])
Algebra.MPolynomial(ring [, obj0 [, obj1 [, ...]]])
Algebra.ResidueClassRing(ring, mod)
Algebra.AlgebraicExtensionField(field, obj){|x| ... }
Algebra.MatrixAlgebra(ring, m, n)
Algebra.Vector(ring, n)
Algebra.Covector(ring, n)
Algebra.SquareMatrix(ring, size)


This is a utility class for geometric calculations.
public static function getCentroid(vertices:Array, pNameX:String = "x", pNameY:String = "y"):Point
This method gets the centroid of any shape with three or more sides.
Parameters
| vertices:Array — An array of vertices.
|
| |
| pNameX:String (default = "x ") — An optional parameter which allows to set the name identifying the
X-axis value of the vertices.
|
| |
| pNameY:String (default = "y ") — An optional parameter which allows to set the name identifying the
Y-axis value of the vertices.
|
Returns
| Point — A Point object representing the centroid.
|
public static function getHypoteneuse(a:Number, b:Number):Number
This method the hypoteneuse of a triangle.
Parameters
| a:Number — The length of the adjacent side.
|
| |
| b:Number — The length of the opposite side.
|
Returns
| Number — The length of the hypoteneuse.
|
public static function rectangularRadius(width:Number, height:Number):Number
This method gets the maximum distance within a rectangle from its centre.
Parameters
| width:Number — The width of the rectangle.
|
| |
| height:Number — The height of the rectangle.
|
Returns
| Number — The rectangular radius.
|


Try out our Premium Member services: Virtual Legal Assistant, Query Alert Service and an ad-free experience. Free for one month and pay only if you like it.
Central Information Commission CIC/WB/A/2007/00585/AD Dated October 3, 2008 Name of the Appellant : Mr. Nilesh Kumar 1-17, Old Double Storey Lajpat Nagar - IV New Delhi 110 024 Name of the Public Authority : Ministry of Environment & Forests Background
1. The RTI application was filed on 5.1.07 requesting for information against 28 points with respect to the Charter of Corporate Responsibility for Environmental Protection(CREP). The CPIO's reply was sent on 29.1.07 stating that under the RTI Act information only in the form of documents as defined under Section 2(f) can be provided and that once documents are specified, photocopies can be sent after deposit of Rs. 2/- per page. The CPIO enclosed details of no. of pages of the Charter released in March 2003 and the no. of pages contained in the Pollution Control Act Rules and Notifications issued thereunder by Central Pollution Control Board , January 2006. The first appeal was filed by the appellant on 13.2.07 expressing his dissatisfaction with the reply and indicating questions not answered/partially answered. The FAA in his Order dated 29.3.07 stated that 24 items of the appellant's request revolved around CREP guidelines and the fall-out of these guidelines. The remaining queries revolved around issues in other areas and not to CREP. He also stated that the appellant was furnished with various documents and publications on his depositing the prescribed photocopying charges. The FAA added that collecting the information and processing it would amount to disproportionate diversion of public resources. The second appeal was filed before the CIC on 27.4.07.
2. The Bench of Mrs.Annapurana Dixit, Information Commissioner, heard the matter on October 3, 20087
3. The Appellant was present at the hearing along with Advocate Mr. Vivek Sibal who represented the appellant.
4. Mr. Rajneesh Dubey, Appellant Authority represented the Public Authoity Decision
5. The FAA stated that there is no law that makes it mandatory for industries to comply with CREP Guidelines. Some industries are following them because they chose to do so.
6. The Commission noted that the Appellant requested for information against 28 points of which 19 revolved around mandatory compliance with CREP Guidelines by industries. The Commission holds that, in the light of the FAA's statement that it is not mandatory for industries to follow the CREP Guidelines, all 19 points have become redundant.
7. The Commission directs the CPIO to allow the appellant to have access to books, files, documents, minutes of meetings, records etc. for information sought for against points 1, 2, 6, 11, 22 and 23 of the RTI request.
8. CPIO also to ensure that the appellant is provided with information sought against points 12, 14, and 26 from CPCB, if it is available at the CPCB office.
9. With regard to the points 19 and 27 in the RTI request, the Commission holds that the Public Authority is not bound to provide answers to queries with 'what' as the prefix, raised by the Appellant since under the RTI Act, the appellant can seek information that exists in material form as given in the definition of 'Information' in Sections 2(f), (i) (j) of the Act and not seek opinions or assessments.
10. The appeal stands closed.
(Annapurna Dixit) Information Commissioner Authenticated true copy:
(K.G.Nair) Designated Officer Cc:
1. Mr. Nilesh Kumar, 1-17, Old Double Storey, Lajpat Nagar - IV, New Delhi 110 024
2. The Central Public Information Officer, Ministry of Environment & Forests, Paryavaran Bhavan, CGO Complex, Lodhi Road, New Delhi 110 003.
3. The Appellate Authority, Ministry of Environment & Forests, Paryavaran Bhavan, CGO Complex, Lodhi Road, New Delhi 110 003.
4. Officer incharge, NIC
5. Press E Group, CIC


This is a tutorial on how you can make your own lazer cut puzzle using OpenJsCad!
While the name of this page is STL Puzzle, OpenJsCad allows to create regular DXF files as well.
While on the topic of OpenJsCad, I want to give credit to the creators of the library. Most of the fancy 3d rendering on this
page and also much of the structure for this html page is derived from the project source at OpenJsCad on GitHub.
Lets get started making the puzzle!
1. Preface
The goal of this tutorial is to make a puzzle that looks like this:
To do so, we need 3 parts
A backboard plate for the puzzle pieces to lay on
A plate with the puzzle pieces cut out
A clear cover to put on top so that the puzzle can be on display when finished
2. Getting Setup
I have provided the backboard piece and clear cover as solidwork parts or regular dxf files.
Note: These pieces are designed to contain a puzzle 10 inces in diameter.
Below is a simple OpenJsCad rendering of an extruded circle. This is enough to generate an STL file which has
a nice triangle mesh pattern. There are a few parameters to play with below, but you can also just write your own
code to create an extruded shape.
Once you are done playing around, download the STL file and continue to step 4. If you created a 2d drawing, download
the DXF file and skip to step 5.
Open the STL file in MeshLab and save it as a DXF file.
Copy the backboard case .dxf file. Name it puzzle.dxf
Open both DXF files in draft sight.
In DraftSight, copy the dxf geometry from the stl dxf file and paste it in the backboard case dxf. Make sure to paste it
somewhere outside of the backboard case geometry.
Select the stl dxf geometry and color it a different color, such as red. This is so that it can be cut before the backboard is cut.
Using the move tool, click on the center of the stl dxf gemotry, then click on the center of the backboard case.
This should move the stl dxf geometry to the center of the backboard case geometry.
Save the file (it should be called puzzle.dxf)
5. Adding an engraving to the puzzle
Find some image that you want to engrave onto the puzzle. Images that are very simple with obvious outlines work best.
The example puzzle is using this image.
Open the image in inkscape and using the Object>Transform tool, transform the dimensions to 9in x 9in.
Using the Path>Trace Bitmap tool, convert the image to a vector image. You may have to play around with the settings and use the preview
to get everything just right
Delete the underlying bitmap image so that only the vector image is left
Save the file as a DXF
If the DXF file outputed by InkScape doesn't work very well. Try an online tool such as this.
Like Step 4, add the image dxf to the puzzle dxf file. Make sure to color it a entirely different color.
If everthing went well in your puzzle.dxf should look like this:
6. Cut!
Import the combinded dxf file to your lazer cutter's tooling program and cut away!
First cut the backboard case, then the clear case so that you become familiar with the sizes you want.
When cutting the puzzle, the cut order should be: 1. Picture Engraving, 2.  Puzzle Cutout, 4. Frame Circle Cutout
Assemble the puzzle with screws and nuts, screw length will vary depending on the thickness of the material you used.
You will need longer screws for the cover. Also when screwing in the cover, do not tighten the screws too much if you want
the pieces inside to be able to move around a little.


Supervised learning algorithms build a mathematical model of a set of data that contains both the inputs and the desired outputs.
The data is known as training data, and consists of a set of training examples. Each training example has one or more inputs and a desired output, also known as a supervisory signal.
Supervised learning algorithms include classification and regression. Classification algorithms are used when the outputs are restricted to a limited set of values, and regression algorithms are used when the outputs may have any numerical value within a range.
You'll find below the different classification and regression algorithms available in the tool.
Classification algorithms
Logistic Regression
In statistics, the logistic model (or logit model) is used to model the probability of a certain class or event existing such as pass/fail, win/lose, alive/dead or healthy/sick.
Read more
K-Nearest Neighbors
In pattern recognition, the k-nearest neighbors algorithm (k-NN) is a non-parametric method used for classification and regression, but here only its classification implementation is available. The input consists of the k closest training examples in the feature space. The output is a class membership.
Read more
Support Vector Machine / Kernel Support Vector Machine
Given a set of training examples, each marked as belonging to one or the other of two categories, an SVM training algorithm builds a model that assigns new examples to one category or the other, making it a non-probabilistic binary linear classifier.
Read more
Naive Bayes
In machine learning, naive Bayes classifiers are a family of simple "probabilistic classifiers" based on applying Bayes' theorem with strong (naive) independence assumptions between the features.
Read more
Decision Tree Classification
In computer science, Decision tree learning uses a decision tree (as a predictive model) to go from observations about an item (represented in the branches) to conclusions about the item's target value (represented in the leaves).
Read more
Random Forest Classification
Random forests or random decision forests are an ensemble learning method for classification, regression and other tasks that operates by constructing a multitude of decision trees at training time and outputting the class that is the mode of the classes (classification) or mean prediction (regression) of the individual trees.
Read more
Regression algorithms
Linear Regression
In statistics, linear regression is a linear approach to modeling the relationship between a scalar response (or target) and one or more explanatory variables (or features). The case of one explanatory variable is called simple linear regression. For more than one explanatory variable, the process is called multiple linear regression.
Read more
Polynomial Regression
In statistics, polynomial regression is a form of regression analysis in which the relationship between the independent variable x and the dependent variable y is modelled as an nth degree polynomial in x.
Read more


Details goes here. . . . . . .
description description description descriptiondescriptiondescriptiondescription
Learn more


Curriculum Vitae for Anton Fletcher
Career Goal
I have always worked with computers - I hope to continue to work with them and learn more about how I can use them to help, and entertain people. I thrive on building software people enjoy using, and really hope I can get them to say "wow!".
Online
Work Experience
Personal Projects
Environment
- Linux
- Windows
- Unity3D
- C#
- Python
Description
- I am a hobbiest game developer, I recreationally program games in my free time.
Community
- As a indie game developer, I am active within vaious game development communities - in particular Ludum Dare,
reddit (/r/gamedev), Facebook (Indie Game Developers), and Lost Decade's discord group.
Finished Works
-
Poker Kingdoms
Poker Kingdoms is a blend between tile matching games such as Bejeweled, and Poker
the rework of this game has been Greenlit for steam and final touches are being made to the initial release
-
The Zen of Zen
The Zen of Zen was created in a single day as part of the 1 Game a Month program.
- Vine
-
Symbolic Vapour
Freelance client work - realizing design from concepts and customizing templates.
Software Engineer
October 2016 - December 2016
Blackboard
North Adelaide, South Australia
Environment
- OSX
- Virtualized Linux Docker Host
- PHP
- Moodle
- Python/web2py
- Go
Description
- Development of internal systems tools for monitoring, deployment, and client communications
- Refactoring, testing, and maintenance of custom file holder
Responsibilities
- Development of core level systems for main product line (Moodle)
- Building customizations for various open source projects for systems work
Systems Administrator
December 2013 - Present
Blackboard
North Adelaide, South Australia
Environment
- Linux
- Puppet
- Git/Gerrit
- Nagios/Graphite/New Relic
- Vagrant
- Python/web2py
Description
- Operation and maintenance of systems supporting moodle instances
- Despite being more of a systems role, my focus has remained focussed on code, providing tools to aid in maintaining systems
Responsibilities
- On call monitoring of infrastructure, actioning of events
- Large scale secure backups
- Provisioning new services
- Diagnosing, and fixing system faults
Accomplishments
- Automation of highly manual fault reporting procedure
- Ongoing work expanding towards a client facing reporting tool
- Extending to provide monthly reports of system stability and operations
actions.
- Creation of high-level display of system faults for large screen display
- Custom interfaces created for Nagios, Foreman, and graphite
- AJAX front end to bring real time information from multiple sources
Applications & Systems Administrator
July 2013 - December 2013
Netspot
North Adelaide, South Australia
Environment
- Linux
- PHP
- Moodle
- Postgres
Description
- High level support of Moodle installations
Responsibilities
- Action bug reports and user faults escallated from help-desk and account managers
Software Developer
December 2011 - July 2013
WorldWeb Management Services
Adelaide, South Australia
Internet Services
Environment
- Linux
- Apache
- MySQL
- PHP
- ContentOne(In-house CMS)
Description
- Development of business management software for third parties.
Responsibilities
- Develop Software catering to business rules for a variety of clients
- Allow customer service team to design, measure, and layout solar panels based on Google Maps Data
- Export layouts to images and PDFs using HTML5 element
- Monitor stock in multiple warehouses, track incoming, and outgoing shipments, and transfers
- Allocate workers based incoming jobs, generate worksheets and rosters
- Calculate commissions based on jobs attended
- Site to site secure communication channel interfacing legacy system with web-interface
- Scheduling application allowing for repeating, and one off appointments, changing frequencies based on season
Enterprise Architect
2010 - September 2011
Ballistic Media
Adelaide, South Australia
Internet Services
Environment
- Linux
- Apache 2
- MySQL
- PHP
- CodeIgnighter
Description
- CGChallenge is a twice annual international art competition. Community members are tasked to produce still images and videos to represent a specific topic and are judges by leaders of the industry.
- Ballistic Publishing distributes high-quality digital art books from warehouses in Australia and the United States, and is looking to expand its distribution channels.
Responsibilities
- Design and Implement media submission system, allowing users to easily present large digital assets to other users and a panel of judges.
- Develop user workflow through CodeIgniter MVC framework.
- Implement HTML based upload progress
- Integrate with Cloud Based Storage (Amazon S3)
- Integrate with Cloud Based Transcoding (Zencoder)
- Develop user-facing video preview using Mencoder & jQuery allowing users to select static preview frames
- Design and Implement black boxed e-commerce system, allowing multiple stores, and warehouses to be managed through a single back-end.
- Develop initial shopping cart
- Design Secure API allowing complete detachment of store software and front-end sites
- Create shipping algorithm finding cheapest, and fastest methods of shipping a user’s selected materials
- Create discounting system allowing discounts to be applied to a cart in a variety of ways (individual products, shipping, groups of products)
- Create series of abstractions, for warehouses, shipping methods, and product types, supporting current inventory and allowing easy implementation for new sales types
- Built a CRUD layer for administration that allows overwriting for more user friendly output
Senior Developer
2008 - 2010
Ballistic Media
Adelaide, South Australia
Internet Services
Environment
- Linux
- Apache 2
- MySQL
- Google Analytics
- Google DoubleClick
- Google Apps For Your Domain
- CodeIgniter
- Solr/Lucene
Description
- CGSociety receives much of its funding from advertisers. The existing advertising software that was being used was discovered to be unreliable in its delivery, and there was no formal way of measuring how users moved around the site
- Despite a decline in usage, system load continued to grow as the amount of content increased, a search engine was a good way to offload the heaviest of tasks
- Company email had been internally managed, with a large overhead of time for small results
As the world moved towards portable devices, the reliance on closed products became evident. - Moving to a cloud based solution meant that staff had their mail, and documents on anything that had access to the Internet
Responsibilities
- Implement Page Tracking allowing metrics of site usage to be taken
- Simple static Urchin codes placed across all sites
- Paths and goals developed helping track where users were going
- More complicated Urchin codes supplied by custom extension for internal framework
- Develop a search engine to offload some of the workload of forums and also give users the opportunity to see more content that was important to them.
- Setup Solr/Lucene server
- Developed comprehensive schema allowing various styles of articles to be represented similarly
- Developed indexing software including a set of indexers to convert various articles into a format usable by schema
- Developed CodeIgniter library to translate permissions from vBulletin format allowing pure CodeIgniter code
- Developed CodeIgniter interface for PHP/Solr hooks
- Replace Existing advertising system with 3rd party managed system
- Developed hooks for new advertising system under existing framework, and CodeIgniter
- Developed standalone IFrame ad unit for 3rd parties
- Configured DoubleClick to work with a month-by month sales system, and produced a detailed how-to on ad placement
- Replace internally managed mail system with 3rd party hosted system
- Train staff in using Gmail efficiently, helping them transition from a sorting based workflow to a search based one
- Offset reliance on Microsoft Office and Windows in favour of web-based alternative.
- Demonstrated the power of shared, online documents
- Moved important company wide documents online allowing single current version available to all
Developer
2006 - 2008
Ballistic Media
Adelaide, South Australia
Internet Services
Environment
- Linux
- MySQL
- PHP
- Synergy (Internal Framework)
- vBulletin
- MediaWiki
Description
- CGPortfolio was developed as a way to give artists a way to display their artwork and network with each other
- CGWiki was put in place in the hopes that we could build a strong repository of knowledge in digital art
- CGTalk is likely the largest online community of digital artists in the world, many members coming from movie, and game studios.
Responsibilities
- Develop an online gallery system for members of CGSociety.
- Build gallery system based on a collection of HTML pages
- Created an upload system that generated forum posts on CGTalk and then imported them into CGPortfolio
- Built a local content delivery network allowing files to be distributed across several servers
- Used ImageMagick to re-size and thumbnail images protecting users’ copyright
- Implement a Wiki allowing users to contribute to a central knowledge-base
- Created login module for MediaWiki using information from vBulletin
- Created a series of templates for members to use creating their articles
- Coach community members in using the MediaWiki markup
- Worked with forum-leaders (moderators) on CGTalk to allow the company to make choices based on community feedback
- Worked with forum-leaders to organise community events such as CGChallenges selecting topics, and judges, as well as running voting, and getting feedback when results were posted
Technical Director
2004 - 2006
CGCharacter
Mylor, South Australia
Broadcasting, Music and Film
Environment
- 3DStudio Max
- Combustion
- Photoshop
Description
- Provided the film “A Sound of Thunder” with musculature animation, as well as some fluid interaction
- Generated fly through videos for development project in Dubai
- Created Crowd Scenes for Documentary series
- Animated figures demonstrating muscle use for fitness purposes
Responsibilities:
- Managed render servers to process heavy computing tasks
- Fed animation files through pipeline as they were completed and manged progress
- Rendered output files to transparent plates and quickly composited with live footage
- Initiated and monitored file transfers for delivery
- Imported CADD files into rendering software creating realistic materials and rendering output
- Developed scripts to simulate crowds of people
- Developed scripts to help generate renderable files
- Movement matched video files to character animation
- Developed scripts to change materials on characters to demonstrate use
- Developed toolkit to eliminate simple repetitive tasks
Education
Bachelor of Computing (Multimedia)
2001 - 2004
University of South Australia
Magill, South Australia
The program is designed to educate students for a career as computer professionals specialising in multimedia. It provides a broad and fundamental understanding of the theory and practice of computers and information technology, plus specialist knowledge of multimedia concepts and techniques. The program prepares graduates for professional careers in the computing and multimedia industry in general, and specialist multimedia software development organisations in particular.
High School
January 1991 - July 1995
Marryatville High School
Marryatville, South Australia


In Class Part One Alnouri
This is a paragraph
Sample headings
Sample list
This is a new list
Listed
Information
Goes
Here


Session 1
Girl Develop It is here to provide affordable and accessible programs to learn software through mentorship and hands-on instruction.
Some "rules"
Meet your team!
Quickly go around the room and introduce yourself.
Format of Class
Tuesday & Thursday each week from 6-8pm.
Small homework assignments on Tuesday
Larger homework assignments on Thursday
Today
Getting your computer setup.
Introduction to HTML.
Thursday
Introduction to CSS
We'll be using the following tools in class today:
A markup language is a set of markup tags:
<tagname>content</tagname>
Each HTML tag describes its content:

This sentence goes in a paragraph (p) tag.

If you 'View Page Source', you see this:
Your Content
+ HTML: Structure
+ CSS: Presentation
= Your Website
A website is a way to present your content to the world, using HTML to structure that content, and CSS to make it look good.
A paragraph is your content

A paragraph is your content

A paragraph is your content

Content in the middle

The p tag means this content is a paragraph.

The header tag means this content is a website's header.
Whenever you type an opening tag, immediately type the closing tag, then fill in your content.

Now I can add content!
Shorthand

This is content within the opening and closing tags.

The examples are shorthand for

 and
Attributes
Adding attributes to an HTML tag provides additional information about the HTML element
Attributes

Lorem ipsum

GDI
Doctype
The first thing in an HTML file is the doctype, which tells the browser which language the page is using:
<!DOCTYPE html>
The doctype is case-insensitive.
DOCtype, doctype, DocType and DoCtYpe are all valid.
HTML Element
After <!DOCTYPE html>, the page content must be contained between  tags.
<!DOCTYPE html>

Head Element
The head contains information about the page, but does not contain page content. It contains elements that let the browser know:
<!DOCTYPE html>

Body Element
The body contains the actual content of the page. Everything that is contained in the body is visible to the user.
Most of your work will be done within the  tags!
<!DOCTYPE html>

Memorize this ☺
<!DOCTYPE html>

<title>Title of the page</title>

All of your page content goes here

All the files for your site should be stored within the same folder.
This includes:
Note: File names should not include spaces or special characters. File names ARE case sensitive.
Go ahead and create your folders
Ignore the HTML and CSS files for now
Later we'll add some content to it!
All elements "nest" inside one another
Nesting is what happens when you put other containing tags inside other containing tags. For example, you would put the

 inside of the  tags. The

 is now nested inside the , and is one of its descendants
All your page's content is 'nested' inside the body element:

A paragraph inside the body element

And other elements can be nested inside of that:

A paragraph inside the body element
which has some italic text
and
some bold text

⇒ A paragraph inside the body element which has some italic text and some bold text
HTML elements are often looked at as a family tree. Developers will often refer to elements as "siblings", "immediate children", and "descendants".
Can you name any siblings?
<!DOCTYPE html>

<title>Title of the page</title>

All of your page content goes here

How about immediate children?

I'm indented!

I'm also indented!

This will make your life much easier down the road, as you add more content and style your pages.
HTML ignores multiple whitespaces in a row. You can add consecutive white space characters (spaces, tabs, & carriage returns) into your HTML, but when you view that page — all but one disappears!
HTML:

Two carriage returns
Three carriage returns
Plus multiple spaces ...

Result:
Two carriage returns Three carriage returns Plus multiple spaces ...
To force consecutive spaces to show, use (stands for "no-break space") in your HTML instead of spaces.
Paragraph
HTML:

Paragraph 1

Paragraph 2

Paragraph 3

Paragraph 1

Paragraph 2

Paragraph 3

Result:
Paragraph 1
Paragraph 2
Paragraph 3
Paragraphs in Action
Paragraphs allow you to format your content in a readable fashion.
You can edit how paragraphs are displayed with CSS
Headings
HTML:

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5

Heading 6

Result:
Headings in Action
Formatted text
HTML:

Here is a paragraph with Emphasized text and Important text.

Result:
Here is a paragraph with Emphasized text and Important text.
Let's add some content to our site!
Remember to place content in the body element, not the head
Links
Standard links have three components:

GDI Boulder/Denver
href="http://www.girldevelopit.com/chapters/boulder"
GDI Boulder/Denver
Additional Link Options
title="Read more about GDI Boulder/Denver"
target="_blank" (opens link in a new tab)
GDI Boulder
Additional Link Options
Additional Link Options
<a<EMAIL_ADDRESS>me!
Let's add links to our site!
Add links that:
Images
Images have three components:

src=""
alt="Picture of a city"
Images

* Notice: This tag is our first example of a stand-alone or "self-closing" element.
Relative vs. absolute paths for links, images, etc.
"filename.jpg"
"images/filename.jpg"
"http://www.girldevelopit.com/chapters/boulder"
Line Break

You spin me right round, baby

Right round like a record, baby

Right round round round

You spin me right round, baby
Right round like a record, baby
Right round round round
Let's add some images and line breaks to our page. We can even turn some images into links!
Unordered and ordered lists
HTML:

Unordered List Item

Another List Item

Ordered List Item

Another List Item

Result:
Lists in Action
Lists can be used to organize any list of items.
You'd be surprised how often lists are used in web development.
Let's add one of each ordered and unordered lists to our page.
We can make a list of links or even a list of images!
Comments
You can add comments to your code that will not be seen by the browser, but only visible when viewing the page source.

Comments can be used to organize your code into sections so you (or someone else) can easily understand your code. It can also be used to 'comment out' large chunks of code to hide it from the browser.

Header Content

Tables
Tables are a way to represent complex information in a grid format. Tables are made up of rows (tr), which contain cells (th for table header cells, or td for standard table data cells).
HTML:

Head 1
Head 2

Data 1
Data 2

Result:
| Head 1 | Head 2 |
|---|---|
| Data 1 | Data 2 |
Tables in Action
Character Codes
©
»
< and >
How to Style Sites — Introduction to CSS
If you haven't already, try to make one of each element discussed in the lecture today and save your HTML file. Next week we'll style it!
Introduce yourself in the slack channel! #html_css_4wk


Click the button to display an alert box:
Click the button to display a confirm box.
Click the button to demonstrate the prompt box.
Click the button to demonstrate line-breaks in a popup box.


ESIOSOFT
Milk
Collection
Sale
Item
transections
stock
Reports
Customer
Society
Society
Rate Charts
Members
Expenses


form test
pls don't submit the form
enter a username
enter the password
pick the color
type the number
submit
hijacking search
Reddit search
reddit search
Google search
google search
youtube search


All I desire for my country is happiness. Let me be the first person to wish you a special Happy 75th Independence Day!
Let's salute our great nation on its Independence Day!
I hope you all feel grateful for the freedom you have and are proud of the nation you were born to.


As always, partners grows with you!
Temporibus autem quibusdam et aut officiis debitis is aut rerum necessitatibus saepes eveniet ut etes seo lage voluptates repudiandae sint et molestiae non mes for Creating futures through building pres preservation.
Lorem ipsum dolor sit , consectet adipisi elit, sed do eiusmod tempor for enim adesg ens minim veniam.
Lorem ipsum dolor sit , consectet adipisi elit, sed do eiusmod tempor for enim adesg ens minim veniam.
Lorem ipsum dolor sit , consectet adipisi elit, sed do eiusmod tempor for enim adesg ens minim veniam.
Lorem ipsum dolor sit , consectet adipisi elit, sed do eiusmod tempor for enim adesg ens minim veniam.
Cases completed
Consultants
Awards winning
Years of Experiences
As always, partners grows with you!
The lysine contingency it's intended to prevent the spread of the animals is case they ever got off the island. Dr. Wu inserted a gene that makes a single faulty enzyme.
Learn MoreThe lysine contingency it's intended to prevent the spread of the animals is case they ever got off the island. Dr. Wu inserted a gene that makes a single faulty enzyme.
Learn MoreThe lysine contingency it's intended to prevent the spread of the animals is case they ever got off the island. Dr. Wu inserted a gene that makes a single faulty enzyme.
Learn MoreThe lysine contingency it's intended to prevent the spread of the animals is case they ever got off the island. Dr. Wu inserted a gene that makes a single faulty enzyme.
Learn MoreThe lysine contingency it's intended to prevent the spread of the animals is case they ever got off the island. Dr. Wu inserted a gene that makes a single faulty enzyme.
Learn MoreThe lysine contingency it's intended to prevent the spread of the animals is case they ever got off the island. Dr. Wu inserted a gene that makes a single faulty enzyme.
Learn MoreThe lysine contingency it's intended to prevent the spread of the animals is case they ever got off the island. Dr. Wu inserted a gene that makes a single faulty enzyme.
Learn MoreThe lysine contingency it's intended to prevent the spread of the animals is case they ever got off the island. Dr. Wu inserted a gene that makes a single faulty enzyme.
Learn MoreThe lysine contingency it's intended to prevent the spread of the animals is case they ever got off the island. Dr. Wu inserted a gene that makes a single faulty enzyme.
Learn MoreThe lysine contingency it's intended to prevent the spread of the animals is case they ever got off the island. Dr. Wu inserted a gene that makes a single faulty enzyme.
Learn MoreThe lysine contingency it's intended to prevent the spread of the animals is case they ever got off the island. Dr. Wu inserted a gene that makes a single faulty enzyme.
Learn MoreThe lysine contingency it's intended to prevent the spread of the animals is case they ever got off the island. Dr. Wu inserted a gene that makes a single faulty enzyme.
Learn MoreAs always, partners grows with you!
All what customers said about us
Imagination… What we can easily see is only a small percentage of what is possible. Logistics through innovation, dedication, and technology.
Fatma HassanImagination… What we can easily see is only a small percentage of what is possible. Logistics through innovation, dedication, and technology.
Marion RavenOur financial advisers always help you
Mon-Sat 10.00am - 6.00p.m
Sun 11.30am - 3.00p.m
+1 1234-456-789
<EMAIL_ADDRESS>Newsletter for recieve
© 2016 Amwal - Powered By Mohamed Arafa


Weather Tracker
Historic Weather Data
Temperature
Pressure
Humidity
Brightness
Wind Speed
umbrella code available on
GitHub


A no BS Open Source Hackathon
25th & 26th March 2017
₹ 75,000
Cash Prize
Cash Prize
About
Mumbai Hackathon is hosted anually by ERPNext and Don Bosco Institute of Technology
The intention of hosting Mumbai Hackathon is to promote open source software development
On 25th March 2017, more than 40 teams participated and 25+ Open Source applications were developed within 30 Hours
Check out projects made at Mumbai Hackathon here
Event hosted by
ERPNext Open Source Software Foundation & Don Bosco Institute of Technology


We are final year Mechatronics engineering students from the University of Waterloo. We have a shared interest in sports and decided to tackle an obvious problem that ruins the viewing experience: poor action tracking.
Dhruv will be responsible for leading the mechanical design of the camera gimbal as well as developing and maintaining the team’s website.
Kalen will be responsible for the mechanical design and construction of the camera gimbal, along with system integration and testing.
Sanjay will be responsible for leading the software development, namely the basketball tracking implementation as well as software integration.
Mauris will be responsible for general project management and leading the electrical and controls aspect of the project.


Photo by Werner Bechtelar
Recent Photos
Photo by Werner Bechtelar
Photo by Werner Bechtelar
Photo by Werner Bechtelar
Photo by Werner Bechtelar
Photo by Werner Bechtelar
Photo by Werner Bechtelar
Photo by Werner Bechtelar
Photo by Werner Bechtelar
Photo by Werner Bechtelar
Photo
Photo by Werner Bechtelar
×
Photo
Photo by Werner Bechtelar
×
Photo
Photo by Werner Bechtelar
×
Photo
Photo by Werner Bechtelar
×
Photo
Photo by Werner Bechtelar
×
Photo
Photo by Werner Bechtelar
×
Photo
Photo by Werner Bechtelar
×
Photo
Photo by Werner Bechtelar
×
Photo
Photo by Werner Bechtelar
×


Titanic Clearing Southampton.
Picture of the Titanic before setting sail. Picture courtesy of Steve Raffield.


A collection of acceleration schemes for proximal gradient methods for estimating penalized regression parameters described in Goldstein, Studer, and Baraniuk (2016) <arXiv:1411.3406>. Schemes such as Fast Iterative Shrinkage and Thresholding Algorithm (FISTA) by Beck and Teboulle (2009) <doi:10.1137/080716542> and the adaptive stepsize rule introduced in Wright, Nowak, and Figueiredo (2009) <doi:10.1109/TSP.2009.2016892> are included. You provide the objective function and proximal mappings, and it takes care of the issues like stepsize selection, acceleration, and stopping conditions for you.
| Version: | 0.1.0 |
| Published: | 2018-04-10 |
| Author: | Eric C. Chi [aut, cre, trl, cph], Tom Goldstein [aut] (MATLAB original, https://www.cs.umd.edu/~tomg/projects/fasta/), Christoph Studer [aut], Richard G. Baraniuk [aut] |
| Maintainer: | Eric C. Chi <ecchi1105 at gmail.com> |
| License: | MIT + file LICENSE |
| NeedsCompilation: | no |
| Citation: | fasta citation info |
| CRAN checks: | fasta results |
| Reference manual: | fasta.pdf |
| Package source: | fasta_0.1.0.tar.gz |
| Windows binaries: | r-devel: fasta_0.1.0.zip, r-release: fasta_0.1.0.zip, r-oldrel: fasta_0.1.0.zip |
| OS X binaries: | r-release: fasta_0.1.0.tgz, r-oldrel: fasta_0.1.0.tgz |
Please use the canonical form https://CRAN.R-project.org/package=fasta to link to this page.


Welcome to
Our Beautiful Online Shop!
Email
Password
Remember me
Forgot Password?
Login
New to TrustMeShop?
Open an Account


This document is a high-level overview of how to create a complete CORBA (Common Object Request Broker Architecture) application using IDL (Interface Definiton Language) to define interfaces and the Java IDL compiler to generate stubs and skeletons. For more information on the development process, and a more detailed tutorial on creating a CORBA application using IDL, see Getting Started with Java IDL: The Hello World Tutorial. You can also create CORBA application by defining the interfaces in the Java programming language. For more information and a tutorial on this development process, see the Java RMI-IIOP documentation.
In this release of Java SE, the server-side implementation generated by the idlj compiler is the Portable Servant Inheritance Model, also known as the POA model. The POA, or Portable Object Adapter, is discussed in more detail in Portable Object Adapter. This document presents a sample application created using the default behavior of the idlj compiler, which uses a POA server-side model.
CORBA supports at least two different server-side mappings for implementing an IDL interface:
Using the Inheritance Model, you implement the IDL interface using an implementation class that also extends the compiler-generated skeleton.
Inheritance models include:
NOTE: ImplBase is deprecated in favor of the POA model, but is provided to allow compatibility with servers written in J2SE 1.3 and prior. We do not recommend creating new servers using this nonstandard model.
Using the Delegation Model, you implement the IDL interface using two classes:
The Delegation model is also known as the Tie model, or the Tie Delegation model. It inherits from either the POA or ImplBase compiler-generated skeleton, so the models will be described as POA/Tie or ImplBase/Tie models in this document.
This tutorial presents the POA Inheritance model for server-side implementation. For tutorials using the other server-side implementations, see the following documents:
The Tie Model is a delegation model. Use the idlj compiler to first generate server-side bindings. Then, run the idlj compiler a second time with the with the -fallTie option to generate Tie model server-side bindings. For the interface Hello, HelloPOATie.java is one of the generated files. The constructor to HelloPOATie takes a delegate or a delegate and a poa. You must provide the implementation for delegate and/or the poa, but the delegate does not have to inherit from any other class, only the interface HelloOperations. For more information, refer to the IDL to Java Language Mapping Specification.
You might want to use the Tie model instead of the typical Inheritance model if your implementation must inherit from some other implementation. Java allows any number of interface inheritance, but there is only one slot for class inheritance. If you use the inheritance model, that slot is used up . By using the Tie Model, that slot is freed up for your own use. The drawback is that it introduces a level of indirection: one extra method call occurs when invoking a method.
The ImplBase server-side model is an Inheritance Model, as is the POA model. Use the idlj compiler with the -oldImplBase flag to generate server-side bindings that are compatible with versions of Java IDL prior to J2SE 1.4. Given an interface Hello defined in Hello.idl, the file _HelloImplBase.java is generated. You must provide the implementation for Hello and it must inherit from _HelloImplBase.
Note that using the -oldImplBase flag is non-standard: these APIs are being deprecated. You would use this flag ONLY for compatibility with existing servers written in J2SE 1.3 or earlier. In that case, you would need to modify an existing MAKEFILE to add the -oldImplBase flag to the idlj compiler, otherwise POA-based server-side mappings will be generated.
This document contains:
To create this example, create a directory named hello/ where you develop sample applications and create the files in this directory, or download the example code and unzip it into your sample applications directory.
Hello.idl
)The first step to creating a CORBA application is to specify all of your objects and their interfaces using the OMG's Interface Definition Language (IDL). IDL has a syntax similar to C++ and can be used to define modules, interfaces, data structures, and more. The IDL can be mapped to a variety of programming languages. The IDL mapping for Java is summarized in IDL to Java Language Mapping Summary.
The following code is written in the OMG IDL, and describes a CORBA object whose sayHello() operation returns a string and whose shutdown() method shuts down the ORB. To learn more about OMG IDL Syntax and Semantics, read Chapter 3 of the CORBA 2.3.1 Specification.
Hello.idl
module HelloApp { interface Hello { string sayHello(); oneway void shutdown(); }; };NOTE: When writing code in OMG IDL, do not use an interface name as the name of a module. Doing so runs the risk of getting inconsistent results when compiling with tools from different vendors, thereby jeopardizing the code's portability. For example, code containing the same names could be compiled with the IDL to Java compiler from Sun Microsystems and get one result. The same code compiled with another vendor's IDL to Java compiler could produce a different result.
To complete the application, you simply provide the server
(HelloServer.java
) and client
(HelloClient.java
) implementations.
HelloServer.java
)The example server consists of two classes, the servant and the server. The servant, HelloImpl, is the implementation of the Hello IDL interface; each Hello instance is implemented by a HelloImpl instance. The servant is a subclass of HelloPOA, which is generated by the idlj compiler from the example IDL. The servant contains one method for each IDL operation, in this example, the sayHello() and shutdown() methods. Servant methods are just like ordinary Java methods; the extra code to deal with the ORB, with marshaling arguments and results, and so on, is provided by the skeleton.
The HelloServer class has the server's main() method, which:
This example provides an example of a transient object server. For an example of the "Hello World" program with a persistent object server, see Example 2: Hello World with Persistent State. For more discussion of CORBA servers, see Developing Servers.
For more discussion of the code, see the detailed tutorial topic Getting Started with Java IDL: Developing a Hello World Server.
HelloServer.java
// HelloServer.java // Copyright and License import HelloApp.*; import org.omg.CosNaming.*; import org.omg.CosNaming.NamingContextPackage.*; import org.omg.CORBA.*; import org.omg.PortableServer.*; import org.omg.PortableServer.POA; import java.util.Properties; class HelloImpl extends HelloPOA { private ORB orb; public void setORB(ORB orb_val) { orb = orb_val; } // implement sayHello() method public String sayHello() { return "\nHello world !!\n"; } // implement shutdown() method public void shutdown() { orb.shutdown(false); } } public class HelloServer { public static void main(String args[]) { try{ // create and initialize the ORB ORB orb = ORB.init(args, null); // get reference to rootpoa & activate the POAManager POA rootpoa = POAHelper.narrow(orb.resolve_initial_references("RootPOA")); rootpoa.the_POAManager().activate(); // create servant and register it with the ORB HelloImpl helloImpl = new HelloImpl(); helloImpl.setORB(orb); // get object reference from the servant org.omg.CORBA.Object ref = rootpoa.servant_to_reference(helloImpl); Hello href = HelloHelper.narrow(ref); // get the root naming context // NameService invokes the name service org.omg.CORBA.Object objRef = orb.resolve_initial_references("NameService"); // Use NamingContextExt which is part of the Interoperable // Naming Service (INS) specification. NamingContextExt ncRef = NamingContextExtHelper.narrow(objRef); // bind the Object Reference in Naming String name = "Hello"; NameComponent path[] = ncRef.to_name( name ); ncRef.rebind(path, href); System.out.println("HelloServer ready and waiting ..."); // wait for invocations from clients orb.run(); } catch (Exception e) { System.err.println("ERROR: " + e); e.printStackTrace(System.out); } System.out.println("HelloServer Exiting ..."); } }
HelloClient.java
)The example application client that follows:
For more discussion of the details of the code, see Getting Started with Java IDL: Developing a Client Application.
HelloClient.java
// Copyright and License import HelloApp.*; import org.omg.CosNaming.*; import org.omg.CosNaming.NamingContextPackage.*; import org.omg.CORBA.*; public class HelloClient { static Hello helloImpl; public static void main(String args[]) { try{ // create and initialize the ORB ORB orb = ORB.init(args, null); // get the root naming context org.omg.CORBA.Object objRef = orb.resolve_initial_references("NameService"); // Use NamingContextExt instead of NamingContext. This is // part of the Interoperable naming Service. NamingContextExt ncRef = NamingContextExtHelper.narrow(objRef); // resolve the Object Reference in Naming String name = "Hello"; helloImpl = HelloHelper.narrow(ncRef.resolve_str(name)); System.out.println("Obtained a handle on server object: " + helloImpl); System.out.println(helloImpl.sayHello()); helloImpl.shutdown(); } catch (Exception e) { System.out.println("ERROR : " + e) ; e.printStackTrace(System.out); } } }
Despite its simple design, the Hello World program lets you learn and experiment with all the tasks required to develop almost any CORBA program that uses static invocation. Static invocation, which uses a client stub for the invocation and a server skeleton for the service being invoked, is used when the interface of the object is known at compile time. If the interface is not known at compile time, dynamic invocation must be used.
This example requires a naming service, which is a CORBA service that allows CORBA objects to be named by means of binding a name to an object reference. The name binding may be stored in the naming service, and a client may supply the name to obtain the desired object reference. The two options for Naming Services shipped with this release of Java SE include orbd (Solaris, Linux, or Mac OS X or Windows), a daemon process containing a Bootstrap Service, a Transient Naming Service, a Persistent Naming Service, and a Server Manager, and tnameserv (Solaris, Linux, or Mac OS X or Windows), a transient naming service that is provided for backward compatibility. This example uses orbd.
When running this example, remember that, when using Solaris software, you must become root to start a process on a port under 1024. For this reason, we recommend that you use a port number greater than or equal to 1024. The -ORBInitialPort option is used to override the default port number in this example. The following instructions assume you can use port 1050 for the Java IDL Object Request Broker Daemon, orbd. You can substitute a different port if necessary. When running these examples on a Windows machine, subtitute a backslash (\) in path names.
To run this client-server application on your development machine:
idlj -fall Hello.idl
You must use the -fall option with the idlj compiler to generate both client and server-side bindings. This command line will generate the default server-side bindings, which assumes the POA Inheritance server-side model. For more information on the idlj options, see the man page for idlj (Solaris, Linux, or Mac OS X or Windows).
The idlj compiler generates a number of files. The actual number of files generated depends on the options selected when the IDL file is compiled. The generated files provide standard functionality, so you can ignore them until it is time to deploy and run your program. The files generated by the idlj compiler for Hello.idl, with the -fall command line option, are:
This abstract class is the stream-based server skeleton, providing basic CORBA functionality for the server. It extends org.omg.PortableServer.Serva nt , and implements the InvokeHandler interface and the HelloOperations interface. The server class HelloImpl extends HelloPOA.
This class is the client stub, providing CORBA functionality for the client. It extends org.omg.CORBA.portable.ObjectImpl and implements the Hello.java interface.
This interface contains the Java version of our IDL interface. The Hello.java interface extends org.omg.CORBA.Object, providing standard CORBA object functionality. It also extends the HelloOperations interface and org.omg.CORBA.portable.IDLEntity.
This class provides auxiliary functionality, notably the narrow() method required to cast CORBA object references to their proper types.The Helper class is responsible for reading and writing the data type to CORBA streams, and inserting and extracting the data type from Anys. The Holder class delegates to the methods in the Helper class for reading and writing.
This final class holds a public instance member of type Hello. Whenever the IDL type is an out or an inout parameter, the Holder class is used. It provides operations for org.omg.CORBA.portable.OutputStream and org.omg.CORBA.portable.InputStream arguments, which CORBA allows, but which do not map easily to Java's semantics. The Holder class delegates to the methods in the Helper class for reading and writing. It implements org.omg.CORBA.portable.Streamable.
This interface contains the methods sayHello() and shutdown(). The IDL-to-Java mapping puts all of the operations defined on the IDL interface into this file, which is shared by both the stubs and skeletons.
javac *.java HelloApp/*.java
To start orbd from a Solaris, Linux, or Mac OS X command shell, enter:
orbd -ORBInitialPort 1050&
From an MS-DOS system prompt (Windows), enter:
start orbd -ORBInitialPort 1050
Note that 1050 is the port on which you want the name server to run. The -ORBInitialPort argument is a required command-line argument. Note that when using Solaris software, you must become root to start a process on a port under 1024. For this reason, we recommend that you use a port number greater than or equal to 1024.
For an example of how to run this program on two machines, see Running the Hello World Program on 2 machines.
To start the Hello server from a Solaris, Linux, or Mac OS X command shell, enter:
java HelloServer -ORBInitialPort 1050 -ORBInitialHost localhost&
From an MS-DOS system prompt (Windows), enter:
start java HelloServer -ORBInitialPort 1050 -ORBInitialHost localhost
You will see HelloServer ready and waiting... when the server is started.
For this example, you can omit -ORBInitialHost localhost since the name server is running on the same host as the Hello server. If the name server is running on a different host, use -ORBInitialHost nameserverhost to specify the host on which the IDL name server is running.
Specify the name server (orbd) port as done in the previous step, for example, -ORBInitialPort 1050.
java HelloClient -ORBInitialPort 1050 -ORBInitialHost localhost
When the client is running, you will see a response such as the
following on your terminal: Obtained a handle on server
object: IOR: (binary code) Hello World! HelloServer
exiting...
For this example, you can omit -ORBInitialHost localhost since the name server is running on the same host as the Hello client. If the name server is running on a different host, use -ORBInitialHost nameserverhost to specify the host on which the IDL name server is running.
Specify the name server (orbd) port as done in the previous step, for example, -ORBInitialPort 1050.
When you have finished this tutorial, be sure to shut down or kill the name server (orbd). To do this from a DOS prompt, select the window that is running the server and enter Ctrl+C to shut it down. To do this from a shell on Solaris, Linux, or Mac OS X, find the process, and kill it. The server will continue to wait for invocations until it is explicitly stopped.
Running the Hello World Application on Two Machines describes one way of distributing the simple application across two machines - a client and a server.


Cancer
Cancer : (June 22 – July 22)
It will be a good day. Your work will be appreciated. And your hopes and expectations will get fulfilled.  You will make even the difficult task look simple and will get success too. You can receive honour from the government too. You can also plan to take a short trip with family.


CKP can only keep your password file open in-memory for a very brief
time, typically about 10 seconds after you close the popup. This can be frustrating if you have a long
password and you need to access several websites.
Check the box above to enable disk-caching. With this
option enabled, an unlocked database is encrypted and stored locally so that
you don't have to re-type your password for each website. The cache expires
automatically after about 40 minutes.


<list id="userTaskList" name="My Tasks" model="com.centurylink.mdw.taskmgr.ui.tasks.list.UserTasks" filter="userTasksFilter" controller="com.centurylink.mdw.taskmgr.ui.tasks.list.TaskListActionController" defaultSortColumn="Task ID" displayRows="20"> <column name="" attribute="selected" checkbox="true" /> <column name="Task ID" attribute="instanceId" linkAction="taskDetail" /> <column name="Category" attribute="categoryCode" /> ... </list>This snippet shows how to spell out the configuration for a sortable list using the framework. The id attribute of the list element is simply a unique identifier referenced in the ListManager getter for the list. The name attribute defines the display name for the list. The model attribute points to a Java class which must implement a retrieveItems method to populate the list with a collection of ListItem model objects (which typically wrap an object defined in our data model). The controller points to a class which implements the ListActionController interface and governs how the list responds to events such as when a link is clicked inside a row. Other attributes perform functions that are relatively self-explanatory. Within the list are a number of column elements which specify data fields that are to be displayed as column values in the list. Columns can be added, removed and rearranged dynamically as long as the appropriate getter method is defined in your model implementation. The "My Tasks" list in this example is used in the myTasks.xhtml facelet file as follows:
<ui:define name="list"> <q:list id="myTasksList" listId="myTasks" listEntity="#{listManager.myTasks}" label="My Tasks (#{authenticatedUser.cuid})" /> </ui:define>
The glue that ties together the mdw-hub-view.xml list definition with the facelet file is the expression language syntax: #{listManager.myTasks}. The method getMyTasks() in ListManager.java returns the list constructed according to the "userTaskList" in TaskView.xml. The myTasks.xhtml facelets file also includes a filter to narrow the contents displayed in the list, as well as a taskAction component which enables actions to be performed on list items. The layout of these components is governed by the filteredList.xhtml template specified at the top of myTasks.xhtml.
The individual pages (as defined in facelets files such as myTasks.xhtml) are displayed in a tabbed arrangement controlled by the
main layout file (typically main.xhtml). This file includes a number of
In general many of the components and much of the behavior of Task Manager are inherited from the framework but may be overridden.
However, some files are purposely duplicated for each project instance.
These files include the top-level facelet files as well as the stylesheets, menus and layout files.
Individual Task Manager implementations may customize these files to easily control the look-and-feel of the application.
If you are developing in the Eclipse IDE and you have performed the JSF/Facelets support setup steps outlined in the
MDW Startup Guide,
you should be able to get autocomplete and syntax help when editing facelets files.
The syntax help provides documentation for the components available for building your facelets.
The autocomplete suggests component names as well as managed beans to be used in your expression language constructs.
These functions are available for CenturyLink-developed components as well as the baseline JSF components built in to the implementation.
TODO: Task Forwarding
TODO:


Reports comparisons with None
. That type of comparisons
should always be done with is
or is not
, never
the equality operators.
Example:
a = 2
if a == None:
print("Success")
Once the quick-fix is applied, the code changes to:
a = 2
if a is None:
print("Success")


{"action": "approve", orderId: 1234}
This is an example of queues in Kidozen.
Kidozen handles pushing messages to arbitraries queues with a simple HTTP POST to the application url as:
/queue/local/queueName
or to another application queue as:
/queue/anotherApplication/queueName
The method of the request should be a POST, the content type should be "application/json" and the body should have the message to post to the queue.
Consuming the Queue is not something that you will normally do in a mobile application. However you can do this by simple using HTTP DELETE request.
As an example you can consume a queue from ruby as follows:
require 'net/http' require 'uri' uri = URI.parse('//localhost:5000/queue/local/tasks/next') begin while true puts "waiting for a message..." http = Net::HTTP.new(uri.host, uri.port) response = http.request(Net::HTTP::Delete.new(uri.request_uri)) puts response.body end rescue Exception=>e end


TCBL login uses the OpenID Connect technology for Single Sign On to access participating TCBL Services.
When you navigate between TCBL services, your TCBL Single Sign On account is recognized and as far as you agree, the profile information you added to it is passed on.
You have full control over your profile information and how it is used by other services.
If you have a TCBL Single Sign On account, you may want to login now. If you don't, this is a good time to sign up.


Enter a number between 0 to 9999 to get started
| You entered | Bulls | Cows |
|---|---|---|
| {{t.num}} | {{t.bulls}} | {{t.cows}} |
Total tries: {{bc.tries.length}}
- The computer selects a random number between 1 and 9999. Your aim is to guess that number in the least number of steps.
- Enter a number between and including 1 and 9999.
- The computer verifies the number and displays the result in terms of bulls and cows.
- A Bull indicates that the digit in your number and the computer's number are in the correct position.
- A Cow indicates that the digit is present in the number, but is not in the right position.
Examples:
Computer's number is 2347.
You enter 1267.
The digits 2 and 7 are present in the both the numbers. 7 is in the exact position. So, it is a bull. 2 is not in the same position... so it is a cow.
Computer's number is 5368.
You enter 2358.
3, 8 are in the same position - 2 bulls.
5 is in a different position - 1 cow.
Computer's number is 2268.
You enter 1328.
8 is in the same position - 1 bull.
2 is in a different position - 1 cow.
You enter 2328.
2 (1st position) and 8 - 2 bulls.
2 (3rd position) - 1 cow.
Computer's number - 0023.
You enter 123.
3 bulls and 0 cows.
You enter 230.
1 bull and 3 cows.
Computer's number is 2347.
You enter 1267.
The digits 2 and 7 are present in the both the numbers. 7 is in the exact position. So, it is a bull. 2 is not in the same position... so it is a cow.
Computer's number is 5368.
You enter 2358.
3, 8 are in the same position - 2 bulls.
5 is in a different position - 1 cow.
Computer's number is 2268.
You enter 1328.
8 is in the same position - 1 bull.
2 is in a different position - 1 cow.
You enter 2328.
2 (1st position) and 8 - 2 bulls.
2 (3rd position) - 1 cow.
Computer's number - 0023.
You enter 123.
3 bulls and 0 cows.
You enter 230.
1 bull and 3 cows.


Home
Back
Welcome back, {{ fullname }}!
You have {{numofappts}} Appointments
{{profilebutton}}
Shop Name: {{ shop }}
" {{aboutMe}} "
0 stars
{{rating}}
{{ photo }}
GroomR : {{fullName}} ({{typeofprof}})
Phone:{{phone}}
Email: {{email}}
{{ favButton }}
Address: {{address}}
{{ hours }} {{certified}} {{ appt }} {{ rateme }}
{{ services }}
{{ reviews }}


*** User 2017-05-03 15:08:57.669 ***
15:08:57.669 [info] Disabling blocking sync...
*** User 2017-05-03 15:08:57.673 ***
15:08:57.672 [info] Configured peer_service_manager partisan_default_peer_service_manager on node 'node-1@antoine-PC'
*** User 2017-05-03 15:08:59.000 ***
15:08:59.000 [info] Enabling membership...
*** User 2017-05-03 15:08:59.001 ***
15:08:59.001 [info] Disabling blocking sync...
*** User 2017-05-03 15:08:59.004 ***
15:08:59.004 [info] Configured peer_service_manager partisan_default_peer_service_manager on node 'node-2@antoine-PC'
*** User 2017-05-03 15:09:00.333 ***
15:09:00.333 [info] Enabling membership...
*** User 2017-05-03 15:09:00.334 ***
15:09:00.334 [info] Disabling blocking sync...
*** User 2017-05-03 15:09:00.337 ***
15:09:00.337 [info] Configured peer_service_manager partisan_default_peer_service_manager on node 'node-3@antoine-PC'
*** User 2017-05-03 15:09:00.501 ***
Joining node: 'node-3@antoine-PC' to 'runner@antoine-PC' at port 40644
*** User 2017-05-03 15:09:00.501 ***
Joining issued: 'node-3@antoine-PC' to 'runner@antoine-PC' at port 40644
*** User 2017-05-03 15:09:00.501 ***
Joining node: 'node-2@antoine-PC' to 'runner@antoine-PC' at port 53882
*** User 2017-05-03 15:09:00.501 ***
Joining issued: 'node-2@antoine-PC' to 'runner@antoine-PC' at port 53882
*** User 2017-05-03 15:09:00.502 ***
Joining node: 'node-1@antoine-PC' to 'runner@antoine-PC' at port 37626
*** User 2017-05-03 15:09:00.502 ***
Joining issued: 'node-1@antoine-PC' to 'runner@antoine-PC' at port 37626
*** User 2017-05-03 15:09:00.563 ***
Waiting for join to complete with manager: partisan_default_peer_service_manager
*** User 2017-05-03 15:09:00.563 ***
Finished.
*** CT 2017-05-03 15:09:00.563 *** COVER INFO
Adding nodes to cover test: ['runner@antoine-PC']
*** CT 2017-05-03 15:09:00.568 *** COVER INFO
Successfully added nodes to cover test: []
*** User 2017-05-03 15:09:04.578 ***
Case finished: ivar_test
*** User 2017-05-03 15:09:11.616 ***
15:09:11.616 [info] Application lasp exited with reason: stopped
*** User 2017-05-03 15:09:11.617 ***
15:09:11.617 [info] Application partisan exited with reason: stopped
=== Ended at 2017-05-03 15:09:11
=== successfully completed test case
=== Returned value: ok
Test run history
| Top level test index


your friendly neighbourhood baseball expert.
Communikey is an Android application i developed during the summer of 2014. I worked with One Tinybit LLC to create this application the following services were included in making Communikey:


--- layout: post title: Look What Arrived For Me Today date: 2010-03-10 19:01:54.000000000 +00:00 tags: - barefoot - shoes - Terra Plana - Evo type: post published: true ---
Look what I got today (thank-you Canoe Inc). Come on everyone, I want to hear you say "Ooooooo". I've not taken them for a spin yet, but initial impressions are good. I'll write up a full review once I've had a chance to take them out for a nice long run.


 We do this by using cutting edge, predictive Artifical Intelligence (A.I.) technologies to help abalone fishermen determine wether or not their catch meets the age requiremnts for capture.
The white abalone snail has been overfished to the verge of extinction. However, by using Machine Learning, we hope to save the species by helping fishermen determine the correct age to return them back into the wild.
The white abalone (Haliotis sorenseni) was once common in kelp forests off the coast of Southern California and Mexico, and has been harvested by humans for around 10,000 years.
It plays an important role in the kelp forest ecosystem, competing with other algal grazers such as sea urchins and keeping their numbers under control.


Skyrocket
your Old Toolchain
Into the Future!
Eindhoven Developers Meetup
new Date(2017, 1, 22, 20, 15, 0);
On the menu today
- Toolchains: The Old versus The New
- What we wanted to solve
- Steps we took
- Where we are now
What is the "old" toolchain?
- Backend-first
- Grunt / Gulp
- LESS / SASS by Grunt / Gulp
- AMD (Require.js) or Concatenation
- jQuery like approach
Getting assets
- Get JavaScript from script tags
- Get Stylesheets from link tags
- Get images from img tags
- Require JavaScript files through injection
What is the "new" toolchain?
- Single Page Applications
- Backend is API
- ES6+
- NPM scripts for tasks
- webpack for bundling entry points
- JavaScript as a starting point
Getting assets
- Get JavaScript from script tags
- Webpack tells to include style
- Webpack loads images
- Require JavaScript files through webpack chunks
Why going forward is hard
- Don't know where to start
- Moving over (forgotten) paradigms
- Backend is not supported yet
- You have to figure out everything
- You have a lot of code to manage
Why starting from scratch is easier
- Clean slate
- Freedom
- No legacy
- You can try out everything
- You can adjust your backend to it
- Project is most likely smaller
How the "old" way stinks
- Gets messy really quick
- AMD (Require.js) has better alternatives
- Dependency management is unclear
- Pipeline can be confusing
- Support is getting worse
What we needed to solve at JouwWeb
New
- Managealbe code base
- ES6+
- ES7 modules + chunks
- Source maps for development
What we needed to solve at JouwWeb
Keep
- Make sure old libs keep working
- Adjust as little as possible
- AMD should work too
- Development "watch" mode
- Production output using webpack
- File size
"Don't pounce on every chance to rewrite the world. Refactor little bits as you go. Make it work, first. Then make it right."
- Eric Elliott
Know problems
- What are entry points?
- Source was copied from a weird folder structure
- Backend injects script tags
- Dynamic requires in our code
- We required 3th party libs using
require('lib/jquery');
- Some dependencies couldn't be bundled
- Files copied from
node_modules
using grunt
Set deliverables
Try to ship as little as possible
Steps we took
- Organize code in structure webpack will understand
- Have all our entry points work with webpack
- Introduce Babel
- Solve
require('lib/jquery');
problem
- Solve dynamic requires
- Let JavaScript handle injected scripts
- Fix broken "old" libraries
- Have a development "watch" environment
Steps we didn't take
- LESS was still part of the "old"
- Fix our folder structure
- Handle copying of assets
- Make it blazing fast
Basics
We created a JavaScript file...
Execute in NPM
// package.json
{
...
"scripts": {
"build": "node ./tasks/webpack"
}
}
// cli
> npm run build
Organising the structure
module/Text/assets/js/plugin/text.js
module/Video/assets/js/plugin/video.js
require('plugin/text.js');
require('plugin/video.js');
Organising the structure
module/*/assets/js/**/*.js
copy to
public/assets/js/**/*.js
Make public/assets/js
a "module root" in webpack
require('filename.js');
const config = {
...
resolve: {
modules: [
'public/assets/js',
'node_modules',
'bower_components',
],
},
};
How we made "watch" work
webpack watches
public/assets/js/**/*.js
We watch for changes in
module/*/assets/js/**/*.js
Copy all to
public/assets/js/**/*.js
webpack reruns
It's not elegant, but effective
Entry points
const config = {
...
entry: {
'js/initialize': './js/app/initialize',
},
output: {
path: 'public/assets/',
filename: '[name].js',
}
}
// 'public/assets/' + 'js/initialize' + '.js'
// lib/bootstrap.js (AMD style)
define(
['bootstrap/dist/js/bootstrap'],
function (bootstrap) => { return bootstrap }
);
// lib/bxslider.js (CommonJS style)
module.exports = require('bxslider-4/dist/jquery.bxslider');
Dynamic module includes
define(['scripts/backend'], function(module) { ... });
function includeModule(name) {
define([name], function(module) { ... });
}
// somewhere else
includeModule('scripts/backend');
function includeModule(name) {
function cb(module) { ... }
switch (name) {
case 'scripts/backend':
require(['scripts/backend'], cb);
break;
case 'scripts/editor':
require(['scripts/editor'], cb);
break;
}
}
Injected scripts
What if the backend generates <script />
tags?
<script src="assets/js/module-a.js" />
<script src="assets/js/module-b.js" />
<script>
window.scripts = ['module-a', 'module-b'];
</script>
// in JavaScript
window.scripts.forEach(includeModule);
Old dependencies
- Fixed them by hand
- Not really important
- tinymce is a totally different story
What we did later
- Fixed our folder structure
- Got LESS (and other assets) to webpack
- Hot Reloading with webpack dev server
- Able to refactor a lot
- SUPER FAST!
Where we want to be
- Single Page Application
- Mostly built on React
- Dynamic route loading
- Drinking beer on a sunny island
Improve your project,
just do it
one little step
at the time.
- Gaya Kessler
Thanks!
For more brain farts check @GayaNinja
(p.s. we're always looking for people, so come chat)


| Version | Changes | Production Release Date |
|---|---|---|
| 208 | Update connection details | 04 May 2017 |
| 103 | Add section on compatabililty to documentation. | 15 December 2012 |
| 98 | Increase maximum inbound message size to 8192 bytes. | 29 September 2012 |
LMAX reserves the right to change the specification of the FIX interface.
LMAX operates FIX Market Data Gateways which allow users to receive Market Data using standard FIX 4.4 messages.
LMAX operates both Production and Test environments which can be connected to using FIX using the following connection parameters.
| Environment | DNS Address | Port number | LMAX CompId | Client CompId |
|---|---|---|---|---|
| Production | fix-md.lmaxtrader.com | 443 | LMXBLM | <client production username> |
| Test | fix-marketdata.london-demo.lmax.com | 443 | LMXBDM | <client test username> |
All LMAX environments operate to the following schedules.
LMAX order books are open for trading in the following trading sessions.
| Monday | Tuesday | Wednesday | Thursday | Friday | |
|---|---|---|---|---|---|
| Trading Opens | 17:05 Sunday America/New York | 17:05 Monday America/New York | 17:05 Tuesday America/New York | 17:05 Wednesday America/New York | 17:05 Thursday America/New York |
| Trading Closes | 17:00 Monday America/New York | 17:00 Tuesday America/New York | 17:00 Wednesday America/New York | 17:00 Thursday America/New York | 17:00 Friday America/New York |
FIX sessions connected to the LMAX FIX Market Data Gateways operate to the following schedule.
| Open for connection | 17:03:00 America/New York |
|---|---|
| Connection closed | 17:02:30 America/New York |
The LMAX FIX Trading Gateways have a maximum inbound message limit of 8192 bytes. The a message is received which exceeds this size, the client will be logged off.
The LMAX FIX Trading Gateway will never publish messages greater than 8192 bytes.
The LMAX FIX Market Data Gateways do not support any FIX message recovery.
In the event of the LMAX FIX Market Data Gateway requesting a message re-send, the resent messages will be ignored.
To reset a FIX Session the client must login with the tag 141 (ResetSeqNumFlag) set to 'Y'.
LMAX aims to maximise compatibility by using standard FIX messages, tags and usage conventions wherever possible.
Periodically, LMAX updates it's FIX specifications in response to changes to the core trading application. Usually these changes are to support additional features and wherever possible this will be achieved through the use of additional messages, tags in existing messages or tag values in existing tags. In order to minimise the impact of these sort of changes, LMAX recommends that the client application accepts messages with unrecognised tags and ignores those tags which it cannot interpret.
LMAX will all endeavor to contact clients prior to change to the FIX API, particularly in the case where a change is breaking (i.e. not additive in nature).
LMAX supports the following FIX message types.
| Type | Name | Description |
|---|---|---|
| 0 | Heartbeat | Message sent during quite intervals on the connection to ensure that connection is still alive. |
| 1 | TestRequest | Message used to request a HeartBeat from the counterparty to allow round trip testing of the connection. |
| 2 | ResendRequest | Message used to request a replay of messages from the counter party. |
| 3 | Reject | Sent in response to a message which is structurally invalid (i.e. invalid or missing tag or ill-formed tag-value). |
| 4 | SequenceReset | SequenceReset. |
| 5 | Logout | Message used to terminate a FIX connection. Can be sent by the client or the LMAX FIX Gateway. |
| A | Logon | Message used to establish a connection between a client and the LMAX FIX Gateway. |
| V | MarketDataRequest | Message sent by the client to request market data. |
| W | MarketDataSnapshotFullRefresh | Message sent by LMAX containing changes in market data |
| Y | MarketDataRequestReject | Message sent in response to an invalid Market Data Request. |
| Tag | Tag Name | Description | Required | Data Type |
|---|---|---|---|---|
| 8 | BeginString | The FIX version number identifier. Always 'FIX.4.4' | Y | String |
| 9 | BodyLength | Length of the FIX Message. | Y | Length |
| 35 | MsgType | The type of the message. | Y | String |
| 49 | SenderCompID | Identifier for the sender of the message. | Y | String |
| 56 | TargetCompID | Identifier for the receiver of the message. | Y | String |
| 34 | MsgSeqNum | The unique sequence number for the message within current FIX session. | Y | SeqNum |
| 43 | PossDupFlag | Always required for retransmitted messages, whether prompted by the sending system or as the result of a resend request. Set to 'Y' if this is a resent message. | N | Boolean |
| 97 | PossResend | Never used by LMAX. | N | Boolean |
| 52 | SendingTime | Time message was sent. | Y | UTCTimestamp |
| 122 | OrigSendingTime | Timestamp when message was originally sent. Required for message resent as a result of a ResendRequest. | N | UTCTimestamp |
| Tag | Tag Name | Description | Required | Data Type |
|---|---|---|---|---|
| 10 | CheckSum | Checksum for message contents. | Y | String |
| Tag | Tag Name | Description | Required | Data Type |
|---|---|---|---|---|
| 48 | SecurityID | Must contain the LMAX orderbook id. | Y | String |
| 22 | SecurityIDSource | Must contain the value '8' (Exchange Symbol) | Y | String |
| Tag | Tag Name | Description | Required | Data Type |
|---|---|---|---|---|
| 146 | NoRelatedSym | Specifies the number of repeating symbols specified. | Y | NumInGroup |
| Instrument | Y |
| Tag | Tag Name | Description | Required | Data Type |
|---|---|---|---|---|
| 267 | NoMDEntryTypes | Number of MDEntryType (269) fields requested. | Y | NumInGroup |
| 269 | MDEntryType | Type Market Data entry. LMAX supported values: 0 = Bid 1 = Offer LMAX only allows subscription to both bid and ask at the same time. If only 0 or 1 is specified individually for a Market Data Request, then the request will be rejected. | Y | char |
| Tag | Tag Name | Description | Required | Data Type |
|---|---|---|---|---|
| 268 | NoMDEntries | Number of entries in Market Data message. | Y | NumInGroup |
| 269 | MDEntryType | Type Market Data entry. LMAX supported values: 0 = Bid 1 = Offer | Y | char |
| 270 | MDEntryPx | Price of the Market Data Entry. | N | Price |
| 271 | MDEntrySize | Quantity or volume represented by the Market Data Entry. | N | Qty |
| 272 | MDEntryDate | Date of Market Data Entry. This tag will only be present on the first entry in the repeating group | N | UTCDateOnly |
| 273 | MDEntryTime | Time of Market Data Entry. This tag will only be present on the first entry in the repeating group | N | UTCTimeOnly |
| Tag | Tag Name | Description | Required | Data Type |
|---|---|---|---|---|
| StandardHeader | Y | MsgType= 0 | ||
| 112 | TestReqID | Required when the heartbeat is the result of a Test Request message. | N | String |
| StandardTrailer | Y |
| Tag | Tag Name | Description | Required | Data Type |
|---|---|---|---|---|
| StandardHeader | Y | MsgType= 1 | ||
| 112 | TestReqID | Identifier included in Test Request message to be returned in resulting Heartbeat | Y | String |
| StandardTrailer | Y |
| Tag | Tag Name | Description | Required | Data Type |
|---|---|---|---|---|
| StandardHeader | Y | MsgType= 2 | ||
| 7 | BeginSeqNo | Message sequence number of first message in range to be resent | Y | SeqNum |
| 16 | EndSeqNo | Message sequence number of last message in range to be resent. If request is for a single message BeginSeqNo (7) = EndSeqNo. If request is for all messages subsequent to a particular message, EndSeqNo = “0” (representing infinity). | Y | SeqNum |
| StandardTrailer | Y |
| Tag | Tag Name | Description | Required | Data Type |
|---|---|---|---|---|
| StandardHeader | Y | MsgType= 3 | ||
| 45 | RefSeqNum | MsgSeqNum of rejected message | Y | SeqNum |
| 371 | RefTagID | The tag number of the FIX field being referenced. | N | int |
| 372 | RefMsgType | The MsgType of the FIX message being referenced. | N | String |
| 373 | SessionRejectReason | Code to identify reason for a session-level Reject message. | N | int |
| 58 | Text | Where possible, message to explain reason for rejection | N | String |
| StandardTrailer | Y |
| Tag | Tag Name | Description | Required | Data Type |
|---|---|---|---|---|
| StandardHeader | Y | MsgType= 4 | ||
| 123 | GapFillFlag | Indicates that the Sequence Reset message is replacing administrative or application messages which will not be resent. Valid values: Y = Gap Fill message, MsgSeqNum field valid N = Sequence Reset, ignore MsgSeqNum | N | Boolean |
| 36 | NewSeqNo | New sequence number | Y | SeqNum |
| StandardTrailer | Y |
| Tag | Tag Name | Description | Required | Data Type |
|---|---|---|---|---|
| StandardHeader | Y | MsgType= 5 | ||
| 58 | Text | If LMAX logs out a client this may contain a text description for the reason for the logout. | N | String |
| StandardTrailer | Y |
| Tag | Tag Name | Description | Required | Data Type |
|---|---|---|---|---|
| StandardHeader | Y | MsgType= A | ||
| 98 | EncryptMethod | Always '0' - None | Y | int |
| 108 | HeartBtInt | The maximum time to wait before a Heartbeat message is sent in the absence of other activity on the connection. The same value is used by both parties. | Y | int |
| 141 | ResetSeqNumFlag | Indicates both sides of a FIX session should reset sequence numbers | N | Boolean |
| 383 | MaxMessageSize | Maximum number of bytes supported for a single message. | N | Length |
| 553 | Username | LMAX username. This is required on the login message sent by the client | N | String |
| 554 | Password | LMAX Password or passphrase. This is required on the login message sent by the client | N | String |
| StandardTrailer | Y |
| Tag | Tag Name | Description | Required | Data Type |
|---|---|---|---|---|
| StandardHeader | Y | MsgType= V | ||
| 262 | MDReqID | Must be unique, or the ID of previous Market Data Request to disable if SubscriptionRequestType = Disable previous Snapshot + Updates Request (2). | Y | String |
| 263 | SubscriptionRequestType | SubcriptionRequestType indicates to the other party what type of response is expected. LMAX supported values: 1 - Snapshot + Updates (Subscribe) 2 - Disable previous Snapshot + Updates Request (Unsubscribe) LMAX does not support 0 - Snapshot | Y | char |
| 264 | MarketDepth | Depth of market for Book Snapshot LMAX supported values: 0 = Full Depth (LMAX supports a maximum of 20 levels of depth) 1 = Top of Book 2-20 = Report best N price tiers of data, up to 20 levels. | Y | int |
| 265 | MDUpdateType | Required if SubscriptionRequestType = Snapshot + Updates (1). LMAX supported values 0 - Full Refresh. | N | int |
| MDReqGrp | Y | |||
| InstrmtMDReqGrp | Y | |||
| StandardTrailer | Y |
| Tag | Tag Name | Description | Required | Data Type |
|---|---|---|---|---|
| StandardHeader | Y | MsgType= W | ||
| 262 | MDReqID | Conditionally required if this message is in response to a Market Data Request. | N | String |
| Instrument | Y | |||
| MDFullGrp | Y | |||
| StandardTrailer | Y |
| Tag | Tag Name | Description | Required | Data Type |
|---|---|---|---|---|
| StandardHeader | Y | MsgType= Y | ||
| 262 | MDReqID | Must refer to the MDReqID of the request. | Y | String |
| 281 | MDReqRejReason | Reason for the rejection of a Market Data request. LMAX supported values: 0 = Unknown symbol 1 = Duplicate MDReqID 4 = Unsupported SubscriptionRequestType 5 = Unsupported MarketDepth 6 = Unsupported MDUpdateType 8 = Unsupported MDEntryType | N | char |
| 58 | Text | Free format text string (Note: this field does not have a specified maximum length) | N | String |
| StandardTrailer | Y |
| Tag | Tag Name | Type | Description |
|---|---|---|---|
| 1 | Account | String | Account mnemonic as agreed between buy and sell sides, e.g. broker and institution or investor/intermediary and fund manager. |
| 6 | AvgPx | Price | Not supported by LMAX - always 0 |
| 7 | BeginSeqNo | SeqNum | Message sequence number of first message in range to be resent |
| 8 | BeginString | String | Identifies beginning of new message and protocol version. ALWAYS FIRST FIELD IN MESSAGE. (Always unencrypted). Valid values: * FIX.4.4 |
| 9 | BodyLength | Length | Message length, in bytes, forward to the CheckSum field. ALWAYS SECOND FIELD IN MESSAGE. (Always unencrypted) |
| 10 | CheckSum | String | Three byte, simple checksum (see Volume 2: “Checksum Calculation” for description). ALWAYS LAST FIELD IN MESSAGE; i.e. serves, with the trailing <SOH>, as the end-of-message delimiter. Always defined as three characters. (Always unencrypted) |
| 16 | EndSeqNo | SeqNum | Message sequence number of last message in range to be resent. If request is for a single message BeginSeqNo (7) = EndSeqNo. If request is for all messages subsequent to a particular message, EndSeqNo = “0” (representing infinity). |
| 22 | SecurityIDSource | String | Identifies class or source of the SecurityID (48) value. Required if SecurityID is specified. LMAX Supported values are: 8 = Exchange Symbol |
| 34 | MsgSeqNum | SeqNum | Integer message sequence number. |
| 35 | MsgType | String | Defines message type ALWAYS THIRD FIELD IN MESSAGE. (Always unencrypted) Valid values: *** Note the use of lower case letters *** 0 = Heartbeat 1 = Test Request 2 = Resend Request 3 = Reject 4 = Sequence Reset 5 = Logout A = Logon V = Market Data Request W = Market Data-Snapshot/Full Refresh Y = Market Data Request Reject |
| 36 | NewSeqNo | SeqNum | New sequence number |
| 43 | PossDupFlag | Boolean | Indicates possible retransmission of message with this sequence number Valid values: Y = Possible duplicate N = Original transmission |
| 45 | RefSeqNum | SeqNum | Reference message sequence number |
| 48 | SecurityID | String | LMAX Security identifier. Requires SecurityIDSource=8. |
| 49 | SenderCompID | String | Assigned value used to identify firm sending message. |
| 52 | SendingTime | UTCTimestamp | Time of message transmission (always expressed in UTC (Universal Time Coordinated, also known as “GMT”) |
| 56 | TargetCompID | String | Assigned value used to identify receiving firm. |
| 58 | Text | String | Free format text string (Note: this field does not have a specified maximum length) |
| 89 | Signature | data | Electronic signature |
| 93 | SignatureLength | Length | Number of bytes in signature field. |
| 95 | RawDataLength | Length | Number of bytes in raw data field. |
| 96 | RawData | data | Unformatted raw data, can include bitmaps, word processor documents, etc. |
| 97 | PossResend | Boolean | Indicates that message may contain information that has been sent under another sequence number. Valid Values: Y=Possible resend N=Original transmission LMAX will never populate this tag with any value other than 'N' on messages sent by LMAX. LMAX will ignore this tag on any messages received by LMAX and the treat the message as having been sent with PossResend='N'. |
| 98 | EncryptMethod | int | Method of encryption. Valid values: 0 = None / other LMAX does not support encryption at the FIX layer. All messages are sent over an SSL encrypted connection. Supported values: |
| 108 | HeartBtInt | int | Heartbeat interval (seconds) |
| 112 | TestReqID | String | Identifier included in Test Request message to be returned in resulting Heartbeat |
| 122 | OrigSendingTime | UTCTimestamp | Original time of message transmission (always expressed in UTC (Universal Time Coordinated, also known as “GMT”) when transmitting orders as the result of a resend request. |
| 123 | GapFillFlag | Boolean | Indicates that the Sequence Reset message is replacing administrative or application messages which will not be resent. Valid values: Y = Gap Fill message, MsgSeqNum field valid N = Sequence Reset, ignore MsgSeqNum |
| 141 | ResetSeqNumFlag | Boolean | Indicates that the both sides of the FIX session should reset sequence numbers. Valid values: Y = Yes, reset sequence numbers N = No |
| 146 | NoRelatedSym | NumInGroup | Specifies the number of repeating symbols specified. |
| 262 | MDReqID | String | Unique identifier for Market Data Request. MDReqId is restricted to a maximum of 16 lowercase hexadecimal characters [0123456789abcdef] with no leading 0 characters (this is a positive 64bit number represented in hexadecimal excluding 0). Must be unique for all current Market Data Requests. If a new Market Data Request (excluding unsubscribtion requests) is received with the same MDReqId as a current Market Data Request then the new request will be rejected as a duplicate. |
| 263 | SubscriptionRequestType | char | Subscription Request Type Valid values: 0 = Snapshot; 1 = Snapshot + Updates (Subscribe); 2 = Disable previous Snapshot + Update Request (Unsubscribe); |
| 264 | MarketDepth | int | Depth of market for Book Snapshot LMAX supported values: 0 = Full Depth (LMAX supports a maximum of 20 levels of depth) 1 = Top of Book 2-20 = Report best N price tiers of data, up to 20 levels. |
| 265 | MDUpdateType | int | Specifies the type of Market Data update. LMAX supported values: 0 = Full Refresh |
| 267 | NoMDEntryTypes | NumInGroup | Number of MDEntryType (269) fields requested. |
| 268 | NoMDEntries | NumInGroup | Number of entries in Market Data message. |
| 269 | MDEntryType | char | Type Market Data entry. LMAX supported values: 0 = Bid 1 = Offer |
| 270 | MDEntryPx | Price | Price of the Market Data Entry. |
| 271 | MDEntrySize | Qty | Quantity or volume represented by the Market Data Entry. |
| 272 | MDEntryDate | UTCDateOnly | Date of Market Data Entry. |
| 273 | MDEntryTime | UTCTimeOnly | Time of Market Data Entry. |
| 281 | MDReqRejReason | char | Reason for the rejection of a Market Data request. Valid values: 0 = Unknown symbol 1 = Duplicate MDReqID 2 = Insufficient Bandwidth 3 = Insufficient Permissions 4 = Unsupported SubscriptionRequestType 5 = Unsupported MarketDepth 6 = Unsupported MDUpdateType 7 = Unsupported AggregatedBook 8 = Unsupported MDEntryType 9 = Unsupported TradingSessionID A = Unsupported Scope B = Unsupported OpenCloseSettleFlag C = Unsupported MDImplicitDelete |
| 354 | EncodedTextLen | Length | Unused by LMAX. Byte length of encoded (non-ASCII characters) EncodedText (355) field. |
| 355 | EncodedText | data | Unused by LMAX. Encoded (non-ASCII characters) representation of the Text (58) field in the encoded format specified via the MessageEncoding (347) field. If used, the ASCII (English) representation should also be specified in the Text field. |
| 371 | RefTagID | int | The tag number of the FIX field being referenced. |
| 372 | RefMsgType | String | The MsgType (35) of the FIX message being referenced. |
| 373 | SessionRejectReason | int | Code to identify reason for a session-level Reject message. Valid values: 0 = Invalid tag number 1 = Required tag missing 2 = Tag not defined for this message type 3 = Undefined Tag 4 = Tag specified without a value 5 = Value is incorrect (out of range) for this tag 6 = Incorrect data format for value 7 = Decryption problem 8 = Signature problem 9 = CompID problem 10 = SendingTime accuracy problem 11 = Invalid MsgType 12 = XML Validation error 13 = Tag appears more than once 14 = Tag specified out of required order 15 = Repeating group fields out of order 16 = Incorrect NumInGroup count for repeating group 17 = Non “data” value includes field delimiter (SOH character) 99 = Other |
| 383 | MaxMessageSize | Length | Maximum number of bytes supported for a single message. |
| 384 | NoMsgTypes | NumInGroup | Number of MsgTypes (35) in repeating group. |
| 385 | MsgDirection | char | Specifies the direction of the messsage. Valid values: S = Send R = Receive |
| 464 | TestMessageIndicator | Boolean | Not supported by LMAX. |
| 553 | Username | String | LMAX username. This is required on the login message sent by the client |
| 554 | Password | String | LMAX Password or passphrase. This is required on the login message sent by the client |
| 789 | NextExpectedMsgSeqNum | SeqNum | Not supported by LMAX. |
| Data Type | Description |
|---|---|
| Boolean | char field containing one of two values: 'Y' = True/Yes 'N' = False/No |
| char | Char value, can include any alphanumeric character or punctuation except the delimiter. All char fields are case sensitive (i.e. l != L). |
| data | Binary (non-ASCII) data. |
| int | Sequence of digits without commas or decimals and optional sign character (ASCII characters - and 0 - 9). The sign character utilizes one byte (i.e. positive int is 99999 while negative int is -99999). Note that int values may contain leading zeros (e.g. 00023 = 23). |
| Length | Representing the length in bytes. Value must be positive. |
| NumInGroup | Value that represents the number of repeating values in a group. |
| Price | Value representing a price. Note the number of decimal places may vary. |
| Qty | Value capable of storing either a whole number (no decimal places) of shares (securities denominated in whole units) or a decimal value containing decimal places for non-share quantity asset classes (securities denominated in fractional units). |
| SeqNum | Representing a message sequence number. Value must be positive. |
| String | Alpha-numeric free format strings; can include any character or punctuation except the delimiter. All char fields are case sensitive (i.e. lmax != LMAX). |
| UTCTimestamp | Representing Time/date combination represented in UTC (Universal Time Coordinated, also known as GMT ) only accepted in this format : YYYYMMDD-HH:MM:SS (whole seconds). For example 20120321-17:15:03. |


MURDER AT 1600 (1997) A Film Review by Ted Prigge Copyright 1997 Ted Prigge
Director: Dwight H. Little Writers: Wayne Beach and David Hodgin Starring: Wesley Snipes, Diane Lane, Daniel Benzali, Alan Alda, Dennis Miller, Ronny Cox, Tate Donovan, Harris Yulin, Norman Fell
"Murder at 1600" deals with the rather "Absolute Power"-esque (a far better film, by the way) problem that the president may have had sex with another woman who wasn't the first lady and then brutally murdered her and shoved her corpse in a bathroom in the White House. Now, I'm sorry, but they have the Secret Service to deal with the corpse, and they wouldn't just toss it in a bathroom. Anyway, the chief suspect is one of the cleaner's of the White House, and the investigator is a cool and inquisitive detective played by the cool Wesley Snipes, and of course buddied by wisecracking ubergod, Dennis Miller, who seems to have written a line or two of his own dialogue.
Snipes is aided in his investigation with not much initial help by a Secret Service chick played by Diane Lane. But the investigation is limited by a creepy White House staffer played by the Daddy Warbucks-looking Daniel Benzali (from "Murder One"). He limits nearly everything, hindering Snipes investigation. Also in on the investigation is another staffer (Alan Alda), the president's horny son (Tate Donovan), and, of course, the President (Ronny Cox), who seems rather ignorant with everything anyway.
Now, this film is not a bad film at all. The plot twists are interesting, though not very shocking since somehow you can feel the twists minutes before. And the film has a totally original albeit unbelievably proposterous finale, including sneaking into the White House (????). And, of course, the acting's good. And the actor chosen to play the big villain is a totally original choice. I like that pick of casting a lot.
But the characters are all cardboard and any kind of character developments are just there for plot reasons. For instance, Diane Lane's characters was a sharpshooter in the Olympics back in the 80s, so you know she's gonna be used to shoot some badguys. And, as most films do, it uses the great comic brilliance of Dennis Miller as just a character who will either be wounded or killed (I won't say which). On his show once, he said the reason his personality shines through each of his film personas is because their so thinly drawn. He's so right. The guy's a genius, give him a good part some day, will ya?
Anyway, the film is pretty fun for a cliched-ridden thriller, and has some really cool plot twists. It's not its absurdity that's wrong with it, but lack of innovation and originality that wounds it. It's not a bad film, but it's nothing special either.
MY RATING (out of 5): **1/2
Homepage at: http://www.geocities.com/Hollywood/Hills/8335/
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews