Hi Tim I'm gonna check that out right away. Thanks for that, really appreciated. Cheers, Diego.
On Tue, 12 Sep 2006 11:24:20 +1200, Tim Hoff <[EMAIL PROTECTED]> wrote: > > Hi Diego, > > I can't speak for Ralf, but the approach that I'm using is similar to > the following example: > > http://www.cflex.net/showFileDetails.cfm?ObjectID=422&Object=File&Channe\ > lID=1 > <http://www.cflex.net/showFileDetails.cfm?ObjectID=422&Object=File&Chann\ > elID=1> > > I prefer to avoid ViewHelper/ViewLocator, but some here still like that > method. For me, using bound view states and views as components works > just fine. I do agree with Bjorn, that if extending a view for other > purposes becomes a need (like a ShoppingCart being used as a WishList), > the class should be instantiated in the ModelLocator. For larger > applications this is common. But, not always necessary for medium and > small applications. From previous threads on this subject, the > concensus seems to be; use whatever method that works for you. Since > most views reference the ModelLocator anyway, you have a lot of freedom > in this area. > > -TH > > --- In [email protected], "Diego Guebel" > <[EMAIL PROTECTED]> wrote: >> >> thank you all for the reply, >> Can someone point me to the Steve approach? >> I still wonder how do Tim and Ralf register the views, are you > creating a >> viewstack with all the views? for example: how are you managing the >> visibility? >> Thanks, Diego. >> >> >> On Mon, 11 Sep 2006 17:51:34 +1200, Tim Hoff [EMAIL PROTECTED] wrote: >> >> > With views, the main thing to keep in mind is directory >> > organization. Respectfully, I have a few differing ideas, than >> > Steven, when it comes to views. But at Cairngorm's current >> > iteration, "all" state == model (local and common). Organize the >> > actual view classes in functional directory groups; for easy >> > identification. In the ModelLocator, bind the state of the views >> > accordingly. With hundreds of views, you will probably want to >> > subclass the ModelLocator, into functional groups, to aid in >> > organization. Ultimately, it boils down to each application's >> > requirements. For me, I just try to keep things as simple and >> > maintainable as possible; even when endless local state variables >> > tend to clutter and complicate the ModelLocator. I'm calling this >> > model happy. :) >> > >> > -TH >> > >> > --- In [email protected], "Bjorn Schultheiss" >> > bjorn.schultheiss@ wrote: >> >> >> >> Good Question and I hope this thread gets a lot of posts. >> >> >> >> Personally I don't think that the modelLocator is always upto the >> > job. >> >> Don't get me wrong, in a data-driven application this methodology >> > is >> >> beautiful, >> >> But my feeling is it will not satisfy all requirements. >> >> >> >> For example, say you have about 100 view states that are loaded in >> > and >> >> disposed of, at runtime, as required. >> >> I don't think the ModelLocator is up to the task. >> >> I think possibly a "ViewManager" of sorts is required that acts as >> > a middle >> >> tier between the Views and the ModelLocator. >> >> >> >> I don't have any concrete classes to show an example of what I >> > mean as I >> >> haven't developed such a solution as yet. >> >> But I am at the beginning of a project that will require such >> > consideration. >> >> >> >> >> >> Regards, >> >> >> >> Bjorn Schultheiss >> >> Senior Flash Developer >> >> QDC Technologies >> >> >> >> -----Original Message----- >> >> From: [email protected] >> > [mailto:[EMAIL PROTECTED] On >> >> Behalf Of Diego Guebel >> >> Sent: Monday, 11 September 2006 12:07 PM >> >> To: [email protected] >> >> Subject: [flexcoders] cairngorm: managing hundred of views >> >> >> >> Hi there, >> >> My questions is theoretical and best practice oriented, I just >> > wonder what >> >> is the best approach to manage hundreds of views since >> >> viewhelper/viewlocator is out of fashion. >> >> I was reading previous post but didn't find a good example or >> > tutorial. >> >> Can anyone put some light on this? >> >> >> >> Sorry if some of you receive this post twice, I think the first >> > once was >> >> moderated. >> >> Thanks in advance. Diego. >> >> >> >> >> >> -- >> >> 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 >> >> >> > >> > >> > >> > >> > >> > >> > -- >> > 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 >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > > -- 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/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/flexcoders/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> 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/
