Re: [Gimp-developer] How to minimize main GIMP window
Hi, "Steven P. Ulrick" <[EMAIL PROTECTED]> writes: > My problem is that on the main GIMP interface, I do not see a minimize > button. I looked through the "preferences" menu, especially > the Window Management part, and I found nothing that would let me > re-enable the minimize button. Set the window type hint for the toolbox to "Normal". Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] RFI: Article on GIMP Development for LinuxFormat magazine
On Thu, 27 Apr 2006 11:53:23 -0600 "Michael J. Hammel" <[EMAIL PROTECTED]> wrote: > The editors apparently saw (or maybe just heard of) Karine Delvare's > lecture at the Libre Graphics conference recently and wanted the article > to be based on or at least make it similar to that talk. I don't have > any information on the lecture, so if anyone saw it and took notes (in > english - I think the talk was in French) please let me know. The presentation is still available, in French, at http://edhel.nerim.net/gimp-contribution/ - I could translate those to english and add notes if you wish. Karine ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] RFI: Article on GIMP Development for LinuxFormat magazine
Michael J. Hammel ([EMAIL PROTECTED]) wrote: > I'm looking for feedback on this (see below) from both core developers > as well as casual (infrequent) contributors and end users. Ok, I guess I am a casual core developer... :) I'll just drop in some thoughts, not really ordered > Here is a summary of what we're looking for in this article: > > Part I: Overiew and History > - Overview of the development process: >design/planning, development, bugfixing, and release > - Who are the current GIMP core developers? Not enough people. Sven and Mitch do most of the work on the core, then there are some people like me who donate less time to the GIMP than they'd like to. See the Changelog to get an idea about the number of really active developers. Then there are people like Pippin, who does groundbreaking work that is not visible in the GIMPs changelog yet. > - The joys of bugfixing and generally being involved in a project's >development - preferrably from a non-core developer's point of view > - Overview of Bugzilla > - This history of the GIMP CVS repository: access and support We use Gnome CVS, people who contribute good patches via bugzilla can get CVS access pretty quickly. > - Where to go for help: mailing lists, web sites > > Part II: Getting Involved > 1. Finding a bug and how to reproduce it simply. > 2. Reporting the bug. > 3. Finding the broken code (show code) > 4. Fixing it (print the solution too) > 5. Making a patch file and submitting the fix (step by step). Maybe it would be good to actually fix a bug in the article. That would probably require to quickly spot something small that can be fixed easily. Look for Bugs with the "gnome-love" keyword. > Additional info (usually presented in sidebars): > 1. Photos of developers and/or people I correspond with and are quoted > in this article > 2. 1 sidebar on Writing a GIMP Plugin > 3. One or more of the following: >a. 1 sidebar on GEGL >b. 1 sidebar on Developer Wishlist >c. 1 sidebar on the 5 most annoying GIMP bugs >d. 1 sidebar on important bug fixes provided by non-core developers > > Any additional advocacy information is also welcome (Carol, you've got > lots there, right?). > > The "annoying bugs" should come from non-developers because we want to > show people what needs to be fixed as encouragement to have them come > fit it. It might make more sense to harp on the "gnome-love" bugs, since they are specifically marked this way because we consider them easy prey for new developers. I hope this helps, Simon -- [EMAIL PROTECTED] http://simon.budig.de/ ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] RFI: Article on GIMP Development for LinuxFormat magazine
Don't know if any of you ever read it, but I've been doing a GIMP tutorial column for Linux Format magazine (in the UK) for about 3 years. I recently retired that column so I could start writing about other things (like embedded stuff for LWN.net - coming soon - and other stuff for LXF), but LXF made one final GIMP request: a big article on getting involved with GIMP development. I've agreed to do the article. I think this would be a great way to help improve development, test and documentation involvement by the GIMP user community. The editors apparently saw (or maybe just heard of) Karine Delvare's lecture at the Libre Graphics conference recently and wanted the article to be based on or at least make it similar to that talk. I don't have any information on the lecture, so if anyone saw it and took notes (in english - I think the talk was in French) please let me know. The article will be about 4000 words (pretty hefty for the typical user magazine) and will be in two parts: An overview followed by a case study (re: example of getting involved). The deadline for the article is May 11th. Sorry I couldn't give more time on this, but that's the way of the magazine world. :-) I'm looking for feedback on this (see below) from both core developers as well as casual (infrequent) contributors and end users. The article is primarily about the source development process but I'm also interested in areas like infrastructure issues (CVS and server management: Manish, is that you these days?), advocacy and documentation support. I've been an outsider looking in for a long time now so I've lost track of who's working on what (other than Sven and David). Any old timers still around: feel free to drop me a line just for grins - it would be interesting to hear what you're up to these days (Miles, Adam, who else did I miss?). Here is a summary of what we're looking for in this article: Part I: Overiew and History - Overview of the development process: design/planning, development, bugfixing, and release - Who are the current GIMP core developers? - The joys of bugfixing and generally being involved in a project's development - preferrably from a non-core developer's point of view - Overview of Bugzilla - This history of the GIMP CVS repository: access and support - Where to go for help: mailing lists, web sites Part II: Getting Involved 1. Finding a bug and how to reproduce it simply. 2. Reporting the bug. 3. Finding the broken code (show code) 4. Fixing it (print the solution too) 5. Making a patch file and submitting the fix (step by step). Additional info (usually presented in sidebars): 1. Photos of developers and/or people I correspond with and are quoted in this article 2. 1 sidebar on Writing a GIMP Plugin 3. One or more of the following: a. 1 sidebar on GEGL b. 1 sidebar on Developer Wishlist c. 1 sidebar on the 5 most annoying GIMP bugs d. 1 sidebar on important bug fixes provided by non-core developers Any additional advocacy information is also welcome (Carol, you've got lots there, right?). The "annoying bugs" should come from non-developers because we want to show people what needs to be fixed as encouragement to have them come fit it. Any feedback on this is welcome. If I get a lot of feedback I obviously won't be able to quote (or use pictures of) everyone. But I'll do my best. If anyone has group photos of the core team, that would be helpful, preferrably scanned or taken at a very high resolution. I've reviewed the GIMP web sites in the recent past but will be thumbing my way through them again just to catch anything I missed. Thanks. I look forward to hearing from everyone and to writing this article - it should be very enlightening to me as well! -- Michael J. Hammel Ximba End User Software [EMAIL PROTECTED] http://www.ximba.org LFS UserID: 16857 -- When his IQ reaches 50, he should sell. -- From a real employee performance evaluation. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] How to minimize main GIMP window
Hello, Everyone My problem is that on the main GIMP interface, I do not see a minimize button. I looked through the "preferences" menu, especially the Window Management part, and I found nothing that would let me re-enable the minimize button. When I right click on the GIMP icon in my taskbar, "minimize" is greyed out. Every other window/dialog that GIMP opens has a minimize button, except the main application interface itself. This has been bothering me for a while now, but the thing that prompted me to finally ask about it was when I tried to take a screenshot of my entire display and I could not get rid of the main GIMP interface. (Implied in the fact that this was an issue is that the thing I wanted to take a screenshot of was maximized. So, any information about how to re-enable the ability to minimize the GIMP would be greatly appreciated. Steven P. Ulrick P.S.: My OS is Fedora Core 5. I am running Gimp 2.3.9 from CVS. Also, "/etc/sysconfig/desktop" shows the following: DISPLAYMANAGER="KDE" DESKTOP="KDE" ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] python scripts not working (2.3.8/linux)
when trying the pygimp->sphere.py, I get an error message
PDB calling error for procedure 'gimp-context-set-foreground':
Argument 'foreground' (#1, type GimpRGB) out of bounds
(validation changed ''
I tracked this down to this: gimpmodule.c:
pygimp_set_foreground(PyObject *self, PyObject* args) {
GimpRGB colour;
...
gimp_rgb_set_uchar(&colour, r, g, b);
gimp_context_set_background(&colour);
...
}
it looks like the "colour" is not correctly initialized
(the "a" member is not initialized)
How about this patch?
--- gimpmodule.c2006-01-23 15:46:19.0 +0100
+++ gimpmodule.c2006-04-27 14:24:24.0 +0200
@@ -808,7 +808,7 @@
g = CLAMP(g, 0, 255);
b = CLAMP(b, 0, 255);
-gimp_rgb_set_uchar(&colour, r, g, b);
+gimp_rgba_set_uchar(&colour, r, g, b, 1);
gimp_context_set_background(&colour);
Py_INCREF(Py_None);
@@ -831,7 +831,7 @@
g = CLAMP(g, 0, 255);
b = CLAMP(b, 0, 255);
-gimp_rgb_set_uchar(&colour, r, g, b);
+gimp_rgba_set_uchar(&colour, r, g, b, 1);
gimp_context_set_foreground(&colour);
Py_INCREF(Py_None);
-- lode
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] python scripts not working (2.3.8/linux)
when trying the pygimp->sphere.py, I get an error message
PDB calling error for procedure 'gimp-context-set-foreground':
Argument 'foreground' (#1, type GimpRGB) out of bounds
(validation changed ''
I tracked this down to this: gimpmodule.c:
pygimp_set_foreground(PyObject *self, PyObject* args) {
GimpRGB colour;
...
gimp_rgb_set_uchar(&colour, r, g, b);
gimp_context_set_background(&colour);
...
}
it looks like the "colour" is not correctly initialized
(the "a" member is not initialized)
adding a " gimp_context_get_background(&colour);"
before makes pygimp work again...
I wonder what the best way to fix this would be:
bzero(colour)
memset(&colour, 0, sizeof(colour));
colour->a = 0; // in gimp_rgb_set_uchar()
-- lode
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
