Jörn Nettingsmeier wrote:
hi *!
i just checked out the new unified resource handling (thanks to doug and
andreas!).
Thanks to Thorsten and Wyona ;).
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?
can somebody who's into the asset code clarify how assets are
differenciated from documents for the purpose of the insertAsset
usecase? i'd like to see this set documented and set in stone somewhere.
since i'm trying to unify the insertAsset and insertImage usecases: how
do we tell images (or in fact anything that can be directly displayed in
the rendered page) from "binary" assets (i.e. stuff that will be
displayed as a link, such as pdfs)?
Currently "resource" doctypes are referenced as assets.
Perhaps this should be handled instead by formats of the doctype instead
of a particular doctype. This way, any document that has an image
representation would be treated as an image, etc.
WDOT?
--Doug
best,
jörn
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
