Flex Modules Over MXML Component Architecture -

i in process of architectural of our project. have choosen mate framework. project not quite complex, advantages on mxml when choose modules.

main app - > views - > events - > maps - > services [php or java] 

when come modules based architecture, seems doubt should not end tight coupling , unwanted issues may break head later solve.

main app - > modules - > module interface -> events - > maps - > services  [php or java] 

1. what advantages if choose modules on mxml component?
2. what prefered , best way architect flex application?
3. since application going communicate backend, need make frontend more complex?
4. is there modules based archiecture sample preview or example have defined architecture.

i've built several flex applications using mate framework environment bit different yours. in case, answer questions:

what advantages if choose modules on mxml component?

modules should used pieces of functionality want reuse across multiple applications. benefit of using modules kensodev mentioned can used in other applications without having rewrite or duplicate code. if application you're architecting going standalone , none of functionality going reused go straight mxml.

what prefered , best way architect flex application?

it depend on app. of apps i've built using mate mxml based , didn't use modules, may make sense use modules in case. depends on project requirements are.

since application going communicate backend, need make frontend more complex?

i'm firm believer in making ui simple possible , doing of heavy work on middle tier or end. goal of project make life easier or more convenient user. in other words, front end that's presented user shouldn't complex underlying business logic , end work be.

is there modules based archiecture sample preview or example have defined architecture.

mate has sample projects available look @ in terms of how structure projects. if helps, structure our projects similar this:

src | |_assets (images or other assets go here.) | |_applicationname   |   |_events (your custom mate events go here.)   |   |_maps (your mate maps go here.)   |   |_model   | |   | |_managers (your data managers go here. of data processing end happens here.)   | |   | |_vo (your value object classes go here.)   |   |_ui     |     |_components (mxml components go here. typically these "front end" components.)     |     |_presenters (your presentation models go here. think of them "code behind" classes front end components.)     |     |_renderers (any custom item renderers lists of data grids go here.)     |     |_skins (any custom skins components go here.)     |     |_views (your application views go here.) 

i hope helps!