Components and Modules are two different things for very different purposes. I do not believe it is an "either or" situation.
Module are usually designed to be an app in an app; basically a self contained complete set of functionality. Where as components are designed to be flexible units focused on a single task; and [in theory] optimized for reuse across multiple projects.
On 6/21/2010 7:46 AM, Wally Kolcz wrote:
In the beginning of my Flex web development I used components to separate different functionality of my web applications. Being acutely aware of load time and different user bandwidths, I switched to now develop my applications in modules. This has made my web applications load faster. Now I am developing 2 pieces of software using AIR and not sure which approach is better. One I started with the same approach using modules, but now that its time to work on the other I am curious if there are any glaring benefits to developing in Modules with AIR. Load time seems relatively short since its using the computers processing power. My apps are certainly faster loading than Adobe's ;). Application install size is not really a factor since none of software application are remarkably huge. It seems a lot easier for me (and much much lazier) to just take each sub application, put it into a Group component and use a viewstack to move around the application rather then loading and unloading separate modules. Now that I am getting into more custom software development, I would love some advice from the experts here on this 'best practice'....Modules or Components. Thanks!
-- Jeffry Houser, Technical Entrepreneur Adobe Community Expert: http://tinyurl.com/684b5h http://www.twitter.com/reboog711 | Phone: 203-379-0773 -- Easy to use Interface Components for Flex Developers http://www.flextras.com?c=104 -- http://www.theflexshow.com http://www.jeffryhouser.com -- Part of the DotComIt Brain Trust
