Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ide-dev] A new survey

Agreed. And that is my point. This is the non-magical approach. Do it the
right way in the platform, not requiring a additional plug-in to be
installed to fix the platform¹s problems.

Unfortunately we are where we are. I don¹t have Oomph installed in my IDE
so I don¹t get the benefits of it¹s magic. When I did, it was shocked by
the UX. Presenting the internal IDs of preferences to the user who doesn¹t
have much hope of understanding what they mean is not what I was hoping to
introduce to new users. The correct way is to just do the right thing and
not bother the user with it unless they really want to.


On 2015-11-03, 3:05 AM, "ide-dev-bounces@xxxxxxxxxxx on behalf of Gunnar
Wagenknecht" <ide-dev-bounces@xxxxxxxxxxx on behalf of
gunnar@xxxxxxxxxxxxxxx> wrote:

>This has been discussed since 2004.
>I certainly would be interested in such a scope. Back in the days I
>thought of a "system" scope (like /etc/eclipse). But ~/.eclipse would be
>a great start. Having such a scope in Equinox would help for some RCP use
>Yes, adoption within the IDE is a separate topic. That's probably the
>reason why the discussion is not progressing. It's too much work to
>rework all the existing preferences. Oomph is a different approach but
>solves the problem in the IDE for me now.
>Gunnar Wagenknecht
>> Am 03.11.2015 um 06:55 schrieb Marcel Bruch
>> FWIW: I had that need to store some information in a user-scope like
>>ids, keys, etc. I¹ve reused the existing implementation to simulate that
>>user scope in $USER_HOME/.eclipse/. which suffices for my use case. If
>>there is no reasonable interest in offering such a scope in the
>>platform, that¹s fine.
>ide-dev mailing list
>To change your delivery options, retrieve your password, or unsubscribe
>from this list, visit

Back to the top