Re: (LONG) Problems with the GIMP (was: Re: [Gimp-developer]tentative GIMP 2.0 release plans)
Tor Lillqvist writes: > There also seems to be some handle leak when GIMP is starting up and > queries all the plug-ins. Also, something needs to be done to #98737 > soon. (Perhaps related, I had to start GIMP at least four times before > it got past all the plug-ins and wrote out the pluginrc file.) Done: 2003-07-30 Tor Lillqvist <[EMAIL PROTECTED]> * app/plug-in/plug-in.c (plug_in_close): [Win32] Plug handle leak, call CloseHandle(). and in GLib: 2003-07-31 Tor Lillqvist <[EMAIL PROTECTED]> * glib/gspawn-win32.c: When possible, manage without the helper process. (Part of the enhancements outlined in #98737.) Speeds up GIMP 1.3's first-time-run plug-in query phase a lot. Plug a file descriptor (and thus Win32 handle) leak: close the read end of the child error report pipe after use. Now I can start GIMP 1.3.17 from fresh and it successfullly queries all the plug-ins, quite fast even, with no handles leaked. Still need to add script support to gspawn-win32.c so that Hans's Python plug-ins work. --tml ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: (LONG) Problems with the GIMP (was: Re: [Gimp-developer]tentative GIMP 2.0 release plans)
Hans Breuer writes: > This is a regression of previous versions. IIRC it was caused > by the usage of gdk_eindow_new() with parameters 'in range' and > additional adjusted by SafeAdjustWindowRect and the code > later calling gdk_window_move with coordinates directly derived > from the current mouse cursor position. > Using SafeAdjustWindowRectEx in gdk/win32/gdkwindow-win32.c:996 > appears to fix it. I just committed changes to gdk/win32 (HEAD and gtk-2-2) that seem to fix these problems. In fact, I dropped SafeAdjustWindowRectEx() altogether, I don't think it's GTK's business to prevent an application from locating its windows outside of the screen if it wants to :-) And with multiple monitors, coordinates might be negative anyway. The main job of the fix was going through the handling of top-level window position and size in event generation and functions, and make sure that it matches GDK's convention (position is that of decoration, size that of client area). And in the Win32 API, usually both position and size include decorations. > I'm still using my somewhat hackish g_spawn_async version attached to > the bug report and don't have to restart at all under win9x during the > whole plug-in query phase. I'll look at g_spawn() improvements tomorrow, hopefully. --tml ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: (LONG) Problems with the GIMP (was: Re: [Gimp-developer]tentative GIMP 2.0 release plans)
At 23:22 27.07.03 +, Tor Lillqvist wrote: [...] > >One irritating thing with GIMP on Windows currently is GTK bug >#112402, I really need to fix that soon. GIMP's toolbox and some other >windows are currently positioned with their title bar exactly off >screen. > This is a regression of previous versions. IIRC it was caused by the usage of gdk_eindow_new() with parameters 'in range' and additional adjusted by SafeAdjustWindowRect and the code later calling gdk_window_move with coordinates directly derived from the current mouse cursor position. Using SafeAdjustWindowRectEx in gdk/win32/gdkwindow-win32.c:996 appears to fix it. >There also seems to be some handle leak when GIMP is starting up and >queries all the plug-ins. Also, something needs to be done to #98737 >soon. (Perhaps related, I had to start GIMP at least four times before >it got past all the plug-ins and wrote out the pluginrc file.) > I'm still using my somewhat hackish g_spawn_async version attached to the bug report and don't have to restart at all under win9x during the whole plug-in query phase. Hans Hans "at" Breuer "dot" Org --- Tell me what you need, and I'll tell you how to get along without it.-- Dilbert ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: (LONG) Problems with the GIMP (was: Re: [Gimp-developer]tentative GIMP 2.0 release plans)
Alan Horkan writes: > Any chance of binaries [for Win32] for testing? If you ask nicely, I might be presuaded to zip up what I've got... (Just built it on Win32 for the first time in a while.) > And what compiler did you use (wondering if I'll be able to get gtk-wimp > to work with the Gimp 1.3 on windows). gcc version 3.2.3 (mingw special 20030504-1) One irritating thing with GIMP on Windows currently is GTK bug #112402, I really need to fix that soon. GIMP's toolbox and some other windows are currently positioned with their title bar exactly off screen. There also seems to be some handle leak when GIMP is starting up and queries all the plug-ins. Also, something needs to be done to #98737 soon. (Perhaps related, I had to start GIMP at least four times before it got past all the plug-ins and wrote out the pluginrc file.) --tml ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: (LONG) Problems with the GIMP (was: Re: [Gimp-developer]tentative GIMP 2.0 release plans)
On Sat, 26 Jul 2003, Michael Schumacher wrote: > Date: Sat, 26 Jul 2003 03:04:12 +0200 (MEST) > From: Michael Schumacher <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: (LONG) Problems with the GIMP (was: Re: [Gimp-developer] > tentative GIMP 2.0 release plans) > > > Michael Schumacher writes: > > > According to Tor Lillqvist, there was something missing from Pango > > > 1.2.3 and fixed shortly after the release. > > > > BTW, I now made new pre-built pango-1.2.3 Win32 packages on > > www.gimp.org/win32/downloads.html, with the missing exports added, so > > building GIMP 1.3.x for Win32 should now be easier. > > Thanks. I've succeeded in building GIMP 1.3 on Win32 using these packages. Any chance of binaries for testing? And what compiler did you use (wondering if I'll be able to get gtk-wimp to work with the Gimp 1.3 on windows). Sincerely Alan Horkan http://advogato.org/person/AlanHorkan/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: (LONG) Problems with the GIMP (was: Re: [Gimp-developer]tentative GIMP 2.0 release plans)
> Michael Schumacher writes: > > According to Tor Lillqvist, there was something missing from Pango > > 1.2.3 and fixed shortly after the release. > > BTW, I now made new pre-built pango-1.2.3 Win32 packages on > www.gimp.org/win32/downloads.html, with the missing exports added, so > building GIMP 1.3.x for Win32 should now be easier. Thanks. I've succeeded in building GIMP 1.3 on Win32 using these packages. HTH, Michael -- The GIMP (deutsch): http://www.gimp.de +++ GMX - Mail, Messaging & more http://www.gmx.net +++ Jetzt ein- oder umsteigen und USB-Speicheruhr als Prämie sichern! ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: (LONG) Problems with the GIMP (was: Re: [Gimp-developer]tentative GIMP 2.0 release plans)
Michael Schumacher writes: > According to Tor Lillqvist, there was something missing from Pango > 1.2.3 and fixed shortly after the release. BTW, I now made new pre-built pango-1.2.3 Win32 packages on www.gimp.org/win32/downloads.html, with the missing exports added, so building GIMP 1.3.x for Win32 should now be easier. --tml ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: (LONG) Problems with the GIMP (was: Re: [Gimp-developer]tentative GIMP 2.0 release plans)
Michael Schumacher wrote: On 19 Jul 2003 at 22:13, David Neary wrote: [...] Those are the problems at the philosophical level. At the practical level, the problems are: 1) Not enough users use bugzilla to report bugs Bugzilla is powerful, but its power comes at the price of complexity... 2) Not enough developers use Bugzilla to find out what bugs need fixing 3) Not enough developers hear user complaints Most bug reports I've read are commented by at least one person who I'd consider to be one of the developers. This might be incorrect, maybe because in my opinion, developing isn't just coding. 4) Not enough users know what's happenning in the developer series. Tried to change this using gimp.de. As this is a german language portal site, it is known (at least I hope it is at all) mainly in german speaking countries. It's limited to the eye-catching features, i.e. new (ui) functions or performace improvments (like the recent mmx enhancements). 5) Not enough non-technical people are working on the GIMP (this is at odds with when I joined, when many of the most active GIMP people were non-technical). In my opinion, it's not clearly defined what they can do. The most common answer is "write documentation", but this seems to requires cvs access or someone who will coordinate the whole thing. Maybe wiki.gimp.org can help here, though it's purpose is still somewhat undecided. That's the practical level. Now, here's why I think these problems exist. 1) Too many communication interfaces, not enough communication. The GIMP has the following communication methods available to it: - Website - www.gimp.org - Website - mmmaybe.gimp.org - Website - gug.sunsite.dk mmmaybe.gimp.org should replace www.gimp.org, so this should clear sooner or later. gug.sunsite.dk isn't under direct control of the gimp community, at least that's that's my impression. - IRC - irc.gnome.org This is the fastest way to get support - even interactive - from the community, so it isn't redundant at all. - Usenet - comp.graphics.apps.gimp Usenet is some peoples medium of choice, too. - Mailing list - [EMAIL PROTECTED] - Mailing list - [EMAIL PROTECTED] - Mailing list - [EMAIL PROTECTED] - Mailing list - [EMAIL PROTECTED] gimpwin-dev is no more, it was closed and everyone was asked to use gimp- developer instead - Mailing list - [EMAIL PROTECTED] - Mail alias - [EMAIL PROTECTED] - Bugzilla - bugzilla.gnome.org - CVS - cvs.gnome.org - Release notes. There's definite consolidation to be done there. That's 13 ways to get information. And 13 ways to send it. I listen personally to about 3 of those... [EMAIL PROTECTED], Usenet and the devel list. I'm using at least six of them - 3 lists, usenet, irc, bugzilla. [...] My first proposal would be to do a reverse split of the users and developers mailing lists - get everyone talking to one another. It will certainly annoy people because of increased traffic, but I think it'll be worth it. We have to face up to the fact that after 3 years without a major release, and only 14 active developers, the GIMP is a small project. Step 1 is to get people talking to each other. Well, whenever something got to technical on gimpwin-users, some of the users did unsubscribe. However, in most of the cases, it was far less technical than anything on gimp-developer, so there may be some problems here. Readers of gimp- user may be a bit more interested in this than the average win32 user, though. Proposal 3 is to try to persuade the Win32 guys to come back to the main gimp mailing list. 1.3 should be buildable out of CVS, but I have not been able to find anyone who's actually done it using free build tools. Personally I failed miserably somewhere around pango. According to Tor Lillqvist, there was something missing from Pango 1.2.3 and fixed shortly after the release. Maybe a thread about building GIMP 1.3.16 on Win32 should be started here, I'm willing to contribute everything I've encountered while trying to do so. Our biggest user base is win32 users, so that's probably our biggest source for future developpers, documenters, ui designers. We should be listening to them, and they should be listening to us. Yep. Though listening to them is a bit hard sometimes. Most of the problems are some kind of "gimp is broken". Often, it turns out to be something completely different. And of course, you'll have to mute all those 'use a REAL os' - posts from the mailing list then. They aren't providing solutions, they are annoying users ;) [...] Proposal 6 - allow people to submit bug reports without a bugzilla account. I would like it if Bugzilla could get their email address from the first mail they send to the portal, sign them up and send them a password, but it doesn't. As a technical problem, is this possible? Or could we have a mail alias to which mails (which pass a spam filter
Re: (LONG) Problems with the GIMP (was: Re: [Gimp-developer]tentative GIMP 2.0 release plans)
On 19 Jul 2003 at 22:13, David Neary wrote: [...] > Those are the problems at the philosophical level. At the > practical level, the problems are: > > 1) Not enough users use bugzilla to report bugs Bugzilla is powerful, but its power comes at the price of complexity... > 2) Not enough developers use Bugzilla to find out what bugs need > fixing > 3) Not enough developers hear user complaints Most bug reports I've read are commented by at least one person who I'd consider to be one of the developers. This might be incorrect, maybe because in my opinion, developing isn't just coding. > 4) Not enough users know what's happenning in the developer > series. Tried to change this using gimp.de. As this is a german language portal site, it is known (at least I hope it is at all) mainly in german speaking countries. It's limited to the eye-catching features, i.e. new (ui) functions or performace improvments (like the recent mmx enhancements). > 5) Not enough non-technical people are working on the GIMP (this > is at odds with when I joined, when many of the most active GIMP people > were non-technical). In my opinion, it's not clearly defined what they can do. The most common answer is "write documentation", but this seems to requires cvs access or someone who will coordinate the whole thing. Maybe wiki.gimp.org can help here, though it's purpose is still somewhat undecided. > That's the practical level. Now, here's why I think these > problems exist. > > 1) Too many communication interfaces, not enough communication. > > The GIMP has the following communication methods available to it: > > - Website - www.gimp.org > - Website - mmmaybe.gimp.org > - Website - gug.sunsite.dk mmmaybe.gimp.org should replace www.gimp.org, so this should clear sooner or later. gug.sunsite.dk isn't under direct control of the gimp community, at least that's that's my impression. > - IRC - irc.gnome.org This is the fastest way to get support - even interactive - from the community, so it isn't redundant at all. > - Usenet - comp.graphics.apps.gimp Usenet is some peoples medium of choice, too. > - Mailing list - [EMAIL PROTECTED] > - Mailing list - [EMAIL PROTECTED] > - Mailing list - [EMAIL PROTECTED] > - Mailing list - [EMAIL PROTECTED] gimpwin-dev is no more, it was closed and everyone was asked to use gimp- developer instead > - Mailing list - [EMAIL PROTECTED] > - Mail alias - [EMAIL PROTECTED] > - Bugzilla - bugzilla.gnome.org > - CVS - cvs.gnome.org > - Release notes. > There's definite consolidation to be done there. That's 13 ways > to get information. And 13 ways to send it. I listen personally > to about 3 of those... [EMAIL PROTECTED], Usenet and the devel list. I'm using at least six of them - 3 lists, usenet, irc, bugzilla. [...] > My first proposal would be to do a reverse split of the users > and developers mailing lists - get everyone talking to one > another. It will certainly annoy people because of increased > traffic, but I think it'll be worth it. We have to face up to the > fact that after 3 years without a major release, and only 14 > active developers, the GIMP is a small project. Step 1 is to get > people talking to each other. Well, whenever something got to technical on gimpwin-users, some of the users did unsubscribe. However, in most of the cases, it was far less technical than anything on gimp-developer, so there may be some problems here. Readers of gimp- user may be a bit more interested in this than the average win32 user, though. > Proposal 3 is to try to persuade the Win32 guys to come back to > the main gimp mailing list. 1.3 should be buildable out of CVS, > but I have not been able to find anyone who's actually done it > using free build tools. Personally I failed miserably somewhere > around pango. According to Tor Lillqvist, there was something missing from Pango 1.2.3 and fixed shortly after the release. Maybe a thread about building GIMP 1.3.16 on Win32 should be started here, I'm willing to contribute everything I've encountered while trying to do so. > Our biggest user base is win32 users, so that's > probably our biggest source for future developpers, documenters, > ui designers. We should be listening to them, and they should be > listening to us. Yep. Though listening to them is a bit hard sometimes. Most of the problems are some kind of "gimp is broken". Often, it turns out to be something completely different. And of course, you'll have to mute all those 'use a REAL os' - posts from the mailing list then. They aren't providing solutions, they are annoying users ;) [...] > Proposal 6 - allow people to submit bug reports without a > bugzilla account. I would like it if Bugzilla could get their > email address from the first mail they send to the portal, > sign them up and send them a password, but it doesn't. As a > technical problem, is this possible? Or could we have a mail > alias to which mails (which pass a spam filter) get c
