The intention is that the UI would be more general and could be used in
RCP apps.
To support this concept, most of the pieces actually live in
org.eclipse.equinox.prov.ui.
The sdk part is simply the plugin that registers the menu command, puts
the UI in a dialog, and uses the "feature" terminology. It should remain
pretty small, mostly composing the UI from prebuilt pieces.
So, for example, an RCP app could use the same UI objects, launching the
UI differently (different menu or dialog, or putting it in the
preferences, or whatever) and it could use different terminology, like
"add-on".
susan
Jeff McAffer <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
08/18/2007 04:39 PM
Please respond to Equinox development mailing list
To: Equinox development mailing list <[email protected]>
cc:
Subject: Re: [equinox-dev] [prov] new UI project in CVS
This is great. Is the UI proposed specific to the SDK? or tooling in
general? That is, would you envision this UI used in an RCP application?
Perhaps something more like prov.ui.user (in contrast to prov.ui.admin).
Jeff
Susan M Franklin <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
08/18/2007 06:12 PM
Please respond to
Equinox development mailing list <[email protected]>
To
[email protected]
cc
Subject
[equinox-dev] [prov] new UI project in CVS
There is a new UI project,
org.eclipse.equinox.prov.ui.sdk
This project will contain the UI for the "update manager replacement UI."
It currently contains a placeholder contribution and dialog, but you will
see it evolving over the next couple of weeks. The split of the projects
is done to separate shared provisioning UI stuff from any particular
instance of a UI.
org.eclipse.equinox.prov.ui - contains the shared stuff
org.eclipse.equinox.prov.ui.sdk - contains the update manager replacement
UI. You'll see terminology such as "feature" etc. used in this UI...
org.eclipse.equinox.prov.ui.admin - remains the admin or developer UI,
where you'll see terminology such as "IU", "Profile," etc.
org.eclipse.equinox.prov.ui.rcp - is the rcp version of the above.
If you are self hosting, then by default you'll have access to both UI's.
You can operate the admin UI from the provisioning perspective, and you
can play with the SDK UI by going to Help>Software Updates (Incubation).
If you don't want the clutter of the multiple UI's, you can always
deselect the UI project that you don't want to see from the workspace
plug-ins that are loaded from your launch config.
I've updated the project sets and the map file. I apologize if there is
anything else I should have updated that I've forgotten...
susan_______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev
