|Re: [ide-dev] Some Infos About Oomph|
On 01/28/2015 08:39 PM, Doug Schaefer wrote:
I agree with Doug.
I don't think people want to deal with multiple instances of their IDE, they want only one, which adapts to the current activity to show relevant stuff. We have perspectives for that in Eclipse IDE, and if you look at reports from new enthusiast Eclipse users, that's something they love.
All due respect to Oomph initiative on that point, I don't believe that end-users want to be able to provision multiple IDEs, or want multiple IDEs in general. Defining and maintaining one IDE per project or language is more something that project teams might like in order to make sure their users get the right stuff, but it's not an end-user's dream.
IMO, giving flexibility is "just" a matter of giving an introduction to the Eclipse release train and marketplace when user start IDE for the first time. An introduction video on the welcome page or a wizard with screenshots of how to browse the release train and marketplace might be sufficient. Then suggesting users some automated actions (such as "Do you want to install your Marketplace favourites in your IDE") would be nice. I don't think the installer as it is now would help users to know better what they want and what's available.
Oomph profiles are interesting, but since Oomph is targeting project teams who want to define a project-specific IDEs (including SCM repos, target-platforms and other, that cannot be packaged properly as RCP), I have the feeling that it's an overkill technology for the goal of providing easier 1st experience with the "generic" Eclipse IDE.
Back to the top