Mykola Paliyenko > but how often do you need model to be shared across views that are backed by different mxmls?
This definitely depends on the type of applications you are creating. The one I am working on now has roughly 20 tables and only 3 are changed by the user. I do more reading and interactivity with the data then worrying about the 3 tables to maintain. This leads me to share a single model across different Views, letting me keep my model the same as the Views change over time. Every time I want to display the same information in a different way I don't have to worry about the Model being generated by a specific View. > Even if you need it you can access one view from another, you can create some more general ViewHelper in this case that will contain that model. Are you inferring that each ViewHelper will have its own model? Duplicate data? Or are you thinking of a ViewHelper-Model driven idea. This might be interesting for you debate about the model being static versus lazy loading the model structure. > I'm my project 90% cases are just dummy calls to the server and displaying the results. Do you see a case where loading one set of data and using across multiple Views is needed? There is some power in realizing we have options to use the power of RIA and flash client, it is not tied to a paged semi-static presentation layer. > If I'll need something that does not fit this concept and makes viewhelper very complex I can always refactor, but why should I start having in mind that I'm writing something very complex. My principle is use the simplest reasonable way that works. This can be answered only by experience to your specific application and development team. I would agree with you on this one, keeping it simple but always refactoring is good. > If it works for JSF, Struts, Webwork, Tapestry then why it does not work for RIA, only because client has more logic? Maybe cause I have no DnD in Java and some effects but all the rest seems to be the same. With Flex 2 there will be more differences, but this is such a big area where some things make sense to compare and some things don't compare at all. I don't have a good comparison on any of these points. The simple difference is that one ends up as D/HTML pages while the other has the power of a Flash client. Either one can be used for bad or good. Renaun ------------------------ Yahoo! Groups Sponsor --------------------~--> Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life. http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/nhFolB/TM --------------------------------------------------------------------~-> -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
