|
From: Tarjei S. <lo...@on...> - 2003-08-01 16:43:48
|
On Wed, Jul 30, 2003 at 10:41:04PM +0200, Alef Arendsen (JTeam) wrote: [..] > As far as additions to the MVC are concerned, I don't think much is > needed to be able to build a decent webapp. Anybody interested in > getting the TilesView(Resolver) in before the 1.0 release (might be a > nice feature to show the pluggability and stuff)?? I'm very interested in getting at least TilesView in before 1.0. I'm using Tiles myself for most of my own personal projects and I find it highly useful. I've spent some time lately looking at the TilesView and TilesViewResolver you posted a couple of weeks ago. TilesView seemed to work quite ok, definitely something that could be included in Spring imho :) When it comes to the TilesViewResolver I'm not quite so sure, it doesn't seem quite right in my opinion. I would much rather see an aproach like the one we currently have for Velocity. The TilesViewResolver you posted didn't really do anything specifically related to resolving the view, it more or less just took care of initializing the DefinitionsFactory for Tiles. I'd like to propose that TilesViewResolver should be renamed to something like TilesConfigurer. TilesConfigurer would just be a simple javabean that takes care of initializing Tiles, just like VelocityConfigurer currently does for Velocity. TilesView would be pretty much the same as before, maybe we could add a definitionName property that gives the user a possibility to not use the view name as the definition name all of the time. We could default to using the viewname as the definitionname to minimize the need for aditional configration for each TilesView but allow the developers out there to override it if needed. -- Tarjei Skorgenes lo...@on... |