Hi, My thoughts about MVC: - you could start with adding a controller, which you can bypass if you just use the current way of building mmbase sites - it will be easier to add different all kinds of logic to the mix (handling double submit problems, back button etc). - it is possible to create controllers/actions in javascript which is stored in WEB-INF and compiled when needed (using Rhino) - in struts for example you would have: struts-config for page flow, javascript for retrieving and processing data, and taglibs to create the presentation. - the model and the way of creating a site doesn't change much (iterative development possible). - applications that need a controller can use and extend it For MMBase you'll need to make MVC as easy to use as possible (not loosing flexibility or speed of implementation). Adding MVC add's a concern, but it also add's room for extension. It's a trade-off, but most systems that are growing and are becoming more complex (in terms of flexibility, possible extension, etc) benefit from adopting MVC. My 2cts Michael
-----Oorspronkelijk bericht-----
Van: [EMAIL PROTECTED] namens Andrà van Toly
Verzonden: vr 28-1-2005 12:43
Aan: [email protected]
CC:
Onderwerp: Re: [Developers] post developers meeting(presentation tags)
At 11:30 +0000 28-01-2005, Kees Jongenburger wrote:
>It was a while ago but V2 proposed to define the data used in view in
>xml. This would free us from the posrel problem in jsp pages. I think
>(like rico said) that the "A" current way to do this might be to have
>separates jsp (or jsp parts) to define the model used and to show the
>data. The can be used for the global structure of pages. On the other
>hand i dislike MVC because it's anty OO and you have to do everything
>3 or more times.
And, in my view, MVC presumes that you can
completely define your site's model beforehand.
Which is maybe the case in some high profile web
sites, but in most cases is not. It's not very
iterative.
One of the concepts, i believe, that laid the
fundament for the web was the iterative nature of
HTML. You could (can) at every moment change the
look of your page by fiddling with your
HTML-tags. And that's also the nature of the
current MMBase taglib, you can fiddle as much as
you like until it looks right ;-)
I think MMBase could use both kind of logics,
buth a taglib that is more suitable for
'iteratively' building smaller sites will be my
favorite.
---AndrÃ
--
Andrà van Toly
http://www.toly.nl mobile +31(0)627233562
------------------------------------------------------------------>><<--
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
Disclaimer
Dit bericht met eventuele bijlagen is vertrouwelijk en uitsluitend bestemd voor
de geadresseerde. Indien u niet de bedoelde ontvanger bent, wordt u verzocht de
afzender te waarschuwen en dit bericht met eventuele bijlagen direct te
verwijderen en/of te vernietigen. Het is niet toegestaan dit bericht en
eventuele bijlagen te vermenigvuldigen, door te sturen, openbaar te maken, op
te slaan of op andere wijze te gebruiken. Ordina N.V. en/of haar
groepsmaatschappijen accepteren geen verantwoordelijkheid of aansprakelijkheid
voor schade die voortvloeit uit (de inhoud van) de verzending van dit bericht.
This e-mail and any attachments are confidential and is solely intended for the
addressee only. If you are not the intended recipient, please notify the sender
and delete and/or destroy this message and any attachments immediately. It is
prohibited to copy, to distribute, to disclose or to use this e-mail and any
attachments in any other way. Ordina N.V. and/or its group companies do not
accept any responsibility nor liability for any damage resulting from (the
content of) the transmission of this message.
<<winmail.dat>>
_______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
