Re: [Gimp-developer] A new

2009-09-20 Thread Gerald Friedland
Hi,

 But SIOX is supposed to be more than a selection tool, isn't it? Isn't
 it about extracting foreground objects? A selection is not enough for that
 when the foreground consists of transparent pixels.

 SIOX is a tool to create a selection, nothing more. I don't see what a
 foreground extraction tool should do besides selecting the foreground.
 Perhaps you can explain this?

 Consider a completely red background with a slightly blurred green filled
 circle in the foreground [1]. If you want to extract the green foreground
 object you need to get rid of the red in the pixels with both red and
 green, but you can't do that with only a selection.

 A good foreground selection tool would need to get rid of the red in the
 pixels with both red and green and only leave slightly transparent green
 pixels.

Absolutely. And this is exactly what Jenny has implemented as part of
the Google Summer of Code.
(So until now SIOX was 'only a selection tool' but now it's not
anymore -- at least once Jenny's code
makes it's way into the main branch)

Gerald

--
Dr. Gerald Friedland
International Computer Science Institute
1947 Center Street, Suite 600
CA-94704 Berkeley, USA
http://www.gerald-friedland.org
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] A new

2009-09-20 Thread Martin Nordholts
On 09/20/2009 08:19 AM, Gerald Friedland wrote:
 A good foreground selection tool would need to get rid of the red in the
 pixels with both red and green and only leave slightly transparent green
 pixels.
 
 Absolutely. And this is exactly what Jenny has implemented as part of
 the Google Summer of Code.
 (So until now SIOX was 'only a selection tool' but now it's not
 anymore -- at least once Jenny's code
 makes it's way into the main branch)

Ok cool.

Speaking of integrating into git master, who will do that? There is a need
to cleanup the branch and introduce proper commit messages. If we could
get help with that it would be great.

BR,
Martin

-- 

My GIMP Blog:
http://www.chromecode.com/

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] are there other occurences of the %s part of _Undo %s ?

2009-09-20 Thread Martin Nordholts
On 09/20/2009 09:56 AM, Cristian Secară wrote:
 There are several strings that become part of these strings:
 _Undo %s
 _Redo %s
 _Fade %s...
 
 My question is if those strings that replaces %s are unique for this
 combination, or they may appear in other places too.

Hi,

No, there is no guarantee that the strings put there are only put there
and nowhere else.

 / Martin

-- 

My GIMP Blog:
http://www.chromecode.com/

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


[Gimp-developer] We should go for a single-window mode in 2.8

2009-09-20 Thread jolie S
jolie wrote:

 http://www.mmiworks.net/eng/publications/2009/09/gimp-single-mode.html 
 

 Read your blog twice and think all the ideas are great.

ah, thanks.

 Commented there too but that was before I read it for the second time.

 An idea occurred to me. When you tear of the tabs, or thumbnail I  
 guess, you
 get a polaroid. Really nice idea. But wouldn't it be great if you  
 could
 rightclick on a thumbnail and chose between polaroid and float  
 image. To make
 it so that the image you're working on has maximum flexibility too,  
 just as
 much as the polaroids?


I have really to ask what you expect from that float image, and how  
different
that would be from multi-widow mode.

 --ps

 founder + principal interaction architect
 man + machine interface works

 http://mmiworks.net/blog : on interaction architecture

For me the big difference is usability. 
When I work in GIMP what happens to me quite a lot is that I click just next
to a window of an image I'm working on and all my GIMP windows are not shown
on my screen anymore because I activated the application I had visibly open
below the GIMP windows. 
To get  GIMP back you have to click on all your GIMP windows in the taskbar.


In a single window interface the background IS gimp. Click next to an image
by accident and nothing will happen, you'll still be in GIMP. 

This is the main reason for me why I am looking forward to a single window
mode. 

Also I've slept on it and given it some more thought and I'd like to ask
again if you would please give having multiple images open at the same time
some more thought. 
IMO being able to work on more images at the same time is VITAL for a
professional image editing program. (just think of cloning to name 1 example)
Please give your users the options to do so in both modes, single and multiple
windows.  

Thank you,
Jolie

-- 
jolie S (via www.gimpusers.com)
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] We should go for a single-window mode in 2.8

2009-09-20 Thread David Gowers
On Sun, Sep 20, 2009 at 8:30 PM, jolie S for...@gimpusers.com wrote:
 Also I've slept on it and given it some more thought and I'd like to ask
 again if you would please give having multiple images open at the same time
 some more thought.
 IMO being able to work on more images at the same time is VITAL for a
 professional image editing program. (just think of cloning to name 1 example)
 Please give your users the options to do so in both modes, single and multiple
 windows.

Peter's specification does give the option to have multiple images open at once.
Perhaps you mean having multiple images both visible and workable-upon
at once. That's certainly important for things like cloning, as you
said.

