Re: [Gimp-developer] A few simple patches
Hi, On Wed, 2007-06-27 at 11:01 +0930, David Gowers wrote: > > (2) It mixes filenames with strings displayed in the GUI. Filenames can > > be of a different encoding and therefore need special treatment. In > > particular you must not call g_path_get_dirname() on the result of > > file_utils_uri_display_name(). > > So the filename should be recoded to ascii and then finally back to > UTF-8? (IIRC URI's are encoded in UTF-8.) No, filenames are not in ASCII encoding. GLib has functions to convert from and to filename encoding but it would go beyond the scope of this mailing-list to explain this here. Since I have already taken care of the issue in SVN, I don't think we need to discuss this further. > > (3) Showing a directory name does only work for local files, it breaks > > for remote files. > > This is incorrect, I checked for that case and it shows what I believe > to be the correct parallel to 'directory name': > for 'http://foo.bar/baz/bif.gif' it shows 'http://foo.bar/baz/' > (the only other parallel I could see making sense would be /baz/ -- > which strikes me as not-very-helpful.) It would have broken on Windows where the path separator for filenames is different from the path separator in URIs. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] A few simple patches
On 6/27/07, Sven Neumann <[EMAIL PROTECTED]> wrote: > Hi, > > On Tue, 2007-06-26 at 12:50 +0200, [EMAIL PROTECTED] wrote: > > > Unless what he's implemented is bad why not just comit anyway until you > > get around to doing it better/diffeently? > > I rejected the patch for several reasons, all of them technical: > > (1) It adds a label for a potentially long string without taking any > measure to avoid that the dialog gets too wide due to that. Okay (I don't know how to ellipsize a string in GTK, though of course I know how to truncate or ellipsize the content of it) > > (2) It mixes filenames with strings displayed in the GUI. Filenames can > be of a different encoding and therefore need special treatment. In > particular you must not call g_path_get_dirname() on the result of > file_utils_uri_display_name(). So the filename should be recoded to ascii and then finally back to UTF-8? (IIRC URI's are encoded in UTF-8.) > > (3) Showing a directory name does only work for local files, it breaks > for remote files. This is incorrect, I checked for that case and it shows what I believe to be the correct parallel to 'directory name': for 'http://foo.bar/baz/bif.gif' it shows 'http://foo.bar/baz/' (the only other parallel I could see making sense would be /baz/ -- which strikes me as not-very-helpful.) > > Sorry, but I couldn't accept the patches for the reasons given above. > And now I have even put more time into this than it has taken David to > come up with the patches in the first place. > > As a general rule, please ask before you write a patch. Okay, I will. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Webdesign is wrong
peter sikking wrote: > interesting to see "Compare compressed images against original", would > it be enough to see the compressed one and balance that against the size > and what your customer expects? I usually do comparisons when I'm trying to get the best image quality out of jpegs. There seems to be a threshold with jpegs beyond which reducing compression only has a negligible effect on quality. I usually search for that point by reducing the compression of a low quality jpeg until it looks the same as (or close to) a high quality one. I suppose I could just reduce compression until it looks "good enough" but I prefer to do spot-the-difference style comparisons. --- Scanned by M+ Guardian Messaging Firewall --- ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Webdesign is wrong
Akkana Peck wrote: > I might have misunderstood this step (I definitely don't follow the > comment about PS not letting you edit -- maybe that's a PS issue) > but it sounds like if you did a "Paste as New" in gimp, you wouldn't > need to create a new canvas or figure out any dimensions. Oh yeah. Thanks for the tip. :) --- Scanned by M+ Guardian Messaging Firewall --- ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Webdesign is wrong
On 6/26/07, peter sikking <[EMAIL PROTECTED]> wrote: > > Please don't forget other users :-) I routinely have a selection > > that's, say, 10,000 pixels by roughly 40 pixels. This might not > > be a usual case for Web graphics... > > an aspect ratio of 1000 to 4. cool. > > at what zoom level(s) do you adjust this selection? > and why? At one point a few years ago I was working on very large maps for MMORPGs stitched together from many smaller images. It was not uncommon for me to have a 1x250 selection. Not quite what Liam is doing, but still extreme. I generally created the selection at about 10x zoom, which meant I had to scroll 100 screens (1024 display width, 1*10x image width) sideways. This would be much harder today, as it seems that GIMP has lost a lot of its old "scroll super fast if i drag far outside the window" functionality in more recent 2.3 builds. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] Mouse problems using Wacom tablets
Luis wrote: > I tried to install Inkscape Fedora RPM, but for some reason the last > repository version seems highly broken (at least with my package setup). > I should compile it by myself when I have some time (lots of libraries > and dependencies). > There are autopackages available at the inkscape website. You can choose the latest stable version or svn compilations. It's not the cleanest way to install a package, but it will work for your tests. > Anyway, your problem description is EXACTLY mine. > Did you try disabling the eraser (not the stylus)? > In that way, the mouse works (but not the eraser, of course). > You should move the stylus to 'activate' the mouse. > Is this also the behavior in Inkscape? > My pen hasn't an eraser (it isn't a Wacom) so I can't tell. What I could see is the same in Gimp and in Inkscape. Once you've used the tablet, it seems to "catch" the pointer, and the mouse becomes unuseful for the app. But if you close the program, everything works as it should. I'm guessing it's a GTK problem because Gimp and Inkscape share the same menu for activating the tablet. But I really don't know if I'm right. Somebody pointed here that is a problem fixed in the newest versions of gtk+ and linuxwacom, but I'll have to wait those libraries to be in the Ubuntu repos, since I'm not so comfortable experimenting with that kind of libraries (GTK mostly, I don't want to break something if I don't know how to fix it - at least in my computer for work :-p). G. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Webdesign is wrong
Liam, >> actually right now I am specifying how the selection tools should >> deal >> with long, very narrow selections, with the web guys in mind. > Please don't forget other users :-) I routinely have a selection > that's, say, 10,000 pixels by roughly 40 pixels. This might not > be a usual case for Web graphics... an aspect ratio of 1000 to 4. cool. at what zoom level(s) do you adjust this selection? and why? thanks, --ps principal user 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] A few simple patches
Hi, On Tue, 2007-06-26 at 12:50 +0200, [EMAIL PROTECTED] wrote: > Unless what he's implemented is bad why not just comit anyway until you > get around to doing it better/diffeently? I rejected the patch for several reasons, all of them technical: (1) It adds a label for a potentially long string without taking any measure to avoid that the dialog gets too wide due to that. (2) It mixes filenames with strings displayed in the GUI. Filenames can be of a different encoding and therefore need special treatment. In particular you must not call g_path_get_dirname() on the result of file_utils_uri_display_name(). (3) Showing a directory name does only work for local files, it breaks for remote files. > Well it's true it does not seem to do much so it may be best no to build > it if it's been pushed to a future release. Still committing the name > change would not be a bad move since David has coded it. Committing that change would have introduced a string change. We are tentatively string frozen so we will avoid any string changes that are not absolutely needed. The Image Properties dialog only exists because the metadata plug-in is not yet ready for prime time. As soon as the plug-in is considered complete and stable, we won't need the core dialog any longer and the two dialogs can be merged into a single one. > Maybe you dont realise how frustrating and demoralising it is to put in > time to come up with improvements, code and submit patchs only to see them > bounced. Sorry, but I couldn't accept the patches for the reasons given above. And now I have even put more time into this than it has taken David to come up with the patches in the first place. As a general rule, please ask before you write a patch. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Webdesign is wrong
On Tue, 2007-06-26 at 01:30 +0200, peter sikking wrote: > [...] > actually right now I am specifying how the selection tools should deal > with long, very narrow selections, with the web guys in mind. Please don't forget other users :-) I routinely have a selection that's, say, 10,000 pixels by roughly 40 pixels. This might not be a usual case for Web graphics... 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] A few simple patches
On Tue, 26 Jun 2007 08:50:44 +0200, Sven Neumann <[EMAIL PROTECTED]> wrote: > Hi, > > On Tue, 2007-06-26 at 11:58 +0930, David Gowers wrote: >> filepath.diff adds a 'file path' field to the 'Image Properties' >> dialog; I did this after some discussion between gg and myself on the >> importance of being able to find out the path easily. > > That's already on my TODO but I will probably do it differently than > your approach. > Unless what he's implemented is bad why not just comit anyway until you get around to doing it better/diffeently? It would be one less task on your busy schedule and one more lose end tidied up for 2.4 >> Image_metadata.diff changes the title used by the 'metadata' plugin >> for its window. Mainly, it's just so that there are not two different >> dialogs both titled 'Image Properties' available. > > The metadata plug-in is unfinished and not supposed to be part of the > next stable release anyway. Perhaps it is time that we stop building and > installing it. > Well it's true it does not seem to do much so it may be best no to build it if it's been pushed to a future release. Still committing the name change would not be a bad move since David has coded it. You've said you were very frustrated about not getting 2.4 out yet. May I gently make the point that if you could be a little more flexible in accepting others contributions even if not _exactly_ the way you would chose for it to be done you would get more contributions and contributers. Maybe you dont realise how frustrating and demoralising it is to put in time to come up with improvements, code and submit patchs only to see them bounced. It really leaves one with the feeling "why did I bother?". Clearly you're not going to accept everything anyone comes up with but everyone needs to find thier motivation for contributing to OSS. I think this often means fixing an personal annoyance or adding a feature we'd like to see. Getting things refused without a what seems to be a firm reason is disheartening and removes the motivation to make further contributions. Please don't take that the wrong way , it's just something you may like to consider that could help the project gain momentum. regards, gg/ ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] [Fwd: upgrading GNU packages to GPLv3]
Von: Sven Neumann <[EMAIL PROTECTED]> > I am forwarding this mail from the FSF to the developer list for your > information and for discussion. The attached mail is a bit low on pointers to actual changes. The sources cited in the Wikipedia GPL article include diffs (some official, some unofficial) by Groklaw and FSF. See http://en.wikipedia.org/wiki/GNU_General_Public_License#Version_3 Do we currently have to consider any technical problems (e.g. some file which do not mention "version 2 or any later")? Reagrds, Michael -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
