Difference between revisions of "GIMP UI Redesign"

From GIMP GUI Redesign
Jump to: navigation, search
 
(expert evaluation notes)
(36 intermediate revisions by 5 users not shown)
Line 1: Line 1:
==team==
+
==expert evaluation notes==
 
 
The GIMP project's User Interface is discussed in an open manner through [http://www.gimp.org/irc.html IRC] and a [https://mail.gnome.org/mailman/listinfo/gimp-gui-list dedicated mailing list], in collaboration with users, developers and designers.
 
 
 
The WIKI will contain the user interaction research results, and specifications coming out of our decisions.
 
Contact the GIMP developers on IRC (the user "ankh" is known to have an admin account) to get a login for the wiki.
 
 
 
Everybody is welcome to [[Procedure_for_Specifications|discuss features and improvements with us]].
 
 
 
===honour list===
 
 
 
We thank these previous team members for their valuable contributions:
 
 
 
* peter sikking, principal interaction architect, m+mi works—[http://blog.mmiworks.net blog], [http://blog.mmiworks.net/search/label/GIMP on GIMP]
 
* Kamila Giedrojć, associate interaction architect —[http://kamilagiedrojc.com/info/index.html portfolio]
 
* Ellen Reitmayr, usability consultant —[http://ellen.reitmayr.net/ website]
 
* Kate Price, interaction architect
 
* Tobias Ehni, usability consultant
 
* Dominique Schmidt, associate interaction architect
 
* Marinus Schraal, associate interaction architect
 
 
 
==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.
 
 
 
Want to go deeper? Read the [[Vision briefing | vision briefing]].
 
 
 
==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]]==
 
 
 
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 | expert evaluation notes]]==
 
  
 
We spent a month and a half evaluating GIMP. Enjoy reading the raw [[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.
 
 
We are working on an [[Interaction design patch | interaction design patch]] format.
 
 
==[[specifications]]==
 
 
Solution models get further developed into UI [[specifications]], ready for implementation.
 
 
==[[design guide]]==
 
 
A (growing) [[design guide | guide]] for those who design interaction for GIMP, concentrating on how solutions can be fitted into the overall interaction framework, constraints and how things interconnect.
 

Revision as of 10:34, 28 February 2007

expert evaluation notes

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