- This topic has 19 replies, 14 voices, and was last updated 19 years, 5 months ago by
.
-
Posts
-
I guess, Tiles support could also be useful, some ideas:
– an inheritance hierarchy for Tiles definitions similarly to type hierarchy for classes/interfaces, also hot links for navigating to the specific Tiles definition in the xml file from the hierarchy view
(a similar would be useful for the Spring support (beside the Spring-ide bean-dependency graph feature), please note this for there)
– a dependency and/or flow (if applicable) graph (similar to struts flow or spring bean depency graph) showing tiles definitions, and other (non-attribute-like) artifacts which can be referred from a tiles definition
– whatever I forgot about 🙂
Regards,
Robert
Still,
– Tiles is available in Struts 1.2, and Shale will not be out for some time,
– Spring supports Tiles directly, and
– there is a proposal to ASF to isolate Tiles out of Struts again as a separate (maybe even top-level) project.So I definitely see no reason why Tiles itself should be considered as murky water since there is a stable release to provide functionality for, even if it might not further be developed (but I guess it will be further developed as a separate project).
Regards,
Robert
I would vote for Sitemesh rather than tiles since it does not depend on the Struts codebase and is arguably more powerful.
Just my $.02
Derek
dadams (at) gaijin-studio.orgGuys this is in our bag of ‘things to do after 3.9’, so no official stance on what we are going to do with Tiles (just wanted to update the thread to let you know we weren’t ignoring it).
I’d like to see tiles support too. It should include
– the possibility to use user defined controller as defaults in the tiles-defs.xml
– usage of more than one tiles-def.xml files
– visualization of the relationships between tiles defined in different tiles-defs.xmlregards,
Jürgen
