RL2 Beta3

[Shaun Smith]

Howdy List,

I've posted a new beta (b3), but since GitHub has deprecated their Downloads page I've had to modify the robotlegs.org website and upload it there.

This release include the last (hopefully) API breaking change: the "lifecycle" property has been removed from IContext. Instead, the lifecycle methods (beforInitializing etc) have been added to the Context's API directly.

Extension authors please note: This change will break any extensions that made use of the lifecycle accessor. Please update your extensions to make use of the new API. 

Before: context.lifecycle.beforeInitializing(callback);

Now: context.beforeInitializing(callback);

Other changes included in this release are:

The Vigilance Extension has been included in the default MVCS Bundle. This means that mapping overrides (including injection mappings) will now through Errors instead of issuing warnings. You can avoid this behaviour by creating your own Bundle.

The MVCS Bundle sets the logLevel to DEBUG. This provides greater insight into the framework when getting started with Robotlegs. As above, you can avoid this behaviour by creating your own Bundle.

The Context exposes two new methods: addChild(context) and removeChild(context). These can be used to manually wire contexts together - for example, in situations where there is no Display List. When adding a child context that context must be in an uninitialized state.

That's it for now. Please try it out and provide feedback by raising issues on GitHub:

https://github.com/robotlegs/robotlegs-framework/issues

[Alessandro Bianco]

Nice! where i can read more about the Vigilance extension? need to understand if it's a good or bad thing for my usual setup :)

Bianco Alessandro

--
You received this message because you are subscribed to the Google
Groups "Robotlegs" group.
To post to this group, send email to robo...@googlegroups.com
To unsubscribe from this group, send email to
robotlegs+...@googlegroups.com
for support visit http://knowledge.robotlegs.org

[Shaun Smith]

Heya,

I probably need to add a readme for that one, but for now you can have a look at the source:

https://github.com/robotlegs/robotlegs-framework/blob/master/src/robotlegs/bender/extensions/vigilance/VigilanceExtension.as

As you can see it simply registers itself as a log target and throws errors when warnings (or other severe messages) are logged. It also adds itself as a listener for Swiftsuspenders mapping overrides and similarly throws errors when mappings are overridden.

I think that it's a good idea to install the Vigilance Extension. You can always add a global exception handler for production environments, which is recommended anyways.