Perhaps a split-panel option for single window mode would resolve
this. (I believe we could still only reasonably show a maximum of 2
images at once; this is simply a limitation of the single-window
format AFAICS.)
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] We should go for a single-window mode in 2.8

2009-09-20 Thread Liam R E Quin
On Sun, 2009-09-20 at 20:51 +0930, David Gowers wrote:

 Perhaps a split-panel option for single window mode would resolve
 this. (I believe we could still only reasonably show a maximum of 2
 images at once; this is simply a limitation of the single-window
 format AFAICS.)

Do you mean that the windows would be too small, e.g. on a 30
cimena display or with 5 LCD monitors :), or do you mean
that the toolkit only supports two panes??

For cloning you only need a tiny part of the source visible...

Liam



-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org www.advogato.org

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] We should go for a single-window mode in 2.8

2009-09-20 Thread Ville Pätsi
On Sun, Sep 20, 2009 at 01:00:15PM +0200, jolie S wrote:
 For me the big difference is usability. 
 When I work in GIMP what happens to me quite a lot is that I click just next
 to a window of an image I'm working on and all my GIMP windows are not shown
 on my screen anymore because I activated the application I had visibly open
 below the GIMP windows. 
 To get  GIMP back you have to click on all your GIMP windows in the taskbar.

Actually you can work around this problem in your window manager by
selecting an image window and pressing the tab key twice. First to hide
the docks and the second to bring them back. This has the side effect of
raising them to the top of the window stack.

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] We should go for a single-window mode in 2.8

2009-09-20 Thread David Gowers
On Sun, Sep 20, 2009 at 8:57 PM, Liam R E Quin l...@holoweb.net wrote:
 On Sun, 2009-09-20 at 20:51 +0930, David Gowers wrote:

 Perhaps a split-panel option for single window mode would resolve
 this. (I believe we could still only reasonably show a maximum of 2
 images at once; this is simply a limitation of the single-window
 format AFAICS.)

 Do you mean that the windows would be too small, e.g. on a 30
 cimena display or with 5 LCD monitors :), or do you mean
 that the toolkit only supports two panes??
Too small (except on a 30 single display. 5 LCD monitors is not a
situation in which I can reasonably imagine you would want to use
single-window mode; feel free to contradict me if you have experience
with this.)

There are no relevant GTK+ limitations. However I understand that with
the current GUI setup of GIMP, horizontal splits like
|IMG|IMG|
are easier to implement in terms of visual organization.


 For cloning you only need a tiny part of the source visible...

This is only true IMO if the source auto-scrolls as you clone.
Otherwise, especially when you need to be reasonably precise, you may
need a relatively large display (for example, 150x150 area @ 300% zoom
= 450x450)
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


[Gimp-developer] We should go for a single-window mode in 2.8

2009-09-20 Thread jolie
On Sun, Sep 20, 2009 at 8:30 PM, jolie S for...@gimpusers.com wrote:
 Also I've slept on it and given it some more thought and I'd like to ask
 again if you would please give having multiple images open at the same
time
 some more thought.
 IMO being able to work on more images at the same time is VITAL for a
 professional image editing program. (just think of cloning to name 1
example)
 Please give your users the options to do so in both modes, single and
multiple
 windows.

Peter's specification does give the option to have multiple images open at
once.
Perhaps you mean having multiple images both visible and workable-upon
at once. That's certainly important for things like cloning, as you
said.

Perhaps a split-panel option for single window mode would resolve
this. (I believe we could still only reasonably show a maximum of 2
images at once; this is simply a limitation of the single-window
format AFAICS.)



Being able to work on more images at the same does indeed mean
workable-upon. 

You could let the open and visible images you're working on at the same time
float all over the screen. Just as the user wants it. Be it underneath or over
the toolbox. ( a preference would be good for that.) 
Paint shop pro does it that way, so does photoshop and my old pre-GIMP
software Picture Publisher did it that way too, and they are all single window
interfaces. It's definitely not something that can't be done. 

-- 
jolie (via www.gimpusers.com)
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Peter's single-window proposal (Was: We should go for a single-window mode in 2.8)

2009-09-20 Thread peter sikking
Daniel Hornung wrote:

 I'm not planning to dive deeply into this discussion, but I feel  
 that Peter's
 blog deserves its own thread.


OK, I am picking up the thread here.

as I just commented on the blog post, I am going to address this need  
for
windows-in-window and work-side-by-side structurally.

this means first finding out the user requirements behind these  
requests.

so for everybody who feels this: _why_ do you need windows-in-window or
work-side-by-side?

Jolie and Daniel already had their say and it is noted, but I want have
the complete picture before adjusting the plan (or not).

