IDEA IMLs should never be committed
ignore more
Merge branch 'jangaroo-1' into jangaroo-3
an example of a Flash-style event declaration that results
in excellent usability in MXML
Get rid of [ExtConfig] for MXML.
[ExtConfig] annotations are no longer needed for MXML
(but still by the EXML compiler).
Instead, an Ext AS component written in MXML reuses the
xtype of its super component, or defines a custom xtype
automagically when a "targetClass" attribute is set.
The top-level config classes component, plugin,
containerlayout and gridcolumn take care of generating
the xtype and registering it with the given targetClass.
This eases specifying Ext AS components in MXML.
Note that this approach relies on a setter function (for
property targetClass) and thus only works in IE8 after
I implement set$foo() being called instead of foo being
assigned. Another option would be to introduce a method
afterPropertiesSet() (like in Spring) that MXML-generated
code calls after having assigned all values.
An example of a Flash-style event that allows to assign the
"click" event handler of an Ext button in MXML.
This has to be done for all Ext events.
Make the viewport config object instantiate itself after the config
component tree has been fully created, so that it suffices to
instantiate a custom <viewport> component and the UI will
appear.
Since the config component tree is built synchronously, the timeout
can be minimal (1).
Using the new [Native(amd="...")] annotation to integrate CKEDITOR
Letting the viewport self-instantiate was not a good idea after all. Removed.
As an example of an inherited event, here is the Flash-like
event API for component#beforerender
repaired EXML to work in parallel to MXML and new Runtime
Using the new [Native(amd="...")] annotation to integrate Ext JS.
Actually, the annotation should be added to each and every API
class. But as it is going to change, anyway, I just introduced it to
the typical entry classes Ext and ComponentMgr.