[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [platform-ui-dev] [CN] Updates for the Common Navigator in Platform 3.2
|
Michael Valenta made a similar suggestion. I hadn't formalized it as a
"viewerProperties" extension, but I think this could make sense.
How should we handle the case where multiple viewerProperties extensions
are defined ? Error?
-------------------------------------------------------------------------
Kind Regards,
Michael D. Elder
Rational Studio / Services Tools Development
IBM RTP Lab
Ext: (919) 543-8356
T/L: 441-8356
mdelder@xxxxxxxxxx
Monday, November 28, 2005 9:22 PM
To: "Eclipse Platform UI component developers list."
<platform-ui-dev@xxxxxxxxxxx>
cc:
From: Nick Edgar <Nick_Edgar@xxxxxxxxxx>
Subject: Re: [platform-ui-dev] [CN] Updates for the Common Navigator in
Platform 3.2
Michael,
For point (4), the popup menu id is currently declared as part of the
<viewerContentBinding> element. Since there can be multiple such bindings
for a given viewer instance, it seems like it would be possible to declare
multiple menu ids, which is probably not what we want. It seems like we
want separate elements: <viewer> for declaring the viewer and properties
on it, like the menu id, and <viewerContentBinding> for associating
content extensions with the viewer.
Nick
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev