| Re: [ide-dev] Some Infos About Oomph |
|
Thanks Eike for this details. Based on your explanation, I have a
few questions/comments. I imagine that we all agree that end-users downloading Eclipse IDE for the first time won't want nor be able to define what they want in any language. So that's not something they should see or care about, it's more an technical internal choice. What's the workflow for new users? Shipping a minimal Oomph-capable RCP instead of EPP packages, and this minimal app would start a wizard to help users to define what they want and then provision the IDE? Is Oomph able to listen to "structural" IDE actions (such as addition of some new feature or setting of a global preference) and to maintain a "current" profile according to it? For example, assuming I install an IDE provisioned by Oomph, and then install e4 Tools in it; then can I export and backup a profile that automatically contains my initial IDE + the addition of e4 tools? And then can I either re-provision a new IDE or an existing one with the profile definition I exported? |