Share the Wealth!

["Byrne, Steven" <SB...@dorado.com>]

Ok ok -- so it looks like spam, but I'm really interested in discussing
sharing of assets. 
 
I'm finding that in my application, there are a large number of assets
that are common to a bunch of components, and it's somewhat of a pain to
have to specify them repeatedly in each .jwc file, including the exact
path to the asset.  This feels clumsy to me -- what if I need want to
move where a particular asset is, such as factor it out into a common,
generic library, I would have to go find and fix each definition of that
asset in all of the .jwc and .page files that I have (which can be a
lot).
 
What I'd like to have is a way to somehow factor out the mentioning of
the exact path to the asset into some "logical" binding that would be
held at a more macro level of granularity, such as in a .library file.
 
Or, it would be cool if there just was a way from component templates to
refer to assets defined in the .application or .library file (almost the
same thing).
 
Has anyone implemented anything like this?  Is there any thought in 3.1
for providing this kind of support for more serious application
development?
 
Steve