Now having the same item twice (even if one toolbar can be disabled) is
*really* bad UI design. A better idea would be to introduce OptItem for the
toolbar to let the master-buffer-* items disappear if the document in question
is no child.
But this is all post-2.0 stuff.
Why is this post-2.0 stuff. This is not so difficult ?
Perhaps it's better to postpone all the UI stuff to a future release.
It seems like discussions with a bit of controversy (e.g. UI) get
stalled during development because there's no "manager" to take the
final decision. Then at the last moment everyone realizes something
needs to happen, and others object because of the deadlines.
As a final suggestion for 2.0: Maybe the UI file could be linked to an
icon directory (instead of the preferences which are being developed
now) and we could add an "experimental" UI file linked to the new
icons and toolbar. This way it will be totally separate from the old
default UI, and maybe allow for some discussion regarding a new
default UI in the future.
What are the issues that are still left then ?
Vincent
