tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thiago H. de Paula Figueiredo" <thiag...@gmail.com>
Subject Re: svn commit: r741938 - in /tapestry/tapestry5/trunk: src/site/apt/ tapestry-core/ tapestry-core/src/main/java/org/apache/tapestry5/ tapestry-core/src/main/java/org/apache/tapestry5/internal/bindings/ tapestry-core/src/main/java/org/apache/tapestry
Date Mon, 09 Feb 2009 22:27:00 GMT
Em Mon, 09 Feb 2009 17:42:23 -0300, Howard Lewis Ship <hlship@gmail.com>  

> This is to get ready to
> bring back a version of $content$ and $remove$ (from T4),

I implemented something very similar to $content$ and $remove$  
implementing two components: crud/Remove (renders absolutely nothing, just  
like $remove$ [1] and crud/JustBody (renders only its body, not its  
element) [2]. A template using them to provide complete previewability can  
be found at [3]. That's one very nice Tapestry feature: implementing a  
very simple component you accomplish something that need special treatment  
in other frameworks (like Tapetry 4, for example).




> plus future
> ideas (allow a subclass template to override only portions of the
> superclass template).

Couldn't this be accomplished just using regular block parameters? AFAIK,  
this can be true for components, but not for pages. Am I right?

Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor

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

View raw message