|Re: [ui-best-practices-working-group] [ide-dev] Java IDEs comparison|
Copying the UX group as this crossed into determining what the user experience should be.
From: <ide-dev-bounces@xxxxxxxxxxx> on behalf of Mickael Istria <mistria@xxxxxxxxxx>
Reply-To: Discussions about the IDE <ide-dev@xxxxxxxxxxx>
Date: Thursday, September 22, 2016 at 1:30 PM
To: "ide-dev@xxxxxxxxxxx" <ide-dev@xxxxxxxxxxx>
Subject: Re: [ide-dev] Java IDEs comparison
While the preference recorder is a clever way to work around the problem, I’m not sure it’s what users are expecting. At least the version I saw of it, it should be recording all preferences without asking the user because as soon as you ask, the smart users realize it’s a workaround, the beginner users wonder why it’s asking.
We really should be storing workspace preferences globally. Then if you’re a super advanced user who wants different preferences per workspace, we can come up with a workaround for that.
If Oomph can do that, then great, but then we need to make sure all Eclipse IDEs (at eclipse and elsewhere) have Oomph in it. That is, it should be in the Platform.
Not sure that’s the right direction. Visual Studio Code, for example does have the concept of multiple “workspaces”. You open it up in a root directory and have have multiple instances of it open at different roots. Visual Studio has the concept of Solution which is similar. Xcode, mind you, does not and you open and close projects.
The main problem here is that java projects tend to be small and numerous and there’s just too much noise if you have your IDE checked out (like I do with Momentic’s 400 projects or so from all over the Eclipse ecosystem) and then want to work with an Android app project for example which would get lost in the noise.
But yes, workspaces are a problem it would be nice to understand the root cause of those user experience problems so we can come up with something really better.