Re: [Gimp-developer] input from the UI team needed

2008-01-24 Thread Sven Neumann
Hi, On Thu, 2008-01-24 at 06:35 +0100, Martin Nordholts wrote: It would also be nice to get the Polygonal Select Tool details sorted out for 2.6. There is code for such a tool in bug #119646 [1], the question is just to what extent it should be merged/integrated with the Free Select Tool.

Re: [Gimp-developer] input from the UI team needed

2008-01-24 Thread Alexandre Prokoudine
On Jan 24, 2008 11:10 AM, Sven Neumann wrote: Oh, and we should perhaps think about adding some tool categories. There are already way too many tools in our toolbox. I guess that putting them into groups and separating these groups visually would help a lot. Sven, I hate to raise

Re: [Gimp-developer] input from the UI team needed

2008-01-24 Thread Sven Neumann
Hi, On Thu, 2008-01-24 at 11:18 +0300, Alexandre Prokoudine wrote: Sven, I hate to raise quasi-offtopic themes, but is the plan to publish a roadmap still in force? ;-) I don't think we want to publish something and call it a roadmap. But we had the plan to make a list of important tasks that

[Gimp-developer] tasks list

2008-01-24 Thread Alexandre Prokoudine
On 24 January, 2008, Sven wrote I don't think we want to publish something and call it a roadmap. But we had the plan to make a list of important tasks that outline where GIMP is heading and what we consider important to work on. Since there doesn't seem to be enough interest among the

[Gimp-developer] task list

2008-01-24 Thread William Skaggs
From: Sven Neumann [EMAIL PROTECTED] I don't think we want to publish something and call it a roadmap. But we had the plan to make a list of important tasks that outline where GIMP is heading and what we consider important to work on. Since there doesn't seem to be enough interest among the

Re: [Gimp-developer] input from the UI team needed

2008-01-24 Thread peter sikking
Hey all, sorry for fading out of view for a while. demanding projects (ongoing), a big flue and christmas got in the way. but that is just part of it. The other part is the lack of a roadmap. the lack is now so that I was prepared to write one myself, just to have something to work with. But I

[Gimp-developer] 2008 UI new year's resolutions...

2008-01-24 Thread peter sikking
GIMPsters, a couple of more things for this year: First, Sven was right at my GIMP lecture last month here in berlin: the UI team needs to grow. So I want to add two more UI professionals to the team (double the size!). One more experienced person (3-5 years in interaction design) and one junior

[Gimp-developer] GIMP UI discussions

2008-01-24 Thread Brian Vanderburg II
I've been reading some stuff at gui.gimp.org and I'm wondering where to respond/comment on the issues. I've got a few ideas/comments here. Open and Save dialogs should be implemented natively This would be quite nice. I've heard Inkscape is also getting this support soon. 1. Initial

Re: [Gimp-developer] input from the UI team needed

2008-01-24 Thread William Skaggs
From: peter sikking [EMAIL PROTECTED] I see the list below of what needs input and they are all worthy problems to solve. But they look to be in part different problems than the ones discussed for the roadmap two months ago. There lies the problem. I will give direction for the small

Re: [Gimp-developer] input from the UI team needed

2008-01-24 Thread William Skaggs
As promised in my previous email, I would like to look at the priorities that Peter presented in his LGM talk (at which I was not present), and try to give a sense of my impression of how much work each one involves. You can find a web version of Peter's talk at

Re: [Gimp-developer] input from the UI team needed

2008-01-24 Thread Sven Neumann
Hi, On Thu, 2008-01-24 at 20:20 +0100, peter sikking wrote: When making the roadmap the rational decision can be taken what GIMP needs now: polygonal tool or fixing the floating selection. One gets the nod, the other has to wait for a next release to get worked on (UI spec, dev, test, doc,