Jörn Nettingsmeier wrote:
[...]
iiuc, we now treat documents and resources uniformly. (YAY!)
it seems that we have a global asset list in the insertAsset.jx view.
since assets can easily be associated with their documents by their
parent-child relation, we could show only the asserts under the current
document node by default, and allow the user to browse the tree upwards.
that will keep the asset list from cluttering up while enabling the user
to get assets from other documents as well. wdyt?
IMO this should be up to the user, but we should provide a reasonable
default setting. My personal preference would be a global asset store -
e.g. a "media" top-level node where I can attach all media as subnodes,
complemented by a keyword meta data search.
i've seen a similar solution (per-user global asset store and global
asset store) in the imperia cms. it's a world of pain.
the solution i propose would encompass both: you can use per-sitenode
assets, and you can also browse to a central location. having only a
global asset store is imho useless except for very small sites.
That sounds resonable. As long as it is possible to have a global asset
store, it's fine with me :)
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
