On Fri, 28 Jan 2000 01:38:32 +0100, Marc Lehmann <[EMAIL PROTECTED]> said:
>Ok. I've just enabled automatic mirroring from the sourceforge cvs
>back to the gimp cvs.
FWIW, I think this should be used sparingly. It is my belief that
we should try to move plugins into a separate package from the
On Fri, Jan 28, 2000 at 01:38:32AM +0100, Marc Lehmann wrote:
>plug-ins/maze/*
>
> is being written back. This (unfortunately!!) means that changes done to
> these files in the gimp cvs will get overwritten. I've not found a better
> way to synchronize two cvs trees better (maybe CVSup would
I'd really like to see the setting for default brush reappear. So
much so that I'd do it myself.
Hows this fit with the freeze? I hate to violate the freeze, esp
since its been getting better. But I'm SO SICK OF THAT CALIGRAPHIC
BRUSH (10x10)! Comments?
Seth
[EMAIL PROTECTED]
--
~/.sig:
Ok. I've just enabled automatic mirroring from the sourceforge cvs back
to the gimp cvs.
The file gimp/PLUGIN_CVS in the cvs tree controls which paths are mirrored
and which are not. If anything goes havoc just delete that file and the
script will stop doing anything.
At the moment, only
Cha
The Translation Status Report is now available nicely formatted and
daily uptodate at:
http://sven.gimp.org/1.1/i18n.html
Hopefully this motivates people to contribute to the translations...
Salut, Sven
Hi everybody,
I've now got a couple of SGI's, three Wacom tablets
(SD510C, UD1218, Intuos 9X12) and two wacom
drivers (Wacom 4.4.0 release and a home-grown)
plus the current Gimp in the same room, but the
various combinations and permutations do not
work together all that well.
The most workable
On 27 Jan, Robert L Krawitz wrote:
> diff -rc print/README /tmp/print/README
Please use diff -u for further patches to preserve readability and
attach them to prevent line wrapping to slash the patch
--
Servus,
Daniel
O.K. There is a new project on sourceforge, "Gimp Plug-ins", for a lack of
a less imaginative name. To put it differently:
"Get your FREE acount NOW!"
For those who don't know: There was a discussion on gimp-developers on
how to better manage the multitude of plug-ins that are part of the gimp
d
On Wed, Jan 26, 2000 at 07:28:13PM -0500, Kelly Lynn Martin
<[EMAIL PROTECTED]> wrote:
> 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
> offe
diff -rc print/README /tmp/print/README
*** print/READMEThu Dec 16 14:44:01 1999
--- /tmp/print/README Thu Jan 13 18:41:34 2000
***
*** 1,4
! Print plugin for the Gimp. Version 3.0 by Robert Krawitz
<[EMAIL PROTECTED]> based on version 2.0 by Michael Sweet
<[EMAIL P
From: Sven Neumann <[EMAIL PROTECTED]>
Date: Thu, 27 Jan 2000 14:17:48 +0100
> Just a comment about the print plugin (I don't know if you've actually
> done it) -- I suppose it's no disaster to do that to 3.0, but the
> intent is that the core of the print plugin live standalone wi
>
> Just a comment about the print plugin (I don't know if you've actually
> done it) -- I suppose it's no disaster to do that to 3.0, but the
> intent is that the core of the print plugin live standalone without
> the Gimp, e. g. in Ghostscript, or as a CUPS filter, or whatnot.
>
We might also
Date: Thu, 27 Jan 2000 04:14:49 -0800
From: "Martin Weber" <[EMAIL PROTECTED]>
I removed the rgb to hsv (and hsv to rgb) routines from several plugins
because this routines are now in libgimp. But there are still some
plugins like compose, decompose and flame where I din't found th
Well, here's the updated translation status report. This might be
of interest for people who want to help finishing the translations
for 1.2. Before you start to work on one of the files, please get in
contact with the maintainer (his/her address should be in the po-file).
po:
Well, here's the updated translation status report. This should be
of interest for people who want to help finishing the translations
for 1.2. Before you start to work on one of the files, please get in
contact with the maintainer (his/her address should be in the po-file).
po:
cs.po > 1391 tra
Gflare uses gtkmultioptionmenu to select a gradient. Wouldn't it be
better to use the same way to select a gradient like the main GIMP
window? Cause I haven't the time to can someone else do this?
On Thursday, 27 Jan 2000, Martin Weber wrote:
> I removed the rgb to hsv (and hsv to rgb) routines from several plugins
> because this routines are now in libgimp. But there are still some
> plugins like compose, decompose and flame where I din't found the time
> to do so. Can someone other do th
I removed the rgb to hsv (and hsv to rgb) routines from several plugins
because this routines are now in libgimp. But there are still some
plugins like compose, decompose and flame where I din't found the time
to do so. Can someone other do this?
Hi!
Looking at bug report #5523, I saw the following:
>The script crashes reproducable when called with the standard settings.
>I have checked that the selected font is installed. The problems seems to
>be located in text_fontname_invoker (), so the problem migth be a bug in
>the gimp core.
Hav
19 matches
Mail list logo
