> > On Tue, 2011-12-13 at 19:29 -0500, Nicolas LE BAS wrote: > >> It just means you have to either implement getContext(scope) for every > >> view request > >> > Are you still planning to do it, mck? If not, do you want me to do it > before 3.0?
Yes. For over a couple of weeks now i've got the vast majority of the "removing ContextResolver" work done. The more i did the more i agree with you Nick. I just haven't had the time to wrap up it up for ready for moderation... I'll chase it up over the next few days. > D. On 12-02-17 11:01 AM, Nicolas LE BAS wrote: > > replacing the URLs by a "ApplicationResource" > > abstraction. That would help providing a clean solution to Gordon's > > issue, and encapsulate the naming conventions we use for > > internationalization. Absolutely! See my reply in the other thread. > E. On 11-10-19 05:41 AM, mck wrote: > > Documentation around Tiles-3 is a big todo still... > > Perhaps if we break this up into smaller tasks, it would look less scary :) Yes. And just take a minimalistic approach. I think making sure existing documentation is correct is important. And basic small tasks that help at the entry level. F. I'd like to add accepting Morten's patch for a MustacheRenderer. https://github.com/apache/tiles/pull/1 Introducing client-side templates into the tiles framework i think is an important step forward into where technologies are moving today... The front end guys (+girls) are all too often off in javascript and busy in just the client-side world, and this is one audience where tiles needs to be well accepted. So if we agree the todo list currently stands at A) package javadoc B) remove ContextResolver D) replace URLs with "ApplicationResource" E) minimal tiles-3 documentation F) MustacheRenderer ~mck -- "The trouble with being in the rat race is that even if you win, you're still a rat." Lily Tomlin | http://github.com/finn-no | http://tech.finn.no |
signature.asc
Description: This is a digitally signed message part
