Accessing Plugin libraries from ftp sites
Hi, I am trying to pull down the plugin libraries for Gimp and am having a hard time connecting to either ftp://ftp.gimp.org and ftp://ftp.x.org. Where else can I get the libraries? thanks David
Re: Speaking of additional plug-ins
On Wed, Jan 26, 2000 at 01:24:44AM +0100, Sven Neumann wrote: enough. Ideally, this project should completely replace the registry. A web interface to the repository together with tips for installation will be essential. Plug-ins should be released on a regulary basis, Better yet, a GIMP interface. If we are to change the entire plug-in architecture anyway, we should make a single way of compiling and installing them. /* Steinar */
Re: Great job!
Pierfrancesco Caci spontaneously blurts out: Hi, I wasn't able to use Gimp for a while, say since version 1.1.11, either because it didn't compile or because it segfaulted. Now I'm successfully using 1.1.15 and I wish to congratulate for the great job and all the new features. Thank you I concur. I was really trying to use whatever came standard with RH6.0 and things are *WAY* better with the latest and greatest. I was doing website stuff and with the old version, I have to continually go back to Photoshop (on my mac) to get things done in a crunch. This round of web assets was created without photoshop at all (actually I used it to scan the images only). I found it to be far more stable and actually work the way I expected it to work. Great job guys! In hopes of making Gimp even better, I have initiated the piGIMP project (pigimp.sourceforge.net) and should hopefully have some very very preliminary Photoshop vs GIMP benchmarking numbers at LWE next week. To quote David, my co-conspirator in the project "Dean, I'm going to kill you for making me install NT". Please send us your thoughts and ideas! -Dean Johnson Tool Hooligan Cluster Admin Tools Jessie Project Silicon Graphics Inc.Eagan,MN (651) 683-5880 "I am Dyslexic of Borg, Your Ass will be Laminated"-- unknown
Re: Speaking of additional plug-ins
On Wed, 26 Jan 2000 14:31:52 +, "Steinar H. Gunderson" [EMAIL PROTECTED] said: Better yet, a GIMP interface. If we are to change the entire plug-in architecture anyway, we should make a single way of compiling and installing them. I've thought about this somewhat. I had a vague idea in mind for how to redo the UI for 1.4/2.0, which included a considerably different way of handling plugins. Plugins would be installed w/i the Gimp interactively (a noninteractive installation procedure would be offered for system administrators) with the user being asked where to install the plugin in the menu tree and so forth. I've never gotten back to it, though. Kelly
Fw: segnalazione bug GIMP 1.1.14 (win32)
A mail from a windows user of Gimp. - Original Message - From: "Dexter" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, January 26, 2000 12:10 AM Subject: segnalazione bug GIMP 1.1.14 (win32) PC: Notebook Acer TravelMate 512T celeron 366 32 Mb ram Win 98 Versione di gimp: 1.1.14 Errore: GLib-CRITICAL **: file giochannel.c: line 84 (g_io_channel_write): assertion `channel != NULL' failed. ** WARNING **: plug_in_handle_proc_run: ERROR
Re: [gimp-devel] Re: End-user feedback: Perl logulator innerbevel
On Tue, Jan 25, 2000 at 10:28:04PM -0500, Kevin Cozens [EMAIL PROTECTED] wrote: Could you provide the subject line of any one of the messages when you reported the problems with script-fu which you say have not been fixed and/or a date when one of the messages was posted to the list? The most recent message I can find is Subject: script-fu maintained? Message-ID: [EMAIL PROTECTED] Date: Thu, 2 Dec 1999 20:48:53 +0100 The result of that thread was that I changed script-fu function names from using "-" to using "_", but the bug persisted. I cannot find the bug report to the bug tracking system, but it might have been so old that it is in the wilberworks bug tracker. Due to a crash I do not have archives of earlier messages, but this error has benn popping up every few months since shortly after 1.1 came out. I don't the above is script-fu related as such. This is all I was able to find so far. Indeed it isn't. -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
Re: Remove the Stack Trace...
On 25 Jan, Marc Lehmann wrote: I really do not understand this. The stacktrace simply does not work. Attaching a debugger is much better, but still: the core file a segv would create would be _far_ more reliable. I buy the argument that users can do bug reports better with an automatic stacktrace, but I don't buy that it makes it easier for developers. You are absolutely right there so I would suggest disabling it for normal use and enable it for distributions I know you like those small patchlets... so here is your personal one... :)) -- Servus, Daniel diff18.gz