so let me know...

 --ps

 founder + principal interaction architect
 man + machine interface works

 http://mmiworks.net/blog : on interaction architecture



___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Peter's single-window proposal (Was: We should go for a single-window mode in 2.8)

2009-09-20 Thread Rob Antonishen
 this means first finding out the user requirements behind these
 requests.

 so for everybody who feels this: _why_ do you need windows-in-window or
 work-side-by-side?

I've been reading both the blog posts, and the many discussions here
on the mailing list, mainly as an interested user of Gimp.

Here are the main reasons I work with two images fully open at one time:

- sampling colours from one image to use in another other.  (I have a
number of palette images I keep around for this purpose.  I know I
could just create real .pal files from them, but I like to be able to
have the colours spatially distributed the way I like...)
- cutting and pasting areas/selections from one image into the other
- cloning from one image to another (auto-scroll would be nice, here).

I also like to work with two views of the same image at different zoom
ratios, depending on the work I am doing (details drawing, usually).
This includes zoomed in cutting and pasting or cloning of areas that
are far apart.

That being said, I believe I would continue to work with the current
multi window layout, mainly because I am used to it...

-Rob A
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Peter's single-window proposal (Was: We should go for a single-window mode in 2.8)

2009-09-20 Thread Karl Günter Wünsch
On Sunday 20 September 2009, peter sikking wrote:
 so for everybody who feels this: why do you need windows-in-window or
 work-side-by-side?
First of all a great idea to get some more feedback. 
I have one thing for which I had wished for side by side windows recently: 
When working on the layer mask of an image. There I would have very much liked 
to have the background layer, the top level layer and it's layer mask each 
side by side so that I could have judged where I was changing something and 
which effect it has immediately. It would have saved the me endless number of 
switches between the different views I needed to complete my editing... 
This may be something different than what you are proposing but if at all 
possible within the framework to have different layers and or layer masks in 
side by side windows would IMHO help me much!
regards
Karl Günter
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


[Gimp-developer] We should go for a single-window mode in 2.8

2009-09-20 Thread jolie S
   Date: Sun, 20 Sep 2009 14:36:36 +0300
   From: Ville =?iso-8859-1?Q?P=E4tsi?= d...@shadowdrama.net

   On Sun, Sep 20, 2009 at 01:00:15PM +0200, jolie S wrote:
For me the big difference is usability.  When I work in GIMP what
happens to me quite a lot is that I click just next to a window
of an image I'm working on and all my GIMP windows are not shown
on my screen anymore because I activated the application I had
visibly open below the GIMP windows.  To get GIMP back you have
to click on all your GIMP windows in the taskbar.

   Actually you can work around this problem in your window manager by
   selecting an image window and pressing the tab key twice. First to
   hide the docks and the second to bring them back. This has the side
   effect of raising them to the top of the window stack.

I made a small video of what I mean. 

http://www.youtube.com/watch?v=6T8jCDrYtmk


I hope that is clear :\

Hitting tabs twice doesn't work for bringing everything back. A single
window like in Picture Publisher, just to give an example, makes sure that
this problem doesn't even occur. 

Another way that won't be to everybody's choice is to use focus
follows mouse without autoraise, and use a shortcut to raise windows
to the top.


I'm sorry, I'm very tired today so it's probably me, but I don't know what
you mean with this. 

-- 
jolie S (via www.gimpusers.com)
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] We should go for a single-window mode in 2.8

2009-09-20 Thread Liam R E Quin
On Sun, 2009-09-20 at 13:00 +0200, jolie S wrote:
  
 When I work in GIMP what happens to me quite a lot is that I click just next
 to a window of an image I'm working on and all my GIMP windows are not shown
 on my screen anymore because I activated the application I had visibly open
 below the GIMP windows.

Sounds like you have some combination of full-screen or miaximised
windows and also the option is set that makes windows come to the
front when you click on them.

If you want to get the most out of using multiple images in GIMP in
Linux, e.g. to be able to use drag and drop between them, you need
(1) sloppy focus (focus-sollows-mouse, but focus is not lost
when the pointer leaves the mouse window)
(2) turn off auto-raise window on focus or click

Now, if you have two overlapping windows and you click in the
lower one, it won't come to the front, clicking doesn't change
the stacking order of windows.

You can also assign a keyboard shortcut to send the current window
to the back, or, if the current window isn't on top, bring it to
the top -- I use windows-f for this (f for front).  I'd be
happy to talk you through this using GNOME if it helps.

On MS Windows it's quicker to click on the active application
in the task bar and minimize or hide it to get back to GIMP.

[...]

 Also I've slept on it and given it some more thought and I'd like to ask
 again if you would please give having multiple images open at the same time
 some more thought. 

I think the idea is that the single window might have multiple tabs, and
also maybe multiple panes.

Liam




-- 
Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org www.advogato.org

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer