The configuration screen

Hi all,

My configuration just went berserk. All the icons are missing, and it's a big mess now, which sort of resembles the Eclipse/Netbeans configuration dialog. Is this a bug in the new EAP? All the tabs are gone, all icons are missing, some treenodes are collapsable, some aren't. I guess it's a known bug, but will this be fixed for the final version?

Erik

(I've attached the picture....)



Attachment(s):
Picture 1.png
21 comments
Comment actions Permalink

No, this is not a bug. This is how the configuration screen will look like in the 8.0 release.



Once, Intellij 3 I believe, used to be on Sun site as a state of the art Swing implementation example.
But times, they are changing ;-)..oh well..

0
Comment actions Permalink

Hello Erik,

No, this is not a bug. This is how the configuration screen will look like
in the 8.0 release.

Hi all,

My configuration just went berserk. All the icons are missing, and
it's a big mess now, which sort of resembles the Eclipse/Netbeans
configuration dialog. Is this a bug in the new EAP? All the tabs are
gone, all icons are missing, some treenodes are collapsable, some
aren't. I guess it's a known bug, but will this be fixed for the final
version?

Erik

(I've attached the picture....)

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Hello M. J. Milicevic,

>>

>> No, this is not a bug. This is how the configuration screen will look
>> like in the 8.0 release.

Once, Intellij 3 I believe, used to be on Sun site as a state of the
art Swing implementation example. But times, they are changing ;-)..oh
well..


We would very much like to hear specific and actionable feedback concerning
the new UI, rather than complaints about how the grass used to be greener
in the days of yore :)

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

>We would very much like to hear specific and actionable feedback concerning
>the new UI, rather than complaints about how the grass used to be greener
>in the days of yore

well, actually I did in one of the JIRA issues where some people suggested to add icons to stuff etc.
I was so disappointed with this new look & feel that I even left quite negative maybe bit rude comment.
Now, if you think of it, if someone thinks that this is a bug, than it should ring some bells.

One thing I can tell about it is that: there is a lot of information displayed to you and there is no easy way to pinpoint something.

For example, with icons, you need some time to learn them but after a while you can easily find what you are looking for.

My difficulty with this new interface is that I need to read each of the labels. Note that search box only filters content of the tabs, it doesn't look at the menu tree for example (I should file this as a bug).
Now, it'll take me some to figure out where those positions are, but once I'll install a plug-in which will add some entry somewhere inbetween and there we go again.

Also, we are few weeks before release date: this should've been implemented long before so you get some feedback..right now it's fact of life. I'll get used to it, but happy I am not..;-)

0
Comment actions Permalink

oh yeah. web forum/newsgroup is again out of synch..

0
Comment actions Permalink

On 2008-10-31 06:06:55 +1300, Dmitry Jemerov <yole@jetbrains.com> said:

We would very much like to hear specific and actionable feedback
concerning the new UI, rather than complaints about how the grass used
to be greener in the days of yore :)


I read that as "the days of yole" ;)

My initial opinion is I like the direction its heading, as the number
on configurable options is growing and growing and growing - but it
looks like someone forgot to turn on the icons next to each entry
(although, not having to make an icon for every option configuration
sure makes things easier on everyone).

When module configuration was split out from the main configuration the
other day that reallly confused the heck out of me for a moment - and I
think that might be the biggest complaints/comments about it (thou
again, I understand why its moved out).

I can't really pin my fingers on yet - but its missing 'something'.
The filtering search is gone afaik "what options do something with xxx"
(unless it just moved somewhere where I never saw it).

Mark


0
Comment actions Permalink

Hello Mark,

My initial opinion is I like the direction its heading, as the number
on configurable options is growing and growing and growing - but it
looks like someone forgot to turn on the icons next to each entry
(although, not having to make an icon for every option configuration
sure makes things easier on everyone).


Once again, we'll see. Maybe we'll put the icons back.

