Developer Update - Removal of parsenow

We've made working with our controls easier for web developers and designers.

Oncord's user interface API for web developers uses a server-side document model.  This is a set of tags (which we call controls) that allow for user interface elements to be constructed rapidly for building forms and other presentation elements.

These controls can depend on each other.  For instance, you might have a table of products which can be filtered by combobox values.  

It becomes complex when the layout of these controls is out of order, or controls depend on each other in a cyclic manner.  For instance, a table depends on a filter of the combobox's value; but the combobox was declared after the table, so it might not have been created or rendered yet.

Previously to solve this problem, we created a system to control the timing of when attribute values would evaluate.  These were parsenow="" and parse="".  These were mysterious and confusing attributes for web developers.  

The old way:

 <forms:editbox value="$expression" parsenow="value" />

The new way:

 <forms:editbox value="[? $expression ?]" />

We've overhauled the entire server document model for Oncord to remove these parsenow and parse attributes.  The new model is consistent with the rest of Oncord's markup, and also provides some performance benefits.

We've written tools to migrate old code, so anything you've developed in the old format will be automatically refactored to the new format within the next week.

Internally it is a major upgrade, with almost every line of code changing slightly in the core software.
We apologise if there were some glitches during deployment over the weekend.  If you experience anything wrong, please Contact Support.