[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [platform-ui-dev] Context menu on Project Navigator not really contextual
|
Doug, I see two separate tasks;
- "Decide what you want beginners see": There's more than one type of 'beginner' depending on what they're doing (e.g. a student learning java and a professional learning eclipse...). This is gonna be tough to do through analysis alone. Given the time / effort it took to change a single preference it's also likely going to take a while...but it's necessary.
- and -
- "make it so": Once you've defined what the correct items getting the UI to actually show that state...
My original posting was related to the second task, providing the mechanism to allow *any* subset of an existing install's contributions to be filtered discretely. My mechanism is predicated on the reality that was hammered into me doing Eclipse 4; there must be *no* required changes to the existing projects. If it were possible to do so we'd have made all the projects move away from 'ActionSets' and over to the Commands, saving a ton of work (for us).
Onwards,
Eric
Doug Schaefer ---07/03/2014 12:26:07 PM---Decide what you want beginners see and make it so. Decide how they should go about things and make t
![]()
| ![]()
Doug Schaefer <dschaefer@xxxxxxx> |
![]()
| ![]()
"Eclipse Platform UI component developers list." <platform-ui-dev@xxxxxxxxxxx>, |
![]()
| ![]()
07/03/2014 12:26 PM |
![]()
| ![]()
Re: [platform-ui-dev] Context menu on Project Navigator not really contextual |
![]()
| ![]()
platform-ui-dev-bounces@xxxxxxxxxxx |
Decide what you want beginners see and make it so. Decide how they should go about things and make those paths easiest. But, really you need to look at these things on a case by case basis. You can't generalize.
From: platform-ui-dev-bounces@xxxxxxxxxxx [platform-ui-dev-bounces@xxxxxxxxxxx] on behalf of Eric Moffatt [emoffatt@xxxxxxxxxx]
Sent: Thursday, July 03, 2014 11:52 AM
To: Eclipse Platform UI component developers list.
Subject: Re: [platform-ui-dev] Context menu on Project Navigator not really contextual
I'm also in full agreement with Mickael, don't get me wrong. It's more that the CPD fixes / enhancements are at least *definable* so the work can start now.
So how do we produce the correct 'defaults' ? The specific set of items needed for one workflow may not fit someone who's coming from a different direction so who wins ? If we produce defaults for both then we're back to having way too many packages...
For my money I still think that we need to (at minimum) allow a 'packager' to provide a package level 'plugin.xml' that *overrides* the ones in the packages. This would allow someone to really fine-tune what the user is exposed to regardless of the plugin structure of the packages being consumed.
At the far end of this would be a way to allow users to select one from a community based site (Market?). Allowing a variety of choices this way has seen some success in the IDE already (the various theme sites); it provides at least a common location to go to access a setup tuned to their specific needs (this could even be produced by a team's manager / leader to streamline their team's workflows to a desired path).
Eric
Lars Vogel ---07/03/2014 11:26:48 AM---I agree with Mickael, good defaults are important. @Eric, for 4.4 I implemented your suggestion to h
| ![]()
Lars Vogel <lars.vogel@xxxxxxxxx> |
| ![]()
"Eclipse Platform UI component developers list." <platform-ui-dev@xxxxxxxxxxx>, |
| ![]()
07/03/2014 11:26 AM |
| ![]()
Re: [platform-ui-dev] Context menu on Project Navigator not really contextual |
| ![]()
platform-ui-dev-bounces@xxxxxxxxxxx |
I agree with Mickael, good defaults are important.
@Eric, for 4.4 I implemented your suggestion to hide tool controls and toolbars via the IPresentation.Explicitely-Hidden model tag. To support your idea, I think we should extend that for menus and menu entries. And adjust CPD to support this flag.
Am 03.07.2014 17:00 schrieb "Mickael Istria" <mistria@xxxxxxxxxx>:
On 07/03/2014 04:00 PM, Eric Moffatt wrote:
We need some way to allow users to filter unwanted entries
Users want something that looks good out-of-the-box. They don't want to have to customize things, and many user will prefer applications that have the best defaults over those that are the most configurable.
IMO, it would be more helpful to provide the ability to customize default menus for package providers. Is it already possible to customize menus through preferences and plugin_customization.ini files?
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev

