[EMAIL PROTECTED] wrote:
Browser-based applications should put as much information on a single
page in a single column (two table columns for label and information)
with a single "Save Everything" button at the bottom. Vertical
scrolling is good. Tabs (each with their own Save buttons) are bad.
Combining all of the tabs into a single page would be a major
improvement.
you might want to do a mockup of your ideas, which
would help to discuss possible refactoring of the site area
[Possible exception: I believe Assets should be connected to the
publication rather than documents. They should have their own
workflow, versioning, and security. But if that change is not
accepted, then Assets should be a section on the (single) document
information page.]
I think most of us would like to have assets handled as any
other document which would allow reuse, etc. By using UUID this
should be a problem and maybe introducing a asset doctype.
But I think it still makes sense to have document attached asset
screen, not to manage the assets itself, but rather to "manage" the
links to the assets, which should be bi-directional.
Michi
solprovider
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Michael Wechner
Wyona - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
