A modest proposal

[Jason Feingold <jf...@solsticesoftware.com>]

Why not allow arbitrary data to be attached to assets in a page
specification and expose these data through the IAsset interface?  There
could be a tag name for the data and they could pop out as an XML dom
node.

The reason I ask is that I want to iterate a bunch of assets and display
links to them on the page.  I figure it's easier to configure assets in
a page specification then to shove them in some external file, or a
database, or code them in java.  However, the limitation on the name
field is very restrictive.  It would also be nice to be able to attach a
description to each asset for display.

Any thoughts, anyone?

-- jason

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org