I can't really pin my fingers on yet - but its missing 'something'.
The filtering search is gone afaik "what options do something with
xxx" (unless it just moved somewhere where I never saw it).


The search is still there. Just start typing.

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Hello M. J. Milicevic,

For example, with icons, you need some time to learn them but after a
while you can easily find what you are looking for.


Again, it's a problem of scaling. Large icons are indeed fairly easy to recognize,
but there's only so many of them that you can fit in the UI. And it's not
clear whether adding small icons to the new UI will actually help things
or not.

My difficulty with this new interface is that I need to read each of
the labels. Note that search box only filters content of the tabs, it
doesn't look at the menu tree for example (I should file this as a
bug).


Please tell exactly which setting is not findable in this way. This seems
to work fine in my experiments.

Now, it'll take me some to figure out where those positions are, but
once I'll install a plug-in which will add some entry somewhere
inbetween and there we go again.

Also, we are few weeks before release date: this should've been
implemented long before so you get some feedback..right now it's fact
of life. I'll get used to it, but happy I am not..;-)


Indeed it would have been great if we had had the possibility of implementing
and releasing the new UI earlier. Unfortunately we hadn't.

And of course, it's very likely that the UI will be further improved in 8.0.x
updates.

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

I think a good configuration option would be:
True/False - Use the old configuration screen :)

I think the old screen had more Pizazz, but was potentially harder to find stuff without using the search.

The main problem I have with the new screen is that with 8975 and 8987 I can't open it!
I get an error every time!

I maned to get to the plugins only via the link on the welcome screen!

0
Comment actions Permalink

Hello Dmitry,

DJ> We would very much like to hear specific and actionable feedback
DJ> concerning the new UI,

I, too, thought that was an intermediary state of the UI, so I didn't complain.
But if you say that's supposed to be the final version...

Here are my comments:
- it looks unfinished (the lack of icons make it even more so)
- it's inconsitent:

  • some of the views get a list of entries in the tree view - like version

control, some still have tabs - global code style

  • some of the nodes have their own views, some are only there for aggregating

other subnodes. One will have to click all over the place to find things
(or not)
- search is not that intuitive anymore (it's hidden by default, the previous
highlighting looked much more obvious than the current filtering)
- while I can see how it can help with scaling, the sheer volume of entries
at this point makes it very hard to read, to start with. A lot of configuration
fragments got their own entries in the tree structure (see version control,
for instance) only to display 3 lines on a big, empty, panel.

I really don't get it... If you wanted a tree type view, what was wrong with
the old classical view of the config pane? This one does not bring anything
the classical view did not have, but just breaks the items into smaller entries
(a questionable initiative, if you ask me) and presents them in an uglier
and less intuitive fashion.

Just my 2c,
Andrei


0
Comment actions Permalink

Hi Dmitry,

I already was a bit afraid of that. That's a real disappointment. The previous option screen looked clean, this just looks like a bunch of option which somehow are configurable. The new approach (IMO) also stimulates adding more and more options without giving it real proper thought. The same for the 'search' in the option screen... why do you need a search option there. Wouldn't a categorized overview of the options be much better, with the re-addition of the icons. Maybe the icons can be smaller, but the long list was not really a problem to me. Maybe a list of categories could look like:

Appearance
-
Code
- TODO
- Intentions
Customize/Personal
- Keymap
- Templates
- Menus & Toolbars
- Quick lists
External
- Webbrowsers
- External tools
- External Diff tools
- HTTP Proxy
- Path variables

Maybe it makes no sense, but I'm really unhappy about the new configuration screen, and it was a bit shocking (sorry for the expression) to see this new screen. I really liked the icons and the always fresh look (I know that's personal) of the old screen!

0
Comment actions Permalink

Hello opticyclic,

I think a good configuration option would be: True/False - Use the old
configuration screen :)


Unfortunately this is not possible. We made many changes to individual configuration
panels that won't work well with the old settings layout.

I think the old screen had more Pizazz, but was potentially harder to
find stuff without using the search.

