ingo schuster wrote:
> At 16:00 01/24/01, ingo schuster wrote:
> >Hi,
> >
> >we still have some properties files in src/config/ , they are not
> >maintained and not needed. Shouldn't we remove them?
+1
> >What about some of the screen modules in jetspeed/modules/screens/ ? I
> >replaced EditAccount, Login, NewAccount and ConfirmRegistration by
> >respective JSPs, they are not needed any more.
+0
> >The EditAccount.jsp needs to find some information about the user in the
> >request. I added an action "PrepareScreenEditAccount" that does this -
> >however you have to make sure that the screen template isn't called
> >without executing the action earlier. Another way to solve this would be
> >to still have an EditAccount.java (screen) that does all the data
> >processing and sets the template name that's used to display the data. I
> >didn't think about this possibility earlier because "screen" sounds like
> >View and "action" like Controller.
> >Do you think that would be cleaner?
> >
I think the intent is to use the screen class to populate the static context
(in this case, get the account information) and use actions to handle the
dynamic modifications (in this case the updates).
In the current Turbine "push" model, i'd say that:
View = template
Controller = screen (active processing) [ + action (reactive processing) ]
--
Raphaël Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Services Manager / Paris
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
