Community
Participate
Working Groups
In working through visual design issues for e4, we constantly have to think about the existing user preferences that affect how things look. Whether these are new preferences, or existing ones, it might be useful to group some of these preferences into overall "thematic" preferences such as "Understated" - a decluttered and simplified UI The challenge of course, is honoring the user's existing choices while also teaching them how to get the new look. Or maybe for the 4.0 workbench we have more leeway in actually changing the defaults? An interesting exercise would be to go through all the IDE preferences and understand how some of them might map into such a theme. For example, General->Appearance-> tab positions and perspective switcher location Editors->Show Multiple Editor Tabs General->Appearance->Label Decorations Perspectives->Hide Empty FastView Bar We are also considering new preferences that would help enhance and/or simplify the look, such as - the ability to turn off the view and editor tab icons - set a background image for the workbench Or even selective changes to existing preferences. For example, if the CVS sharing decorator showed only on the project and not every single resource inside, that would reduce a lot of clutter.
On the e4 call, we discussed that having user control of something like "declutter" should just be considered as part of the default stylesheet, and if you like the clutter, go back to the "classic" stylesheet. In other words, you can't have "the new look but with view icons and tabs on bottom." McQ believes that the solution to "users shouldn't have to hack CSS" should be "better CSS editors."
As someone who runs a project providing a CSS editor, I naturally have to ask, "which one are they using now?" and "is this an offer to help improve ours?"
(In reply to comment #2) > As someone who runs a project providing a CSS editor, I naturally have to ask, > "which one are they using now?" and "is this an offer to help improve ours?" ;-) From the standpoint of the Eclipse SDK end user, they are not using any editor currently. We provide end user prefs for things like "show tabs on the bottom" or "show editor tabs", etc. e4 CSS styling will provide much greater flexibility in the presentation of the workbench, so the question was what users who don't necessarily know/edit CSS will do to be able to make minor adjustments to the look and feel. I'm not sure of the answer here yet - what kind of editor makes sense...
Removing outdated target milestone.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