The main problem I have with the new screen is that with 8975 and 8987
I can't open it! I get an error every time!


What error exactly?

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Hello Andrei,

Hello Dmitry,

DJ>> We would very much like to hear specific and actionable feedback
DJ>> concerning the new UI,
DJ>>

I, too, thought that was an intermediary state of the UI, so I didn't
complain. But if you say that's supposed to be the final version...

Here are my comments:
- it looks unfinished (the lack of icons make it even more so)


There will be some additional UI improvements in the final 8.0 release.

- it's inconsitent:

  • some of the views get a list of entries in the tree view - like

version
control, some still have tabs - global code style


The code style configurable has already been redesigned similarly to Colors
and Fonts, so it's also a list of tree nodes now.

  • some of the nodes have their own views, some are only there for aggregating

other subnodes. One will have to click all over the place to find
things (or not)


We're getting rid of aggregation-only nodes as much as we can.

- search is not that intuitive anymore (it's hidden by default, the
previous highlighting looked much more obvious than the current filtering)


We'll discuss this - maybe the search will be visible by default once again.

- while I can see how it can help with scaling, the sheer volume of entries
at this point makes it very hard to read, to start with. A lot of configuration
fragments got their own entries in the tree structure (see version
control, for instance) only to display 3 lines on a big, empty, panel.


It's a question of balance, and it's true that we may have shifted it a bit
too far in the opposite direction. :) I think that no one will argue that
many of the options screens in IDEA 7 (editor, debugger) were very much overloaded.

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

In the newest builds the worst issues with the new settings dialog have been addressed I see. I am starting to like the new "feel", already I can find some settings much faster than with the old icon based settings layout. Code style settings are much more accessible now.

The "look" of the settings tree can still be improved a bit I think (see attached screen shot).

The label at the top of the tree is currently unreadable, and there is no way to make it completely visible. It should be left aligned and after hovering over it with the mouse a tool tip with the complete text could pop up. Alternatively it could be split over two lines.

Also the tree icons (the little pluses and minuses) could use more white space. They are too close to the left border and too close to the text, giving the tree a crowded look.

Bas



Attachment(s):
new_settings.png
0
Comment actions Permalink

I've used the "Blame IDEA Core" button to submit it several times, but I'm not sure where it gets uploaded to so that I can track it.
The most recent submission said "Submitted as 126522."


