< 0.5 | 0.6 | 0.7 >

• Model 0.5.1
• New Data Types
• Changed Elements
• Changes
• Model 0.5.2
• New Elements
• Changed Elements
• Unified Design
• Changes
• Model 0.5.3
• Changes
• Model 0.6
• Changes

Model 0.5.1

Released May 2010

This adds support for OpenID and RSS feeds. There has also been a lot of metamodel refactoring, to clean up the metamodel. Many issues have been fixed.

New Data Types

iamlOpenID

A URL that is an OpenID URL. This is always valid on the client-side, but only valid on the server-side once the user has authenticated with the given URL. This follows the specifications in OpenID v1.1; for example, it supports delegating URLs.

When rendered as an InputTextField, an "Authenticate" button is provided, which will allow the server to authenticate the user.

Changed Elements

Frame

A Frame can now have different rendering targets. By default, it will generate HTML.

If the rendering target is set to RSS2_0, then the content will be rendered as a RSS 2.0 feed instead. This is achieved by iterating over any DomainIterators in the frame.

EntryGate

An EntryGate can now require a Label to be set (and valid) within the same Scope. For example, if the Label is of type iamlOpenIDURL, then the user must provide and authenticate a valid OpenID URL before the Scope can be accessed.

Changes

1. Meta-model changes
• Refactoring of Domain Modelling elements ( issue 178 )
• DecisionOperation and DecisionCondition merged into DecisionNode ( issue 160 )
• CompositeWire and SingleWire removed ( issue 189 )
• FieldValue properties are now stored in an explicit containment reference ( issue 170 )
2. Code generation
• A new domain modelling runtime framework ( issue 178 ), which improves code generation time significantly
• Various performance and size improvements to code generation
3. Development
• Diagram editors are now completely removed from version control ( issue 175 )
4. Documentation
• The documentation has not been fully migrated yet, nor all of the example models migrated yet, but this will be completed before 0.6.

Model 0.5.2

Released July 2010

This minor release adds autocomplete wires, and refreshes the rendering of elements in the diagram editors. There is also a small amount of metamodel refactoring, along with other issue fixes.

New Elements

Autocomplete Wire

An Autocomplete Wire allows for the easy creation of an autocompletion visual element.

Changed Elements

Visible Thing

All VisibleThings now support an additional property, rather than just InputTextFields: currentInput. If supported at runtime, this represents input that the user has provided but before it has been committed.

It also adds the Event onInput, which is fired whenever the currentInput has changed. Not all model elements support onInput and it is not guaranteed to fire consistently.

Action Edge

To unify better with the desired ECA style, Actions have been renamed to ActionEdges.

The differences between RunAction and NavigateAction have been removed, and the two elements have been unified into ActionEdge.

Unified Design

The style and design of model elements has been refreshed, and unified according to the Physics of Notation by Moody ( issue 195 ). The wide range of colours that were in use before have been unified down into seven; full details on this change will be in the thesis.

Changes

1. Meta-model changes
• DomainIterators and InputForm no longer have fieldValues created through model completion.
• The javascriptAlert PrimitiveOperation has been renamed to alert ( issue 196 )
2. Code generation
• Duplicate extensions are now found and provided as warnings when developing templates ( issue 182 )
3. Interface
• The diagram elements icons have been refreshed ( issue 18 )
• A new tool to generate new element IDs has been added; for example, an InputTextField with an ID of model.1a9b9019af.153 may be renamed to text1 ( issue 86 )
4. Documentation
• The element export script now also exports to SVG, as well as PNG ( issue 193 )
• The documentation has not been fully migrated yet, nor all of the example models migrated yet, but this will be completed before 0.6.

Model 0.5.3

Released January 2011

This release is mostly bug fixes and other small changes. The metamodel may be changing significantly in the next release (as the thesis requires) so this is an interim release before these changes proceed. Many improvements have been completed.

There has also been some performance improvements, such as reducing the size of generated models, improving Drools rule performance and improvements to Modeldoc.

Changes

1. Documentation
• Wrote up a list of sample representations of user interface elements in InterfaceElements

Model 0.6

Released September 2011

This is a major release that represents the final version of the IAML modelling environment, as documented in the corresponding Thesis to the project. A lot of the metamodel changes are described by  issue 234 , and includes many issue fixes summarised below.

Changes

1. Meta-model changes
1. New elements
• The underlying model of the language has been refactored to support first-order logic concepts. This includes the model elements of Functions, Predicates, BooleanProperties, BuiltinProperties and ComplexTerms ( issue 244 ,  issue 245 ,  issue 247 ).
• XQuery functions and predicates are now supported through XQueryFunctions and XQueryPredicates ( issue 246 ).
• The underlying metamodel for domain modelling has been changed to reuse the Ecore metamodel through EMF ( issue 242 ).
• The logic behind the "set" BuiltinOperation has been moved to a new model element within activity modelling, SetNode.
2. Changed elements
• The Arithmetic model element is now deprecated, and should be replaced with a XQueryFunction (issue 220).
• The Property element has been renamed to Value. StaticValues are now merged with Values ( issue 179 ).
• The Hidden visual element has been merged into hidden Labels ( issue 224 ).
• The EntryGate and ExitGate elements have been merged into a single Gate element ( issue 254 ).
• DomainIterators now contain a single DomainInstance ( issue 241 ).
• A DomainIterator now has a new value, 'current pointer' ( issue 219 ).
• A VisibleThing now has a new value, 'visible' ( issue 223 ).
3. Renamed elements
• DomainSchema is now DomainType ( issue 263 ).
• CompositeOperation is now ActivityOperation ( issue 248 ).
• CompositeFunction is now ActivityPredicate ( issue 268 ).
• PrimitiveOperation is now BuiltinOperation.
4. Removed elements
• The DynamicApplicationElementSet element has been removed ( issue 253 ).
• The abstract type ApplicationElement element has been removed ( issue 257 ).
• The ExternalValueEdge element has been removed ( issue 274 ,  issue 277 ).
2. Code generation
• The DomainIterator query now supports the now() function ( issue 203 ).
3. Interface
• The visual representation of metamodel elements is now consistent across all elements, and generated by SimpleGMF ( issue 233 ).
• Names obtained from ENamedElement, rather than NamedElement, will now be correctly displayed ( issue 282 ).
4. Documentation
• All metamodel elements are now documented through ModelDoc.
• All model completion rules are now documented through ModelDoc ( issue 240 ).
• The HelloWorld documentation has been updated ( issue 138 ).
5. Verification
• OCL constraints on the metamodel have been implemented through the EMF Validation Framework ( issue 235 ).
• The NuSMV verification plugin has been released through the update site ( issue 236 ).
• The CrocoPat verification plugin has been released through the update site ( issue 237 ).
6. Performance
• Initialising new IAML diagrams should now be faster, as an unnecessary HTTP request was removed ( issue 252 ).
• Unused model completion rules have been identified and removed ( issue 261 ).
• Unused metamodel constructs and references have been removed ( issue 259 ).