Re: Project activity

This is a multi-part message in MIME format...

------------=_1124476761-15681-181
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Massimo Lusetti wrote:

>Not at all, please look at Tapestry related infos (doc, ml and source).
>Not counting that the template are still public documents since
>they're rendered in your web app.
>
Hi Massimo,

Well.... I've read the docs and I posted the question to the mailinglist 
(see mail 'Some Tapestry 4 questions' by me from 17th of July). The 
answer I got from Kevin Menard was this:
-----------------------------------------
It does matter where you  place your HTML file though.  I have a 
directory structure like:

context/
   -----------> css/
   -----------> WEB-INF/

I used to place all my HTML & .page files into WEB-INF/, but it  seemed 
when I dumped the .page file, I had to move the HTML file up  to 
context/.  Maybe you should try that.
-----------------------------------------

As soon as I did that, it all worked. And unless I'm completely 
misreading it, it still says exactly this in the T4 Users Manual: 
http://jakarta.apache.org/tapestry/UsersGuide/template.html

But you are right about this being off topic just a whee bit. :oP



>This discussion is OT here so i will not reply anymore and sorry for the noise.
>
Although the previous issue was indeed off topic on this list, I don't 
think the discussion about the different web frameworks is. The 
Barracuda webpage still lacks some documentation on the Tapestry 
framework. In the 'Surveying the Landscape' section it still says about 
Tapestry: "[...] Interesting approach, but we need to better understand 
the details before we can fully evaluate it in terms of strengths and 
weaknesses."

I personally find this discussion very useful for anyone looking at 
different frameworks to see which one to go with. It is hard to make a 
decision without knowing them all and yet it takes an awfull lot of time 
to get to know them all. Any information that makes that choice easier 
would be welcome in my opinion.


>For the records, I like barracuda too as I've used it for my biggest
>app (an HTML to Z39.50 gateway with state-full to state-less protocol
>binding) and it served me _very_ well but Tapestry seems to me a more
>powerful framework, just to mention one feature, its support for
>portlet development. So it is difficult to compare the two without
>keeping in mind the broad target they share.
>
I think we are in full agreement here: Barracuda is very cool, but at 
the moment Tapestry is the most powerful and mature framework. 
Especially combined with Java5/Annotations.

Wicket seems to be gaining momentum at tremendous speed though.


Regards,

Onno



------------=_1124476761-15681-181
Content-Type: text/plain; name="message-footer.txt"
Content-Disposition: inline; filename="message-footer.txt"
Content-Transfer-Encoding: 8bit



--

Barracuda mailing list

[email protected]

http://www.objectweb.org/wws/lists/projects/barracuda


------------=_1124476761-15681-181--