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

2008-01-28 Thread Alexander Rabtchevich
Martin Nordholts wrote: Hello Just wanted to mention this since it appears if you haven't noticed it: You can already now do what you are asking for: 1. Make an arbitrary selection 2. Select - To Path 3. Use the Path Tool to edit the created path 4. Select - From Path I already know

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

2008-01-28 Thread Alexander Rabtchevich
Martin Nordholts wrote: Hello Just wanted to mention this since it appears if you haven't noticed it: You can already now do what you are asking for: 1. Make an arbitrary selection 2. Select - To Path 3. Use the Path Tool to edit the created path 4. Select - From Path I already

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

2008-01-26 Thread Alexia Death
Sven Neumann wrote: Would it make sense to add it as a new tool now (provided that Jimmac draws a nice icon for it)? I guess we can always merge it with the Free Select tool later if that is desired As a user I can say it is definitely desired. I miss the option to draw straight segments

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

2008-01-26 Thread Martin Nordholts
Alexander Rabtchevich wrote: And I can see freehand and polygonal selection tools as two different tools or modes. The main wish is to be able to handle any existing selection as a set of Bezier curves (or polygonals). So one can draw a selection as he wishes with any of existing tools,

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

2008-01-25 Thread Sven Neumann
Hi, On Fri, 2008-01-25 at 04:38 +, William Skaggs wrote: 8. improve the text tool Evaluation: Most of the points mentioned here would be relatively simple to implement. One of them -- the ability to have multiple text items within a single layer -- might not be simple, and it should

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

2008-01-25 Thread Sven Neumann
Hi, On Thu, 2008-01-24 at 20:20 +0100, peter sikking wrote: Even before 2.4 came out, I was warned that not to much UI work could be done for 2.6. GEGL first. OK. suits me, that leaves a period where the UI analysis can get (finally!) done and a transition can be made towards tackling the

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

2008-01-25 Thread Martin Nordholts
Sven Neumann wrote: 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

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

2008-01-25 Thread Sven Neumann
Hi, On Fri, 2008-01-25 at 17:21 +, William Skaggs wrote: The idea I was responding to was, as I understood it, basically to have multiple PangoLayouts within the same layer. Even that would probably not be so difficult to implement, but I think it would probably cause more harm than

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

2008-01-25 Thread William Skaggs
From: Sven Neumann [EMAIL PROTECTED] 8. improve the text tool Evaluation: Most of the points mentioned here would be relatively simple to implement. One of them -- the ability to have multiple text items within a single layer -- might not be simple, and it should be considered

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

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

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,

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

2008-01-23 Thread Martin Nordholts
Sven Neumann wrote: Hi Peter, there are a couple of things that are waiting for input from the UI team. Things that we would like to sort out for GIMP 2.6. It would be nice if we could get some advice from you and your team. I made a list of the things that in my opinion are most important