Yes, sure I will, though there ware few "features" that putt me off a bit...
Like, digging a bit dipper into the process of translating of MXML file I found that it is very raw at the moment
This means that the MXML compiler isn't very smart... in fact it isn't smart at all, besides there are lots of minor bugs an inconsistency of what comes out of MXML code...
Few things to mention:
- impossible to add multiple listeners for the same event.
- impossible to remove listeners added through MXML.
- inconsistent behavior of [DefaultProperty] when used with [ArrayType].
- impossible to specify access modifiers through MXML.
- no control over how generated listeners are defined (they are declared as public always for no reason).
- general "not smart" code generation (like, references to functions are made by string identifier - a potential danger of ambiguity if you happen to have more than one open namespace and those namespaces happen to have methods with the same names, valid listeners added through MXML are not recognized- thus additional listeners are generated).
- And least but not last: the properties declared in MXML are not guaranteed to be declared in the AS resulting from it in any order... nor alphabetical, nor display object / non-display object... neither the order from MXML - so that if you wanted to do the depth management by yourself, it just looks now like that is completely impossible...
And there are lots more things to complain about...
And, yes, I'm working on some big project where I intend to use what I try to do with MXML. But it is miles away from being completed and is huge
at the very best it will get into production stage late this Autumn (well, I may be optimistic
Considering the framework.swc. I have updated that file several times, firstly, I forgot to add there the classes needed for embedding assets. I'll check if I forgot anything else to add there. Besides it is based on framework.swc from SDK 3.2 (at that time ISystemManager used to have way less methods (all the ApplicationDomainBridge stuff was added in 3.3, which made SyStemManager even more difficult when trying to load Flex SWF into regular SWF
A friend of mine is now working on some sort of navigation helpers and site structure patterns (if you're familiar with Gaia - something of that kind, but less complex). So, next thing I'll be working on will be incorporating of what he does in my project. Sure, I'll have to review all I have and, yes, I'll continue working on it!
Besides, I've added an example of stuff I added lately:
(skins / styles and hints)http://code.google.com/p/e4xu/source/br ... k/examples
it has an SWF which is basically the test of different things + the MXML source for it.