Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Are too many packages actually hurting Eclipse?

On 07/30/2013 11:56 AM, Mickael Istria wrote:
On 07/30/2013 11:01 AM, Pascal Rapicault wrote:
- On first start, prompt the user with a customization wizard that let the user add more plugins to his Eclipse. For example, it
could ask questions about the language being used, the SCM, etc.
That would be an interesting approach and a good alternative to using installer: Ship a single vanilla Eclipse product, and have a
"your Eclipse top-ins" wizard opening p2-director on the release train + Market Place so that end-users could decide what they want
to install. The basics of an IDE configurations (dev language, frameworks, SCM, Mylyn & trackers...) could have a dedicated page.


Eclipse is excellent in providing composable and configurable tools.
It's just the selection from available options that seems to
overwhelm some people, so they end up with a setup that is no
good match for their needs.

I seem to see parallels between:
- which features / plugins do I install?
- what skin meets my sense of aesthetics and ergonomics?
- what preferences fit my working habits? (see earlier thread)

We, the providers, can only make guesses at what suits people,
but couldn't we make it easier for people to *share* their
collections / configurations? Easier in terms of 1-click
export & import, and easier in terms of a community place
where collections are uploaded / voted / ranked?

May be a bad idea, if thousands of people just drop their
preferences, how is Joe Programmer gonna find something
that's good for him? I don't know ...

Maybe we need some Code Recommenders technology to give
good advice during selection :)


Back to the top