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:
1) Image component. Why have an Img component in app1? What's missing in it preventing to become a core component? 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" .../> 3) Shell component. Any proposed enhancements? 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)? -- Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
