Difference between revisions of "GIMP UI Redesign"

From GIMP GUI Redesign
Jump to: navigation, search
(team)
Line 9: Line 9:
 
* kate price, interaction architect ([http://mmiworks.net m+mi works])
 
* kate price, interaction architect ([http://mmiworks.net m+mi works])
 
* Tobias Ehni, usability consultant
 
* Tobias Ehni, usability consultant
 +
* Dominique Schmidt, associate interaction architect
  
 
===honour list===
 
===honour list===
Line 27: Line 28:
 
* GIMP is user-configurable to automate repetitive tasks;
 
* GIMP is user-configurable to automate repetitive tasks;
 
* GIMP is easily user-extendable, by ‘one-click’ installation of plug-ins.
 
* GIMP is easily user-extendable, by ‘one-click’ installation of plug-ins.
 +
 +
==functionality overview==
 +
 +
To design something, you need to know ''everything'' it is suppose to do. At the beginning of this project a short, sharp [[media:GIMP_functionality.pdf‎ | functionality overview]] was made, based on version 2.3.11 (extra kudos to Kamila for all that work).
  
 
==[[User Scenarios | user scenarios]]==
 
==[[User Scenarios | user scenarios]]==
Line 32: Line 37:
 
These [[User Scenarios]] are used in the GIMP redesign project. They are the result  
 
These [[User Scenarios]] are used in the GIMP redesign project. They are the result  
 
of workplace observations and a weekend workshop with the GIMP team.
 
of workplace observations and a weekend workshop with the GIMP team.
 
==functionality overview==
 
 
To design something, you need to know ''everything'' it is suppose to do. At the beginning of this project a short, sharp [[media:GIMP_functionality.pdf‎ | functionality overview]] was made, based on version 2.3.11 (extra kudos to Kamila for all that work).
 
  
 
==[[Expert Evaluation Notes | expert evaluation notes]]==
 
==[[Expert Evaluation Notes | expert evaluation notes]]==

Revision as of 10:58, 19 December 2011

got ideas?

Join the GIMP UI brainstorm, the channel for everybody to contribute to this process. It is moderated by our team, we ‘listen’ to what you show us and broaden our horizons.

team

The team that is working on the UI redesign project consists of:

  • peter sikking, principal interaction architect, m+mi works—blog, on GIMP
  • kate price, interaction architect (m+mi works)
  • Tobias Ehni, usability consultant
  • Dominique Schmidt, associate interaction architect

honour list

We thank these previous team members for their valuable contributions:

  • Kamila Giedrojć, associate interaction architect —portfolio
  • Ellen Reitmayr, usability consultant —website

product vision

Ultimately, every decision taken by our UI team is about realising the product vision. At the LGM 2006, peter sikking held a workshop with the GIMP team, and helped them to formulated their product vision:

  • GIMP is Free Software;
  • GIMP is a high-end photo manipulation application and supports creating original art from images;
  • GIMP is a high-end application for producing icons, graphical elements of web pages and art for user interface elements;
  • GIMP is a platform for programming cutting-edge image processing algorithms, by scientists and artists;
  • GIMP is user-configurable to automate repetitive tasks;
  • GIMP is easily user-extendable, by ‘one-click’ installation of plug-ins.

functionality overview

To design something, you need to know everything it is suppose to do. At the beginning of this project a short, sharp functionality overview was made, based on version 2.3.11 (extra kudos to Kamila for all that work).

user scenarios

These User Scenarios are used in the GIMP redesign project. They are the result of workplace observations and a weekend workshop with the GIMP team.

expert evaluation notes

We spent a month and a half evaluating GIMP. Enjoy reading the raw Expert Evaluation Notes.

analysis

Our analysis its the result all of our work on GIMP up to now, and shows the way forward for each aspect of GIMP UI, in the form of solution models.

usability

Tobi's work in progress to further improve the usability of GIMP.

work in progress

Notes, tables, sketches showing work in progress towards detailed specification.

specifications

Solution models get further developed into UI specifications, ready for implementation.