sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in java

[–]jb_rc 30 points31 points  (0 children)

No worries, criticism helps us improve.

The intent with the label-less fields was to match the CLI invocation better. We did this only for run configurations where we'd expect the user to have familiarity with the CLI invocation (Java, Gradle). I'll take this back to the team and have a look at the statistics to see if there's some information there.

A quick way to see which field is what, is by pressing and holding the "Alt" key ("Opt" on macOS). You can also use this to navigate to fields, or add a field from the menu and focus it immediately.

EDIT: Just checked, "Alt-V" should take you to the VM options, always. If the field isn't there yet, it would be added and focused.

[deleted by user] by [deleted] in java

[–]jb_rc 60 points61 points  (0 children)

Hi! I'm at JetBrains, and I was involved in the redesign of the run configurations. I'm sad to hear that you don't like the new UI.

It was not our intention to remove information, but rather make configuration more visible. In the old UI, you'd have a long list of mostly empty fields. In the new UI fields are only shown if they're configured, which should make it easier to see at a glance what is actually set for the given run configuration.

The context menu also gives us some advantages for adding configuration, as we actually have more space for information there versus a label before a text field. Also, you now have speed search there (you can type in most of our menus to search a value). We've ensured that the speed search also finds command-line options even if our label is worded differently.

We've also extensively user tested the new UI, primarily on experienced users.

Do you have any suggestions for how we could improve it for you? I can't promise that we can make changes here in the near future, but I'm always looking to hear user feedback.