Thomas Vandahl wrote:
I was in need of better reusable components in my web applications, so
I sat down and wrote a Tiles extension to Turbine. It consists of the
necessary loaders, assembler brokers, screen classes etc. It is
sitting here on my hard disk and waiting to see the light of day.
How does it work? The approach of Turbine is that an application has
layouts, navigations and a screen. This works well for many
applications but is difficult to handle if your application consists
of a lot of screen elements. So what I did was to introduce a
sub-screen module type which can be plugged into the screen using a
pull tool. In Velocity-speak usage is like
<div id="calendar">$tile.setTemplate("CalendarTile.vm")</div>
Could that be a useful feature in Turbine? Do you consider this worth
contributing? Your comments will be appreciated.
Sounds a lot more flexible than #parse() so I am +1.
One more thing. While I went through the Turbine code to find all the
places where modules are referenced I found that even though all these
elements are meant to be pluggable, the structure is somehow
hard-wired. See TurbineAssemblerBrokerService#init() for an example.
Wouldn't it be useful/desirable to refactor this in a way that
additional modules could be plugged in more easily? I admit that this
would mean a lot of refactoring and some changes might even break
applications but I think it's worth it in the long run. Again your
comments will be appreciated.
Sounds like a positive step.
My preference would be to commit these post-2.3.3/2.4-M2.
Cheers,
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
