Frank Schönheit - Sun Microsystems Germany wrote:
As a canonical extension, for "hierarchical" documents such as forms in
database documents, there should be a third item in the list, to store
in configuration in the database document, and to apply it to all "sub
documents" of this database document (of the given type).
Yes - a much better way of putting what I intended to say.
There's two obstacles I see: First, I am not sure how hierarchical UI
configuration is currently handled by the framework. Of course, if a
given document contains a toolbar configuration, but no menu
configuration, then you want it to fall back to the forms-in-DBDoc menu,
*not* to the global configuration. This might require additional
implementations in the framework.
Second, the current UI does not allow to remove the configuration for a
particular menu/toolbar.
As I well know - the MyInvoice database I attached to a couple of emails
has a mangled database document menu tree - I just went right in, with
no forethought and 'mangeld' away (R.P.?)...not something to do at
first, maybe not at all on the database document, but certainly a last
step not a first.
Drew
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
