Re: [Gimp-user] gimp on 64 bit OS
On Friday 08 April 2005 17:41, Sven Neumann wrote: > Hi, > > Ketil Froyn <[EMAIL PROTECTED]> writes: > > Thanks for the responses. I guess one major limiting factor could > > be the types used internally by the GIMP. For instance, if it > > does operations on uint32 type variables internally, I'd think > > the compiler needs to be pretty clever to make use of 64 bit > > operations. But now I'm getting into deep waters here here...:) I > > was hoping someone in the know could confirm whether there's any > > point going to 64 bit to make the GIMP faster, rather than just > > getting a faster 32 bit CPU. > > The only real advantage you will get from a 64bit CPU is that you > can address more than 4GB of RAM and will be able to handle very > large images in GIMP provided that you actually stuff more than 4GB > of RAM into your hardware. > Actually, these 64 bit CPUs have more registers as well. I'd expect the compiler to make a better usage of them. Does this happen? Ketil, as for the 64 bit integers - there could not possibly be a program benefiting from this directly. They still do one operation a time. Multiple operations with a single instruction (SIMD) is what would speed up an app CPU usage are the correlate processing units like 3Dnow, MMX and SSE. I'd guess the GIMP takes advantadge of MMX, SSE, SSE2, and these had not improved on the new 64 bit chips (btw, the registers relevant to SIMD were already 64 or 128 bit wide way before the move to 64 bit on the general purpose registers). Certainly the SSE2 code might get some improvements..there is room for implementing 3Dnow code as well - it may not even get faster than SSE2 code on Athlons, but it would quite a task for one to perform. Do you have some spare time to learn coding 64/128 bit SIMD? :-) Regards, JS -><- > > Sven > ___ > Gimp-user mailing list > Gimp-user@lists.xcf.berkeley.edu > http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Speech bubble
David Holland writes: > Sorry I am very new to using the GIMP. > How do I add a speech bubble to a picture ? I had a lesson on that in the Linuxchix GIMP course: it was the second half of Lesson 5 in http://www.linuxchix.org/content/courses/gimp/ If you're new to the gimp and haven't used layers and text before, I'd recommend reading Lesson 3 first. There's also lots of great information in "Grokking the GIMP", at gimp-savvy.com (not by me, I'm just a satisfied buyer of the book). ...Akkana ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] file open with gimp 2.2.4 and AFS
On Fri, Apr 08, 2005 at 01:27:24PM +0200, Reinhard Drube wrote: > >>> > is there a way to avoid that the whole file tree > >>> > is accessed upon 'file open'? Running gimp on a > >>> > unix machine with AFS client contacts every AFS > >>> > cell around the world. That lasts >15 minutes > >>> > for a simple file open! So I am looking for > >>> > a gimmick at least to avoid access to path /afs. > >>> > I think the same problems can occur with nfs mounted > >>> > file systems. > >>> > > >>> > Before that I operated with gimp 2.0.3 where only > >>> > the path was scanned where gimp was started. This > >>> > worked fine. > > >> File a bug against gtk+. The old filesel special cased /afs and /net, > >> the new one doesn't appear to. > > I think this is not the fact. If I compile > > gtk+-2.4.14/examples/filesel/filesel.c That uses GtkFileSelection, not GtkFileChooser. Like I said, GtkFileSelection (the old, deprecated widget) special cased things. GtkFileChoose does not. > this program works fast and fine. There you have a pulldown menu > which contains the cwd and all supaths. But without inspecting them > until I select them! > > On the other hand the 'open file' of gimp 2.2.4 offers one clickable > button per subpath. And as I see on the console these subpaths are > inspected. That is absolutely nonsens. The fact that the dialogs look *completely* different, as you noticed, should've been a tip off that you were testing different things. > So if some of you can tell me where is the source file I can change > I will do. If you feel like trying to fix it yourself, start with gtkfilesystemunix.c. There isn't any special casing infastructure there though, so if you were hoping for a one-line change, it's going to be more work than that. -Yosh ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] Speech bubble
Sorry I am very new to using the GIMP. How do I add a speech bubble to a picture ? Send instant messages to your online friends http://uk.messenger.yahoo.com ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] file open with gimp 2.2.4 and AFS
Hi, > I think this is not the fact. If I compile > > gtk+-2.4.14/examples/filesel/filesel.c That is the old file-selection widget, not what GIMP 2.2 is using. Please follow Yosh's advice and file a bug-report against the GtkFileChooser widget. Sven ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] gimp on 64 bit OS
Hi, Ketil Froyn <[EMAIL PROTECTED]> writes: > Thanks for the responses. I guess one major limiting factor could be the > types used internally by the GIMP. For instance, if it does operations on > uint32 type variables internally, I'd think the compiler needs to be > pretty clever to make use of 64 bit operations. But now I'm getting into > deep waters here here...:) I was hoping someone in the know could confirm > whether there's any point going to 64 bit to make the GIMP faster, rather > than just getting a faster 32 bit CPU. The only real advantage you will get from a 64bit CPU is that you can address more than 4GB of RAM and will be able to handle very large images in GIMP provided that you actually stuff more than 4GB of RAM into your hardware. Sven ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] file open with gimp 2.2.4 and AFS
>>> > is there a way to avoid that the whole file tree >>> > is accessed upon 'file open'? Running gimp on a >>> > unix machine with AFS client contacts every AFS >>> > cell around the world. That lasts >15 minutes >>> > for a simple file open! So I am looking for >>> > a gimmick at least to avoid access to path /afs. >>> > I think the same problems can occur with nfs mounted >>> > file systems. >>> > >>> > Before that I operated with gimp 2.0.3 where only >>> > the path was scanned where gimp was started. This >>> > worked fine. >> File a bug against gtk+. The old filesel special cased /afs and /net, >> the new one doesn't appear to. I think this is not the fact. If I compile gtk+-2.4.14/examples/filesel/filesel.c this program works fast and fine. There you have a pulldown menu which contains the cwd and all supaths. But without inspecting them until I select them! On the other hand the 'open file' of gimp 2.2.4 offers one clickable button per subpath. And as I see on the console these subpaths are inspected. That is absolutely nonsens. So if some of you can tell me where is the source file I can change I will do. Thanks for help! Reinhard ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Error trying to compile Perl for gimp 2.0
On Thu, 7 Apr 2005 16:15:11 +0200 Rikard Johnels <[EMAIL PROTECTED]> wrote: > Why cant i compile? > > [EMAIL PROTECTED]:~/Downloads/Gimp-2.0> perl Makefile.PL > checking for gimp-2.0... no > checking for gcc... cc > checking for C compiler default output... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether cc accepts -g... yes > checking for cc option to accept ANSI C... none needed > checking for gimptool-2.0... /opt/gnome/bin/gimptool-2.0 > checking for GIMP - version >= 2.0.0... no > *** Could not run GIMP test program, checking why... > *** The test program failed to compile or link. See the file config.log for > the > *** exact error that occured. This usually means GIMP was incorrectly > installed > *** or that you have moved GIMP since it was installed. In the latter case, > you > *** may want to edit the gimptool-2.0 script: /opt/gnome/bin/gimptool-2.0 > configure: error: ** unable to find gimp, make sure it's in your path > (version > 1.3.15+ required!) > > [EMAIL PROTECTED]:~/Downloads/Gimp-2.0> rpm -q gimp > gimp-2.2.4-1.guru.suse92 > > [EMAIL PROTECTED]:~/Downloads/Gimp-2.0> rpm -q gimp-devel > gimp-devel-2.2.4-1.guru.suse92 > > [EMAIL PROTECTED]:~/Downloads/Gimp-2.0> file `which gimp` > /opt/gnome/bin/gimp: symbolic link to `gimp-2.2' > At a rough guess, your LD_LIBRARY PATH is probably /usr/lib Set your LD_LIBRARY_PATH=/opt/lib:/usr/local/lib:/usr/lib You better find out where your gimp-2.0pc file is and maybe amend that path as well PKG_CONFIG_PATH=/opt/lib/pkgconfig:/usr/local/lib/pkgconfig/:/usr/lib/pkgconfig/ HTH Owen ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
