Must everything be modal?

Hi,

Is it really a KO requirement that all the Settings dialogs/(and children dialogs) to be
modal?

E.g. one big inconvenient is when working on 'file templates':
In this case it would be very practical to be able to open files for consequent copy and paste, or
when pressing "Apply" to be able to access the new menu, to test if what's generated is OK(and not
for a simple coma or semicolon to close all popup windows and to reopen all again).

Another example is the "errors". It has many settings that would improve productivity, but most of
the users don't use them (only the default scheme) because it's very complicated to check them:
Usually one would have a test file and change settings to see how/if they apply, but to reopen/close
all the modal dialogs again and again it's just too much for 'fine tunning' of one project.

I can think that this the same for many other settings where the user would need to access the IDE
while changing some of the settings (because these settings are not just a simple checkbox).


Thanks in advance,

Ahmed.

4 comments

+1, that should go on the list of usability improvements.

Thanks
R

0

How about making them dockable as well?

For example, have the settings dialog dockable so that you don't have to
move things around.

Amnon

Ahmed Mohombe wrote:

Hi,

Is it really a KO requirement that all the Settings dialogs/(and
children dialogs) to be
modal?

E.g. one big inconvenient is when working on 'file templates':
In this case it would be very practical to be able to open files for
consequent copy and paste, or
when pressing "Apply" to be able to access the new menu, to test if
what's generated is OK(and not
for a simple coma or semicolon to close all popup windows and to reopen
all again).

Another example is the "errors". It has many settings that would improve
productivity, but most of
the users don't use them (only the default scheme) because it's very
complicated to check them:
Usually one would have a test file and change settings to see how/if
they apply, but to reopen/close all the modal dialogs again and again
it's just too much for 'fine tunning' of one project.

I can think that this the same for many other settings where the user
would need to access the IDE while changing some of the settings
(because these settings are not just a simple checkbox).


Thanks in advance,

Ahmed.

0

Is it really a KO requirement that all the Settings dialogs/(and
children dialogs) to be
modal?

This also applies to the Help Window when not starting it from the menu, but
from some other dialog/joptionpane that has a help button:

- it's a pain that the user can't see the the help (and maybe follow some steps
from the help and do them at same time in the IDE), because one needs to close the
help since it's modal - to be able to do something.

Several newbies/students that I gave IDEA to learn complained about this problem.

Even more, I think this kind of behavior makes the Help almost useless, and
is very negative for the adoption of IntelliJ by new users.

Thanks in advance,

Ahmed.

0

Agreed.

As the matter of fact we've decided to move out of using JavaHelp so hopefully
we'll be able to deliver more usable stuff here.

-


Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>> Is it really a KO requirement that all the Settings dialogs/(and
>> children dialogs) to be
>> modal?

This also applies to the Help Window when not starting it from the
menu, but from some other dialog/joptionpane that has a help button:

- it's a pain that the user can't see the the help (and maybe follow
some steps from the help and do them at same time in the IDE), because
one needs to close the help since it's modal - to be able to do
something.

Several newbies/students that I gave IDEA to learn complained about
this problem.

Even more, I think this kind of behavior makes the Help almost
useless, and is very negative for the adoption of IntelliJ by new
users.

Thanks in advance,

Ahmed.



0

Please sign in to leave a comment.