Hi all,

I just came across some of the mails about Tiles2. First, I am very glad that someone has the time to let Tiles evolve. But, I am a little bit disappointed about how the proposed Tiles API evolved.

 In some case, I have the feeling that we are going backward :-).
A lot of redundancy in Tiles comes because of the backward compatibility with the template library. Some new tag names where proposed because old ones were confusing. In the same time, the old names were left for backward compatibility.
 If I remember well :

   * <get> was changed to <insert> - because we mainly say that we want
     to insert something
   * Attributes "template=" and "component=" were changed to "page=" -
     because we specify the page to insert. Tiles is more than a
     templating mechanism, and the inserted page is not necessary a
     template :-). Maybe we can use "tile=" now that tile is a very
     well established name.
   * The controllers were added to allows stand alone use of tiles to
     be able to do some kind of computation associated to the tiles.
     When used with Struts, there is a redundancy (with the use of
     actions), but when used alone, the controller mechanism is very
     useful to separate view rendering from controller business

It is true that Tiles2 gives us the opportunity to remove all the redundancies, but we have to take care to not fall again into the previous mistakes :-) Once again, that my feeling after reading some of the mails, and maybe I have missed something in the discussions.

 Cedric

Antonio Petrelli wrote:

Re-hi list :-)

I noticed that GetTag extends InsertTag and it does not add anything, it only sets "isErrorIgnored" flag to true.
So I am thinking on removing one of those.
From my POV it should be better to remove InsertTag (or better, remove GetTag then rename InsertTag to GetTag), because this way it is clear that GetTag is the opposite of PutTag.
What do you think?

Ciao
Antonio

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to