Error during dispatching of java.awt.event.MouseEvent[MOUSE_RELEASED,(733,63),absolute(725,-969),button=1,modifiers=Button1,clickCount=1] on frame1
java.lang.NullPointerException
at java.lang.String$CaseInsensitiveComparator.compare(String.java:1218)
at java.lang.String$CaseInsensitiveComparator.compare(String.java:1212)
at java.lang.String.compareToIgnoreCase(String.java:1259)
at com.intellij.openapi.options.newEditor.OptionsTree$8.compare(OptionsTree.java:1)
at com.intellij.openapi.options.newEditor.OptionsTree$8.compare(OptionsTree.java)
at java.util.Arrays.mergeSort(Arrays.java:1270)
at java.util.Arrays.mergeSort(Arrays.java:1282)
at java.util.Arrays.mergeSort(Arrays.java:1282)
at java.util.Arrays.sort(Arrays.java:1210)
at java.util.Collections.sort(Collections.java:159)
at com.intellij.openapi.options.newEditor.OptionsTree.a(OptionsTree.java:42)
at com.intellij.openapi.options.newEditor.OptionsTree.access$300(OptionsTree.java:33)
at com.intellij.openapi.options.newEditor.OptionsTree$Root.a(OptionsTree.java:0)
at com.intellij.openapi.options.newEditor.OptionsTree$Root.buildChildren(OptionsTree.java:13)
at com.intellij.ui.treeStructure.CachingSimpleNode.getChildren(CachingSimpleNode.java:38)
at com.intellij.ui.treeStructure.SimpleTreeStructure.getChildElements(SimpleTreeStructure.java:25)
at com.intellij.ui.treeStructure.filtered.FilteringTreeStructure.fillChildren(FilteringTreeStructure.java:45)
at com.intellij.ui.treeStructure.filtered.FilteringTreeStructure.refilter(FilteringTreeStructure.java:39)
at com.intellij.ui.treeStructure.filtered.FilteringTreeStructure.(FilteringTreeStructure.java:33) at com.intellij.ui.treeStructure.filtered.FilteringTreeBuilder.(FilteringTreeBuilder.java:35) at com.intellij.openapi.options.newEditor.OptionsTree$3.(OptionsTree.java:1) at com.intellij.openapi.options.newEditor.OptionsTree.(OptionsTree.java:98) at com.intellij.openapi.options.newEditor.OptionsEditor$2.(OptionsEditor.java:5) at com.intellij.openapi.options.newEditor.OptionsEditor.(OptionsEditor.java:165) at com.intellij.openapi.options.newEditor.OptionsEditorDialog.createCenterPanel(OptionsEditorDialog.java:24) at com.intellij.openapi.ui.DialogWrapper.init(DialogWrapper.java:662) at com.intellij.openapi.options.newEditor.OptionsEditorDialog.]]>(OptionsEditorDialog.java:42)
at com.intellij.ide.actions.ShowSettingsUtilImpl.a(ShowSettingsUtilImpl.java:37)
at com.intellij.ide.actions.ShowSettingsUtilImpl.showSettingsDialog(ShowSettingsUtilImpl.java:17)
at com.intellij.ide.actions.ShowSettingsAction.actionPerformed(ShowSettingsAction.java:5)
at com.intellij.openapi.actionSystem.impl.ActionButton.a(ActionButton.java:61)
at com.intellij.openapi.actionSystem.impl.ActionButton.a(ActionButton.java:89)
at com.intellij.openapi.actionSystem.impl.ActionButton.processMouseEvent(ActionButton.java:23)
at java.awt.Component.processEvent(Component.java:5899)
at java.awt.Container.processEvent(Container.java:2023)
at java.awt.Component.dispatchEventImpl(Component.java:4501)
at java.awt.Container.dispatchEventImpl(Container.java:2081)
at java.awt.Component.dispatchEvent(Component.java:4331)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4301)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3965)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3895)
at java.awt.Container.dispatchEventImpl(Container.java:2067)
at java.awt.Window.dispatchEventImpl(Window.java:2458)
at java.awt.Component.dispatchEvent(Component.java:4331)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
at com.intellij.ide.IdeEventQueue.c(IdeEventQueue.java:35)
at com.intellij.ide.IdeEventQueue.b(IdeEventQueue.java:223)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:217)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)

0
Comment actions Permalink

My two cents: I like how "Fonts" is now separate from "Colors", but apparently the font defined in "Colors" still take precedence when changing the color config through quick switch.

0
Comment actions Permalink

Hello Dmitry,

DJ> There will be some additional UI improvements in the final 8.0
DJ> release.

Glad to hear it. And please consider bringing the icons back, somehow (if
only for the head entries). If you group the installed plugins under one
entry (as opposed to letting each one of them at the root level) than you
might not even have to deal with icons for them. I guess that's the main
scalability problem you had on the Selena settings dialog, right?

DJ> The code style configurable has already been redesigned similarly to
DJ> Colors and Fonts, so it's also a list of tree nodes now.
DJ>

Again, can you somehow indicate what's a subsection of a config and what's
on it's own (icons might be one indication). I don't find that the tree indentation
is really cutting it, it's hard to parse a long list of items without some
anchor points.

DJ> We're getting rid of aggregation-only nodes as much as we can.

OK, I'll wait and see, then. :)

DJ> We'll discuss this - maybe the search will be visible by default
DJ> once again.

The more you do to draw attention to it, the better. I have a few colleagues
migrating to IDEA (7) from Eclipse these days and I still have to point the
search functionality out to them. Hiding it will guarantee new users miss
it for sure.

