Howard Lewis Ship <hlship <at> gmail.com> writes:
> Again, I hope that the workbench is temporary; I really think we want more
> compelling examples than this old hack!
Sure. Make it work and make it better.
> 3) Shell component. Any proposed enhancements?
>
> Hoping this will not be needed, though it is useful for linking to
> stylesheets. I'm hoping that we'll soon be able to say:
>
> <html>
> <head>
> <title>${page.title}</title>
> <link type="text/css" href="${stylesheet}"/>
>
> I want to loosen up the rules to allow expansions inside non-component
> element attributes.
It seems a good idea. Now I see why you hesitate to have the Image,
Shell and Any components. So I'll just keep them in the workbench
for the moment and revise/remove them as it goes.
> I think the asset: prefix will be different too, it will be used to identify
> a resource relative to the actual template (the template may
> be on the classpath). In many cases, it will be easier to use the <at>
> Inject annotation and expose a read-only property, but still ...
OK.
> 4) The "source" parameter of the Loop component doesn't accept an array
> > (because arrays don't implement Iterable). Maybe we can enhance to
> > TypeCoercer to handle the conversion (map Array.class to Iterable.class)?
>
> That would be a good solution, either Object[] --> List or Object[] -->
> Iterable would be good.
Will try.
> Having fun yet?
Well, I'd say it's a good learning experience.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
