Hi Jos, >I notice that you don't mention Data Binding. How important is this >feature? What widgets gain the most from it, which _require_ it to make >them usable? What do we loose from not having it? > > Skipped it on purpose. That's a hairy one.
As you may know, Flex 2 implements a very neat databinding system that's related to collections. I've been thinking about this quite a bit for Arp as well as there are efforts (like Christophe's ModelLocator) that allow binding. In Arp, I want the final solution to work across technologies (Flash 8/AS2, Blaze/AS3, Flex 2/AS3, AS3-only and MTASC) so I'm split as to whether binding should be something that is implemented in a technology/framework-specific manner (what I'm currently leaning towards) or within a cross-cutting structural or component framework (like Arp or a 3rd party component framework.) Ideally, at least for Arp (which is *not* a component framework but a lightweight structural framework), I'm currently of a mind to keep binding out of it so that people can make use of binding in the Flex 2 framework if they want to or use the binding classes in the V2 component framework or not use binding at all. Does any of this make any sense or I am just rambling? :) All the best, Aral _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
