On 12/11/06, Kent Tong <[EMAIL PROTECTED]> wrote:

Hi,

As needed by the workbench, there are some items that I may help with.
Please let me know if it is the way to go or you have some other ideas
in mind:


Again, I hope that the workbench is temporary; I really think we want more
compelling examples than this old hack!


1) Image component. Why have an Img component in app1? What's missing
in it preventing to become a core component?


I'm just being very slow and very careful about adding components. I really
think there should be far fewer coponents in T5 than in T4.


2) Any component. I've written a simple one in the workbench. If there
is no proposed design change, I'd like to move it to the core. There
is a minor issue though: it seems there is no way to specify a "type"
attribute as an informal parameter:

  <t:comp type="literal:text/css" element="literal:link" .../>


This may need to wait for invisible (T4-style) template instrumentation, i.e
.:

 <link t:type="Any" type="text/css" ...

My current leaning is that for this style, parameters are assumed to be
literal: unless prefixed.  We'll see if that is confusing.


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.

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 @Inject
annotation and expose a read-only property, but still ...


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.


--
Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT)



Having fun yet?

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind

Professional Tapestry training, mentoring, support
and project work.  http://howardlewisship.com

Reply via email to