[Riyad Kalla]

rdomingo,
Please give us an idea of what “tiles supports” means to you and your team. What kind of support did you need? Is Rob’s assessment above what you were looking for, or did you not need that much functionality or did you need more?

[rdomingo]

Hi Riyad,

Sorry I didn’t get back to you any sooner. But it is almost time to travel to SF javaone and I still have lot’s of work to do…

Actually I already had an answer to my question, it’s described in the myeclipse roadmap. At least a date indication of tiles support is there.

To answer your question:
I feel we don’t need much functionallity, we just need (probably only the basics, i’m not that familliar with thiles). And when using tiles I would like to be able to keep using the struts-conf design tool of myeclipse.

Currently when using tiles, the tool panics and doesn’t show any sense… It might be a huge improvement when this designer could be aware of the tiles-def.xml so you can also select an existing tile for your forward, etc….

Additional it might be nice to have a designer for the tiles-def.xml. In my opinion the support for struts-conf designer has the higher priority because this one gives an overview of the complete process of your application, we like to use it during development. And on the otherhand the tiles-def.xml is just for layout details and hasn’t that much impact on the overall process.

Hopefully this answers your question, otherwhise feel free to contact me.

have fun,
raymond domingo
ovsoftware

[Bernard de Terwangne]

+ 1 vote for tiles support

[pcwappdev]

I would like to see some kind of tiles support as well. I’m still fairly new to struts and tiles, so one thing that would be useful to me is the ability to see all children tiles of any given tile.

For example, consider the following tiles-def.xml snippet:
<tiles-definitions>
<definition name=”template_t1″>
<put name=”pageId” value=”template_t1″/>
<put name=”site_header” value=”templatexx.site_header”/>
<put name=”site_banner” value=”templatexx.site_banner”/>
<put name=”left_area” value=”template_t1.left_area” type=”definition”/>
<put name=”right_area” value=”template_t1.right_area” type=”definition”/>
<put name=”right_bottom_area” value=”template_t1.right_bottom_area” type=”definition”/>
<put name=”site_footer” value=”templatexx.site_footer”/>
</definition>
<definition name=”templatexx.site_header”>
<putList name=”modules”>
<add type=”definition”>module_logo</add>
<add type=”definition”>module_skybox</add>
<add type=”definition”>module_toolbar</add>
</putList>
</definition>
<definition name=”module_logo” path=”/common/module/hd_logo.jsp”/>
….
</tiles-definition>

It would be helpful for me to have a way to recursively find all the included tiles for tile template_t1. As you can see in this example, template_t1 includes serveral tiles, and these in turn include other tiles. Sometimes this goes down 2 or levels, and it is a bit of a pain to go through all these tile definitions to find which jsp file I need to change. It would be helpful for me to have a way to see all the children tiles of any given tile.

I hope this makes sense, if not, let me know and I will try to clarify.

[mstrong4867]

When a path in struts-config.xml specifies a tile definition (e.g., path=”myapp.viewshoppingbasket”), it shows up as a blue box in the struts-config.xml’s graphical representation. Were it a JSP target, clicking on it would open the JSP.

When it is a tile definition, one would hope that clicking on it might at least go to the definition stanza within that definition’s file.

From there one might want to ctrl-left click on any path defined within the tile definition to bring up the actual JSP’s specified within the definition.

Otherwise, the other suggestions advanced in the thread about drilling up the hierarchy of tile definitions are definitely a good ideas, too.

Just my 2 cents. ;o)

Mike

[Author]

Posts