DJ> It's a question of balance, and it's true that we may have shifted
DJ> it a bit too far in the opposite direction. :) I think that no one
DJ> will argue that many of the options screens in IDEA 7 (editor,
DJ> debugger) were very much overloaded.

They were overloaded, I give you that. However, if I wanted to configure
something and didn't know what exactly it was (or what it was called, rather),
I knew where I had to go. There was one place that I knew I could expect
to find things debugger related, and I went there.

I remember I had the same reaction when tabs started being put in place,
a while back. All of a sudden, searching for something became so much harder,
more clicks, more places to look for and go back to if scanned too quickly.

This is one thing I really hate about Eclipse. It's really hard to figure
something out if you don't know where it's placed. I think this dialog goes
in that direction. You shouldn't underestimate the need to find things out,
I've been using IDEA since version 2, and I know what kind of stuff it has
configurations for, but quite often I still have to search around to find
the place. Splitting a reasonalbly loaded pane into 3 lines subpanes will
definitely not help.

Best,
Andrei


0
Comment actions Permalink

Hello opticyclic,

I've used the "Blame IDEA Core" button to submit it several times, but
I'm not sure where it gets uploaded to so that I can track it.


Fixed. Thanks a lot for the heads up. :)

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Hi Dmitry,

One vote from me for the new UI. I like it - no joke. Please rethink the
structuring and put the usual search input field above the tree.

Tom

0
Comment actions Permalink

We would very much like to hear specific and actionable feedback concerning
the new UI

>

Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


Hello Dimitry,

I like the direction the new UI is heading in and can see the scalability benefits. Some feedback I'd give is this:

1) It might be nice to be able to completely collapse the major sections (IDE Settings and Project Settings). Not a huge thing, but I could see that helping someone to focus in on things a little better

2) I asked this question in a separate thread a few days ago, but have so far not gotten a response: Is there any chance that the Template Project Settings can be moved into the Settings dialog rather than being a separate window (and action to launch)? I've often found this awkward. And when I get new people to try IDEA, they often to not find this dialog. I've had a couple new users complain about having to constantly redo/repeat the same settings in new projects (until I point this dialog out to them). Given the scalability potential of the new settings layout, I think the Template Project Settings would fit in there fine, and it would be IMHO more intuitive to have all settings in one place.

Best Regards,
Mark Vedder

0
Comment actions Permalink

I'm OK with the new tree structure, but then I always liked the classic view rather than the icon grid. I like how everything is alphabetically ordered-- weren't things not in alphabetical order before?

I do think it looks plain without any icons. I wasn't a big fan of inventing icons just to have icons for every settings panel, but maybe you could at least show the icons which are used in other places e.g. debugger icon, mr. inspector icon, todo icon, etc. It helps to tie the settings to the part of the product which they apply to. It might look weird if some nodes have icons while some don't. Either that, or maybe you should display the icons on the settings panel themselves.

The biggest issue I have is that you have split project structure to a separate dialog. There seems to be some inconsistency. On "Settings" dialog you have Project Settings and IDE Settings- and on "Project Structure" dialog you have Project Settings and Platform Settings. My feeling is that Platform Settings should be in the "Settings" dialog. Then you can just remove Project Settings bar in "Project Structure" dialog. That would improve slightly, but still I am wondering why "Project Structure" has been split out when you still have Project Settings in the "Settings" dialog? Why not just have "Project Structure" under the Project Settings bar in "Settings" dialog?

I agree with Erik's comment that there needs to be some more organization to keep the list from getting too long. One thing in particular is I would like plugins that aren't installed by default to be shown separately at the bottom. I have "Dilbert Daily Strip" and that is showing up between "Debugger" and "Editor" nodes and I have "JFormDesigner" between "Intentions" and "Keymap". Put non-standard plugin settings at the bottom or under "Plugins" node. I think it will help to keep the core IDEA settings always in the same order.

0

Please sign in to leave a comment.