Unfortunately I haven’t focused on keeping the components very modular. As it stands right now, the components pull from every project that makes up the framework, so you’re absolutely right. I’m trying to get everything in the framework up to a certain level of quality, then I plan on building out the components for better general use. But I’m only one guy ;).

I generally agree with this: make it work, then make it elegant, then make it fast. I think I’m somewhere between step two and three.

Thanks for the interest, would love to get feedback on what documentation or features you need, and maybe even some github pull requests :).

Fancy stuff – although I only was able to have a short look so far. What I’m most concerned is speed. You write:

“The speed you expect from a TextField, the power you expect from a Text Engine.”

and that sounds most promising. Unfortunately when creating a simple Hello world speed test (just creating 10000 textfields, adding some text) I see a *massive* decrease (>100x) in speed compared to the bad old flash.text.TextField. Can you elaborate a bit more where speed comes in? (or what I should do different?)

The other thing is size: This simple test mentioned before is (release built) 66kb. That’s not nothing. So may be it just packs a load of features in it, just in case – that’s probably reasonable, but I’ve got to say, that adding this to an existing framework can have quite an impact. I just wonder: why does it have to be that fad? Or rather: can I prevent it from becoming fad?

While digging deeper into ur code, the last question might become obsolete, but for the speed, i’d really love to hear your thoughts and experiences. Thanks a lot!