Re: [platform-ui-dev] Component framework proposal

[Randy Hudson <hudsonr@xxxxxxxxxx>]

Some ?s:

How is a legacy view (for example the
PropertiesView in 3.0) going to work with a multipage editor written using
this new proposal?  The legacy view relies on active part notification.
 It's not clear how changing pages in a multipage editor is going
to notify this event, if the pages aren't even IEditor/WorkbenchParts.

setFocus() is too simple of an example
for the multiplex case.  What about keybindings contexts, registered
actions, selection providers, etc.?  Is the goal to support nesting
of these new Components, or nesting of existing Views/Editors?

-randy

Mike Wilson <Mike_Wilson@xxxxxxxxxx>
Sent by: platform-ui-dev-admin@xxxxxxxxxxx

11/03/2004 09:34 AM

Please respond to
platform-ui-dev

To	platform-ui-dev@xxxxxxxxxxx
cc
Subject	Re: [platform-ui-dev] Component framework proposal

See markup in red. Come chat if anything isn't clear.



McQ.




Stefan Xenos/Ottawa/IBM@IBMCA 
Sent by: platform-ui-dev-admin@xxxxxxxxxxx
11/02/04 18:03
Please respond to
platform-ui-dev


To
platform-ui-dev@xxxxxxxxxxx
cc

Subject
[platform-ui-dev] Component framework proposal







The component framework proposal is now available online. 

This is part of the spec for the workbench part API in Eclipse 3.1, 
intended to support easier nesting and reuse of UI components. 

http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-ui-home/components-proposal/ComponentFrameworkProposal.html


  - Stefan
[attachment "Component Framework proposal.html" deleted by Randy
Hudson/Raleigh/IBM]