I've found after (far too many) years of engineering software, that consistency is far better than dogma.
It is incredibly rare that a design pattern, taken off the shelf and dusted, works for every case. In your case, if you have a reason to create the view via the presenter, I wouldn't fear it. I would just update my diagrams accordingly and then *stick to it* in all cases. The statement "I'm using Pattern X" and then varying 50% of the time is far more dangerous, than modifying a pattern and sticking to it :) Roger On Jan 25, 2010, at 8:54 AM, rmuller wrote: > Should not the Presenter create the view? > Sometimes you need different views (based on authorization data in my > case) where you can reuse the Presenter. I let the Presenter decide > which view to use. I do this in the ctor. > In all examples I see however, the Presenter and View are created by > the parent Presenter/AppContext. Also every View has its own Presenter > (1 : 1). So I wonder if my design is correct. > > What is the general opinion about this? > > Ronald > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
