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 redunda
Hi,
This is a backward compatibility reason, as nearly all the complex
stuff in Tiles :-).
The discussion should be in the old struts archives.
If you remove redundancies, you will break some backward
compatibilities, but you will certainly simplify Tiles.
Cedric
Wendy Smoak wrote:
The Tiles implementation has become complex because of the numerous
backward compatibilities. I think that it is possible to simplify the
code by removing some of them. For example it should be possible to
simplify the way tiles initialize by removing struts 1.0 compatibility
(if it still t
Hello everybody,
I'am +1 in Tiles becoming a top level project, or at least to be
extracted from the Struts core.
You can add me in the set of initial committersin the draft proposal,
if you agree.
Cedric
Ted Husted wrote:
OK, there's a draft proposal up at
[http://wiki.apache.org/struts/T
initialization of Tiles in Struts.
Hope this help,
Cedric
BaTien Duong wrote:
Cedric Dumoulin wrote:
Greeting Cedric:
It has been a long time to see you again on the list. I wonder if you
have some time to make tiles work better with faces. Here is what I
have tried faces and tiles without struts (so
Hi,
Such question should be post in the struts-user mailing list :-).
Tiles is a framework that build pages by assembling fragment or
"tiles" on the server side. When you request a page made of tiles, the
server return the entire page, not a particular tile.
If you want only a particular are
