Difference between revisions of "Single-window mode specification"
From GIMP GUI Redesign
Line 5: | Line 5: | ||
Designing the single-window mode (swm) interaction solution boils down to the following tasks: | Designing the single-window mode (swm) interaction solution boils down to the following tasks: | ||
− | # understanding the user needs behind the '''huge''' request for single window and base the overall design on it; | + | # understanding the user needs behind the '''huge''' request for single-window and base the overall design on it; |
# design the switching that controls which is ''the'' current active image under swm; | # design the switching that controls which is ''the'' current active image under swm; | ||
# design the opening and closing of GIMP and image files under swm; | # design the opening and closing of GIMP and image files under swm; | ||
Line 11: | Line 11: | ||
# redesign docking and tearing off of dockable dialogs, and whole columns of them. | # redesign docking and tearing off of dockable dialogs, and whole columns of them. | ||
− | === understanding single window === | + | === understanding single-window === |
− | The interest from users is huge | + | The interest from (potential and ex-) GIMP users in single-window is huge, literally 100 time higher than any other GIMP topic. Absorbing and classifying all the input, we define the following '''user needs''' that drive this interest: |
; single application instance | ; single application instance | ||
− | : This is the user need to see the (usually single) GIMP application instance that is running represented as a single entity. e.g. one item in the ‘taskbar,’ only one menubar (not one | + | : This is the user need to see the (usually single) GIMP application instance that is running represented as a single entity. e.g. one item in the ‘taskbar,’ only one menubar (not one for every open file). |
; stop fighting window managers | ; stop fighting window managers | ||
− | : Users are fed up with GIMP dialogs getting lost under document windows. And with the ‘taskbar’ being stuffed with non-entities. This has a lot to do with | + | : Users are fed up with GIMP dialogs getting lost under document windows. And with the ‘taskbar’ being stuffed with non-entities. This has a lot to do with recalcitrant window managers and application–window manager communication on several platforms. All this cannot be ‘repaired’ bit by bit. Users see the magic bullet in stop fighting and going single-window. |
; single working plane | ; single working plane | ||
− | : This is the user need for a work surface where everything is GIMP, and only GIMP, to concentrate on | + | : This is the user need for a continuous work surface where everything is GIMP, and only GIMP, in order to concentrate on their work. It also is the need for an end to every GIMP window, toolbox and dialog floating around in the desktop window stack individually. |
'''Reminder''': the world is still a 50-50 place: 50% of users want to keep the current multi-window way, and the other 50% is looking forward to a single-window interface. | '''Reminder''': the world is still a 50-50 place: 50% of users want to keep the current multi-window way, and the other 50% is looking forward to a single-window interface. |
Revision as of 09:39, 5 May 2011
Contents
introduction
This is the specification for the single-window mode, in addition to the multi-window one.
analysis + design goals
Designing the single-window mode (swm) interaction solution boils down to the following tasks:
- understanding the user needs behind the huge request for single-window and base the overall design on it;
- design the switching that controls which is the current active image under swm;
- design the opening and closing of GIMP and image files under swm;
- design working side-by-side with several files under swm;
- redesign docking and tearing off of dockable dialogs, and whole columns of them.
understanding single-window
The interest from (potential and ex-) GIMP users in single-window is huge, literally 100 time higher than any other GIMP topic. Absorbing and classifying all the input, we define the following user needs that drive this interest:
- single application instance
- This is the user need to see the (usually single) GIMP application instance that is running represented as a single entity. e.g. one item in the ‘taskbar,’ only one menubar (not one for every open file).
- stop fighting window managers
- Users are fed up with GIMP dialogs getting lost under document windows. And with the ‘taskbar’ being stuffed with non-entities. This has a lot to do with recalcitrant window managers and application–window manager communication on several platforms. All this cannot be ‘repaired’ bit by bit. Users see the magic bullet in stop fighting and going single-window.
- single working plane
- This is the user need for a continuous work surface where everything is GIMP, and only GIMP, in order to concentrate on their work. It also is the need for an end to every GIMP window, toolbox and dialog floating around in the desktop window stack individually.
Reminder: the world is still a 50-50 place: 50% of users want to keep the current multi-window way, and the other 50% is looking forward to a single-window interface.