Re: [Gimp-developer] Refactoring code from GPL to LGPL
Hi, Robin Rowe [EMAIL PROTECTED] writes: I honestly am not sure what the process for moving code to libgimp is... essentially it is just moving the code to a library, and then adding a wrapper (if required) around those functions to expose them to the PDB. Good technical anwer, thanks. Well, the answer was technically incorrect since it's the PDB and libgimp that's a wrapper around code in the core, not the other way around. I'm also wondering from a license standpoint. The code in app is GPL, but libgimp is LGPL. I'm not a lawyer, but it would seem that to change the code license from GPL that GIMP would need to get permission from all authors, or reserve the right to change the license later. Sven has said in the past that he often checks in patches in his own name in CVS, that GIMP does not keep exact records of who its authors are. Sorry, but that's not true. Whenever I check code into CVS I mention the authors explicitely so it's completely possible to track the authors by looking at the CVS log. How do you get permission to move GIMP code from GPL into LGPL? Basically we do this so rarely that is hasn't been a problem so far to get permissions from everyone who touched the code in question. May I ask why you are asking these questions? Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2 Questions
Sven Neumann wrote: Hi, Stephan Menzel [EMAIL PROTECTED] writes: 1. Whenever I click on the 'Insert Text' Button, the foreground color as well as the color for the text itself changes to black. Though it is possible to use another color it is much more complicated than before (1.2.2). Why? I often pick a color out of the picture with this little colorpickertool and then insert text in this color that matches another in the picture. Black is the least I would use. But now this is complicated and rather a pain. Does this change have any purpose I just don't see? Anyway, if it doesn't, can you change that back in the next release? The foreground color is not supposed to change. If it really does, that would be a bug. However I don't seem to able to reproduce this. This is an issue with the per-tool contexts. If you select a colour with the colour picker, then select the text tool, the text tool will have a black foreground (its own context). However, it doesn't affect the background. This is confusing, because it means that using the colour picker to pick a text colour involves picking the colour, opening the colour chooser and saving it, setting the text tool, opening the colour chooser for the text tool, and loading the saved colour. Which is complicated.It would be nicer (imho) if the text tool used the active FG if it hadn't been set yet, rather than defaulting to black. If you look at this from the point of view of someone coming from 1.2, this problem is obvious. Cheers, Dave. -- Dave Neary [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2 Questions
Hi, Dave Neary wrote: It would be nicer (imho) if the text tool used the active FG if it hadn't been set yet, rather than defaulting to black. The proper way to do this, I suppose, would be to get rid of the color option from the text tool options, and just use the foreground in the same way as the other paint tools use it (keep it in the context, but don't set it by default). Cheers, Dave. -- Dave Neary [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2 Questions
Hi, Dave Neary [EMAIL PROTECTED] writes: This is an issue with the per-tool contexts. This is not an issue, it's a bug and should be reported in Bugzilla. If you select a colour with the colour picker, then select the text tool, the text tool will have a black foreground (its own context). However, it doesn't affect the background. This is confusing, because it means that using the colour picker to pick a text colour involves picking the colour, opening the colour chooser and saving it, setting the text tool, opening the colour chooser for the text tool, and loading the saved colour. Which is complicated.It would be nicer (imho) if the text tool used the active FG if it hadn't been set yet, rather than defaulting to black. Sorry, but that's definitely not how it works nor how it's supposed to work. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2 Questions
Hi, Stephan Menzel [EMAIL PROTECTED] writes: Well, it does here. I can reproduce it every time. 0. Load Gimp and load any picture (tried with RGB and Greyscale) 1. press O 2. pick a color from the picture 3. close the little color chooser window 4. press T or click the Text button - The forgroundcolor is black again and so is the text. As I said, I had a closer look and it does indeed not behave as it should. So this is clearly a bug. I use version 2.0.1, which works fine, besides this. If it really is a bug. It wouldn't be so bad if I could choose a new color from the textcolorwidget but there is only the color dialog which is inconvenient. I prefer 'o'. You don't have to use the color dialog that you open from the text tool options. Simply drag a color on the color button to change the text color. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2 Questions
Hi, It would be nicer (imho) if the text tool used the active FG if it hadn't been set yet, rather than defaulting to black. That's exactly how it is supposed to work. Dave Neary [EMAIL PROTECTED] writes: The proper way to do this, I suppose, would be to get rid of the color option from the text tool options, and just use the foreground in the same way as the other paint tools use it (keep it in the context, but don't set it by default). Nope, that won't work. The text tool is supposed to use the foreground color unless it is being used on an already existing text layer. In that case it needs to use the color of the text layer and that's why the color button is needed. All that needs to be done here is to get the bug fixed and resurrect the intended behaviour. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2 Questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Good morning, On Tuesday 11 May 2004 10:53, Dave Neary wrote: The proper way to do this, I suppose, would be to get rid of the color option from the text tool options, and just use the foreground in the same way as the other paint tools use it (keep it in the context, but don't set it by default). Exactly. This is how it used to be and this is how it should be. The extra color option in the text options is not needed. Stephan -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAoKM1bv5p9h9J588RAohFAKD6PMKglAj8kH7XkAU+5eC6iRPZYQCg9HEG qTlXMRx/Du6lrPuHZ9ATUW0= =5FAv -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2 Questions
Hi, Stephan Menzel [EMAIL PROTECTED] writes: The proper way to do this, I suppose, would be to get rid of the color option from the text tool options, and just use the foreground in the same way as the other paint tools use it (keep it in the context, but don't set it by default). Exactly. This is how it used to be and this is how it should be. The extra color option in the text options is not needed. As I already explained in a previous mail, Dave is wrong here and the color button is needed. The way it used to be there wasn't the concept of editable text layers. With the introduction of text layers the color button became necessary. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2 Questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Sven, On Tuesday 11 May 2004 12:13, Sven Neumann wrote: As I already explained in a previous mail, Dave is wrong here and the color button is needed. The way it used to be there wasn't the concept of editable text layers. With the introduction of text layers the color button became necessary. I have seen your Mail later, sorry. Does that mean, that this color must default to black as well? There can be an extra color button in that dialog, no worries, but couldn't it default to the picked foreground color when this text layer is created in the first place? Or is that how it is supposed to be? Stephan -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAoKjnbv5p9h9J588RAuIIAJ0eYsJf/uOWX+5rtNyXPHAbChf1DQCfd3N0 Uy+JpWEYANgpjcVML1EFX4w= =nTPO -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Volunteer needed
Hi, I thought I would have time to do so, but I am fast realising that I won't. We now have, as I said before, 3 ways that people can donate funds directly to the GIMP, via the GNOME Foundation. This is a short-term arrangement, and we will discuss what (if anything) we want to put in place long-term with the foundation board at GUADEC. So - here's the request: The following information needs to be added pretty quickly (and prominently) to the webpage, so that we can start advertising the ways to fund the GIMP around community sites. Is there anyone with the time to do this today or tomorrow? I won't have time to do this (even if it's pretty small) until next week, at the earliest. Thanks, Dave. = Fundraising info to add to the webpage === Donating money to the GIMP is easy! The guys at the GNOME Foundation have graciously agreed to act as fiscal agents for us, which means we can offer tax deductible donations in the US. There are 3 ways to support the GIMP financially, and get as many of the GIMP Developers as possible to the GIMP Developers Conference, taking place in Norway as a sub-event of GUADEC at the end of June, as well as expenses associated with the establishment of the GIMP Foundation: 1) Cheque, made payable to the GNOME Foundation, and sent to GNOME Foundation c/o Novell, Inc. 8 Cambridge Center Floor 5 Cambridge, MA 02142 with a cover-letter (or a note in the memo field) saying it is for the GIMP. You can additionally send a mail saying that you have donated to [EMAIL PROTECTED], if you want to. 2) Wire transfer Send an email to [EMAIL PROTECTED], requesting bank details, and specifying that you are donating to the GIMP. 3) Paypal Donate to [EMAIL PROTECTED], this will notify us, and the GNOME board, that funds have been donated to the GIMP. Credit card donations are also accepted via this route. Please indicate whether you would like your donation to remain anonymous, as otherwise you will be listed as a sponsor of the GIMP on the gimp.org web-pages. Note: The following can be added to allow a paypal donation to be just one click from the website (the page http://www.gimp.org/sponsors/thanks.html should exist with a short thank you message, otherwise the return field should be omitted): form method=post action=https://www.paypal.com/cgi-bin/webscr; input value=_xclick name=cmd type=hidden input value=[EMAIL PROTECTED] name=business type=hidden input value=The GIMP name=item_name type=hidden input value=108 name=item_number type=hidden input value=http://www.gimp.org/sponsors/thanks.html; name=return type=hidden input value=1 name=no_shipping type=hidden input alt=Support the GIMP name=submit border=0 src=donate.png type=image /form I've attached donate.png, which is directly taken from www.gnome.org/friends. Alternatively, we can use the paypal icon like this... input alt=Make payments with PayPal - it's fast, free and secure! name=submit border=0 src=https://www.paypal.com/images/x-click-but04.gif; type=image ...but since we're not getting anything from paypal, perhaps the neutral one is better. Thanks a lot, Dave. -- Dave Neary [EMAIL PROTECTED] inline: donate.png___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: Volunteer needed
Hi all, Dave Neary wrote: 3) Paypal snip I sent this a little too quickly - I'm still waiting for a confirmation that paypal is available, and the values in item_id and item_name may be different. It would still be cool to get the first 2 methods on the site asap and add the 3rd when it's confirmed as an option (which should be today). Cheers, Dave. Donate to [EMAIL PROTECTED], this will notify us, and the GNOME board, that funds have been donated to the GIMP. Credit card donations are also accepted via this route. Please indicate whether you would like your donation to remain anonymous, as otherwise you will be listed as a sponsor of the GIMP on the gimp.org web-pages. Note: The following can be added to allow a paypal donation to be just one click from the website (the page http://www.gimp.org/sponsors/thanks.html should exist with a short thank you message, otherwise the return field should be omitted): form method=post action=https://www.paypal.com/cgi-bin/webscr; input value=_xclick name=cmd type=hidden input value=[EMAIL PROTECTED] name=business type=hidden input value=The GIMP name=item_name type=hidden input value=108 name=item_number type=hidden input value=http://www.gimp.org/sponsors/thanks.html; name=return type=hidden input value=1 name=no_shipping type=hidden input alt=Support the GIMP name=submit border=0 src=donate.png type=image /form I've attached donate.png, which is directly taken from www.gnome.org/friends. Alternatively, we can use the paypal icon like this... input alt=Make payments with PayPal - it's fast, free and secure! name=submit border=0 src=https://www.paypal.com/images/x-click-but04.gif; type=image ...but since we're not getting anything from paypal, perhaps the neutral one is better. Thanks a lot, Dave. -- Dave Neary [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] New to Development
Hi Bill, Laughner, Bill wrote: I'm a newbie to this developer list. I've been searching the site for some info on how the developer community is governed, but could not find what I was looking for. Who/how are patches approved for release and how is the release process managed? Sven does it, mostly. Cheers, Dave. -- Dave Neary [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2 Questions
Hi, Stephan Menzel [EMAIL PROTECTED] writes: Does that mean, that this color must default to black as well? There can be an extra color button in that dialog, no worries, but couldn't it default to the picked foreground color when this text layer is created in the first place? Or is that how it is supposed to be? I thought I explained that already. Unless a text layer is selected, the color button in the text tool options is supposed to stay in sync with the foreground color. That's how it works in the HEAD branch. I am not sure when and why it broke in gimp-2.0. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] New to Development
Hi, Dave Neary [EMAIL PROTECTED] writes: I'm a newbie to this developer list. I've been searching the site for some info on how the developer community is governed, but could not find what I was looking for. Who/how are patches approved for release and how is the release process managed? Sven does it, mostly. Well, yes. But please don't send me patches by email. Given the amount of spam I receive I might not even get your mail. And even if it reached me, I would ask the sender to open a bug report and attach the patch to it. That's the only way to assure that patches aren't lost and/or forgotten. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Getting to 2.2
Hi there, I know Sven wanted to get 2.2 out in late June, which is in about 7 weeks from now. When do we think would be a good time to feature freeze, string freeze, etc? I haven't yet done anything on the 2.1 series, since I've been busy with other things, and trying to take a break and rebalance my yin, so I'm not really in a position to say where we are with respect to goals and where we think we'll be in the next couple of weeks. But from experience, if we want a 2.2 release in the end of June, we will probably need to have a release soon, and a pre-release feature frozen in a couple of weeks or so. What do people think of that plan? Alternatively, I'm happy enough to freeze in the end of June, and release at the end of August or so. Cheers, Dave. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Volunteer needed
Hi Dave, GNOME Foundation c/o Novell, Inc. 8 Cambridge Center Floor 5 Cambridge, MA 02142 Perhaps the country name could be added as well? Otherwise people may assume it is the first Cambridge (UK) or one of the other international cities using the same name. Regards JG ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
