Re: cmon guys, no patch from 1.1.32 to 1.2??
> On 27 Dec, [EMAIL PROTECTED] wrote: > > > You know since you take time to answer my posts, I might as well too. > > Compared to your "limited" 64k how does 9600 that disconnects every 5 > > minutes sound to you? And the fact that downloading something like a > > full gimp 1.2.0 would take close to 2 or 3 hours? And the fact that > > those 2-3 hours would cost me somewhere in the neighborhood of $5 PLUS > > telephone charges? Now go think again. 1. Why is your internet connection so slow I know a lot of people in Japan, they have all got nice connections. Are you poor? 2. Even if you pay $100, I think it's still damn cheap compared to Photoshop. I used to use Photoshop. But why??? For web design, only the gimp's text tool(including Gdyn Text IMHO) is poor compared to Photoshop. The scriptibililty and multi-threading is very nice. Both apps have the basics. 3. Your further posts were imature. Grow up. 4. I agree a patch would have been cooler and I didn't like it myself. But I must admit that I didn't know Gimp is available via CVS. Great! Who cares about patches when CVS is available? 5. How do you update X? 6. Dear Mr. Timecop, grown ups post with real life names... -- Mat
Re: What's with GIMP and TIFF already?
> [ Problems opening Windows TIFF images] > sounds to me like your using a devlelopment port based in > Winblows...oh...you are. your TIFF library that GIMP is referencing > is buggered mate. > GIMP doesnt save TIFFs, nor open them, libtiff does (dunno > what the library is called in windoze). the problems with > the browser may have something to do with your filesystem. > GIMP was written under ext2fs, msw2000 doesnt use that, maybe > thats the problem. I don't think that's is the problem. I can't open most PC/Mac TIFF images, like from Photoshop, without resaving them with ACDSee. The rest of the world has no problems, but Gimp (or libtiff) does. I'm using Linux. -- Mat
OT:
Am Mon, 18 Dez 2000 schrieben Sie: > It will be very easy to make a gnome-frontend for gimp-2.0, as it will be > modular enough to be used in about any environment. > > I am also quite sure that the regular gimp hackers will help with the > gnome frontend (as opposed to kde, since most people know gtk and maybe > gnome but not kde). Hmm, I live in Germany (and your name suggests the the same) and I don't know _anybody_ using GNOME. Everybody I know is either using KDE or Windowmaker. Oh and one guy is using Enlightenment. But I guess you are talking from the coders point of view. There seems to be a reality difference between the coders and the end-users. Why? I guess it's because most coders hate win and most end-users come from win. :-) Will a coder be able to write QT front end as well? But actually, though I use KDE myself, I couldn't care less if an app comes along as a GTK or an QT version. Both GNOME and KDE (and GIMP of course) are great projects. Thanks to you coders. -- Mat
Re: GIMP 1.1.30 compile error
Am Son, 10 Dez 2000 schrieb Matthew Colton: > Hi all! > For the first time after a long while, the GIMP will not compile on my machine. > :-( > I'm running SuSE Linux 7.0 Prof. > I patched GIMP 1.1.30 from 1.1.29(as always). This the error I get. Any ideas? > > > make[3]: Entering directory `/home/mat/src/gimp-1.1.28/plug-ins/gimpressionist' > Making all in Brushes > make[4]: Entering directory >`/home/mat/src/gimp-1.1.28/plug-ins/gimpressionist/Brushes' > make[4]: *** No rule to make target `snow1.pgm', needed by `all-am'. Stop. > make[4]: Leaving directory >`/home/mat/src/gimp-1.1.28/plug-ins/gimpressionist/Brushes' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory `/home/mat/src/gimp-1.1.28/plug-ins/gimpressionist' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/home/mat/src/gimp-1.1.28/plug-ins' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/home/mat/src/gimp-1.1.28' > make: *** [all-recursive-am] Error 2 The problem is a missing file (snow1.pgm) in the patch... Thanks to Alex for sending me the file. GIMP compiled fine after I copied the file to plugins/gimpressionist/Brushes. -- Mat
GIMP 1.1.30 compile error
Hi all! For the first time after a long while, the GIMP will not compile on my machine. :-( I'm running SuSE Linux 7.0 Prof. I patched GIMP 1.1.30 from 1.1.29(as always). This the error I get. Any ideas? make[3]: Entering directory `/home/mat/src/gimp-1.1.28/plug-ins/gimpressionist' Making all in Brushes make[4]: Entering directory `/home/mat/src/gimp-1.1.28/plug-ins/gimpressionist/Brushes' make[4]: *** No rule to make target `snow1.pgm', needed by `all-am'. Stop. make[4]: Leaving directory `/home/mat/src/gimp-1.1.28/plug-ins/gimpressionist/Brushes' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/mat/src/gimp-1.1.28/plug-ins/gimpressionist' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/mat/src/gimp-1.1.28/plug-ins' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/mat/src/gimp-1.1.28' make: *** [all-recursive-am] Error 2 Thanks in advance! -- Mat
Re: I inform the author ;-)
Am Sam, 21 Okt 2000 schrieben Sie: > On Sat, Oct 21, 2000 at 02:13:33PM +0200, regis rampnoux <[EMAIL PROTECTED]> wrote: > gimp/plug-ins/perl/ > > Warning: the following files are missing in your kit: > > po/Makefile.PL > > po/update.sh Had the same error too, but Gimp (1.1.28) compiled well anyway and works fine, wierd... -- Mat
Letter Spacing and a "Spam sux!!"
Hi The text tool offers the opportunity to change line spacing, but not letter spacing, it this in the works? I personally think this is a very basic function, is it so hard to program? And: C'mon, what's going on here, why all the spam? Will this change in the near future? Sorry, but I'm really annoyed... -- Mat
1.1.26 and still having scanner problems
Hi, since 1.1.25 I can't link xscanimage or xsane as a gimp plugin. Gimp freezes on startup while scanning the plugins. Just to be sure it's not something I did, I recompiled 1.1.24 and tested it. Both xsane and xscanimage work fine with 1.1.24, but not with 1.1.25 or 1.1.26. Since we're getting close to 1.2 this is making me nervous... -- Mat
Gimp 1.1.25 and scanner
Hi, I've just upgraded from 1.1.24 to 1.1.25. Everything compiled well, but now I can't scan directly into Gimp anymore. If I link xscanimage to my .gimp-1.1/plug-ins directory, the Gimp freezes while checking the plug-ins on start up. No error messages, no nothing, just freezes. This is wierd, since xscanimage itself still works fine. Any ideas? Thanks! -- Mat
Re: GDynText
Am Mit, 30 Aug 2000 schrieb ebi5: > How do you place text generated by GDynText anywhere other than the top > left corner? use the move tool. -- Mat
