Blog post about T5 being bad for interface developers.

[Inge Solvoll <in...@gmail.com>]

Quite interesting post, don't know if you've seen this. Howard answers in
the comments.

http://friendlybit.com/html/tapestry-5-and-how-not-to-treat-html/

Re: Blog post about T5 being bad for interface developers.

["Thiago H. de Paula Figueiredo" <th...@gmail.com>]

Em Tue, 13 Oct 2009 14:31:14 -0300, Martin Reurings <ma...@windgazer.nl>  
escreveu:

> He didn't come up with anything that hasn't been mentioned before. Most  
> of his points can be explained both ways, being either good or bad from  
> whichever 'school' you follow. I seriously think this particular  
> developer has the same issue that I had 3 years ago, component based  
> frameworks limit our (Interface Developers) control over the html output.

In Tapestry 5, if you have complete control over HTML, you can create a  
page class that returns a TextStreamResponse. :)

> allows a developer a large amount of control. And instead of coming up  
> with 'Yet Another JavaScript Library' T5 happens to run on prototype,  
> which happens to clash with jQuery (or perhaps the other way around?).

I guess Prototype is older than jQuery.

> The only point I might possibly like to have a talk about is  
> self-closing tags getting expanded. I don't see the benefits of it? But  
> then, I want my pages to output html4, or html5, not xhtml, so I don't  
> care :)

You can define if Tapestry will output HTML or XHTML. The same page, with  
the same state, can be rendered a little differently when using one or the  
other. And you can even provide your own MarkupModel if you want something  
different.

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

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org

Re: Blog post about T5 being bad for interface developers.

[Martin Reurings <ma...@windgazer.nl>]

He didn't come up with anything that hasn't been mentioned before. Most 
of his points can be explained both ways, being either good or bad from 
whichever 'school' you follow. I seriously think this particular 
developer has the same issue that I had 3 years ago, component based 
frameworks limit our (Interface Developers) control over the html output.

However, where frameworks like .Net, DotNetNuke and JSF (any 
incarnation) almost completely black-box the components, at least T5 
allows a developer a large amount of control. And instead of coming up 
with 'Yet Another JavaScript Library' T5 happens to run on prototype, 
which happens to clash with jQuery (or perhaps the other way around?).

The only point I might possibly like to have a talk about is 
self-closing tags getting expanded. I don't see the benefits of it? But 
then, I want my pages to output html4, or html5, not xhtml, so I don't 
care :)

I stand by what I posted at that blog, T5 may not be perfect, but it's a 
far cry from most of the other frameworks...

Thiago H. de Paula Figueiredo wrote:
> Em Tue, 13 Oct 2009 04:13:53 -0300, Inge Solvoll 
> <in...@gmail.com> escreveu:
>
>> Quite interesting post, don't know if you've seen this. Howard 
>> answers in
>> the comments.
>> http://friendlybit.com/html/tapestry-5-and-how-not-to-treat-html/
>
> That guy raises some good points, but that post is mostly comprised of 
> uninformed rants. For example, what he says about Tapestry forcing 
> form ids is flat out wrong.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org

Re: Blog post about T5 being bad for interface developers.

["Thiago H. de Paula Figueiredo" <th...@gmail.com>]

Em Tue, 13 Oct 2009 04:13:53 -0300, Inge Solvoll <in...@gmail.com>  
escreveu:

> Quite interesting post, don't know if you've seen this. Howard answers in
> the comments.
> http://friendlybit.com/html/tapestry-5-and-how-not-to-treat-html/

That guy raises some good points, but that post is mostly comprised of  
uninformed rants. For example, what he says about Tapestry forcing form  
ids is flat out wrong.

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

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org