On Tue, 2011-10-18 at 00:44 -0400, Nicolas LE BAS wrote: > Of course I realize I'm the newcomer here; you guys have probably > discussed all of this already, and perhaps reached similar > conclusions > (or not...). But it helps me understanding how things are, and well, > perhaps I can help, who know?
Not at all. You've done a great summary of how things stand in tiles-3. Thanks for opening this discussion. > However I noticed that having tiles-velocity-render had no sense without > its "request" counterpart. Therefore I decided to put them together. This is my understanding as well. To do the rendering you need to create an appropriate request/context to that renderer, even if these concepts are on either end of the "bridge". Maybe the documentation could be clearer in saying you only need to include the render dependency though. (For the common case when you're not requiring just the request part). Documentation around Tiles-3 is a big todo still... > Oh, you are right. In fact if we want to separate the API from the > implementation (even the simplest ones) a new module should be > created. Can we extract the api for proposal and go from there? Already i'm struggling a bit to keep up... > Tiles has been indeed the most undervalued project in past decade. It was > the most useful part of struts, but when the focus shifted away from struts, > tiles was forgotten. Since then struts as been outpaced by spring and JSF, > however tiles is still the easiest and most elegant way to organize a > complex web site, and it works not only with struts, but with every current > MVC technology. I agree whole heartedly with you Nick. ~mck -- "Perl: The only language that looks the same before and after RSA encryption." Keith Bostic | www.semb.wever.org | www.sesat.no | tech.finn.no | http://xss-html-filter.sf.net
signature.asc
Description: This is a digitally signed message part
