Quite true. And Flex has poor modularity, mainly for historical, but also for performance reasons. I am all for better modularity in Flex in the future, the question is how to get there. However, I'm hoping we can continue such a discussion in a separate thread.
On 1/4/12 12:54 PM, "Bertrand Delacretaz" <bdelacre...@apache.org> wrote: > On Wed, Jan 4, 2012 at 9:42 PM, Michael Schmalle <m...@teotigraphix.com> > wrote: >> ...I also think that the list should really have a decent discussion about >> the >> future uses of interfaces and the lack of them in the framework to allow for >> customizations through composition instead of subclassing or copy and paste >> craziness.... > > I have extremely limited knowledge of Flex or its internals (which > might actually be a good thing in my role as an incubation mentor > here) but from this and other comments in this thread I sense that > improving modularization and "composability" of Flex might help > avoiding difficult discussions about which component is better than > another one. > > The Apache HTTP server project is an excellent example of extremely > modular software, and I think a big part of that is because people > couldn't agree of what needs to be in a web server. By reducing the > server to a minimal core, and having plugins for most everything, the > part on which everybody must agree is much smaller. > > In summary, I think modularity is a very powerful tool to avoid > conflicts in large open source projects ;-) > > -Bertrand -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
