Em Thu, 02 Oct 2008 18:04:24 -0300, Alex Kotchnev <[EMAIL PROTECTED]> escreveu:

Who would have thought this much discussion would come out of this :-)

Unanimities are boring and we learn next to nothing with them. :)

I am not advocating the usage of some "other" magical framework to manage the layouts.

I think I have not made my point clear: I was not talking about having to learn another framework, but learning one more feature from our framework.

My point is this : how many applications do you have that DO
NOT use a common layout ?

Now you raised a good discussion point. :)
But there is a hard question to answer: how can we write a layout component that is good enough for most of the situations? What would be its template? I don't have the answer. Maybe we could provide some ready-to-use layouts, but I don't think this should be an intrinsic part of the framework, just an useful add-on.

I fail to see how having 2 artifacts (an empty class and html) is simpler than having just one, especially when the java class is just an empty class.

Simple in the sense that you have just one option (1 class - 1 template) instead of two (1 class - 1 template, just 1 template). I'm not sure, but I vaguely remeber Howard speaking that the obligatory page class simplifies and gives a better performance to the inner workings of Tapestry.

In the little project that I do, I do have a bunch of pages that are
composed of mostly static text, but for which I like being able to apply the same layout as all the other pages.

It's not exactly the same thing, but a feature request I would do is Tapestry to pick up new classes (pages, components, mixins) and templates after the application was started. It already picks up chages to existing things, but not picks up new things. ;)

--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
Consultor, desenvolvedor e instrutor em Java
http://www.arsmachina.com.br/thiago

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to