On 23 Feb 2001, Michael Natterer wrote:
That lessens but does not solve the problem that the code is more
complicated because of the destruction of tools due to state changes.
I'm quite a bit biassed about wether we should destroy tools after use
or not, but IMHO a tool should simply be
On Thu, 29 Mar 2001, Guillermo S. Romero / Familia Romero wrote:
[EMAIL PROTECTED] (2001-03-29 at .26 -0700):
Ugh, speaking of error, all so-called "letter" paper isn't necessarily the
same size. I've had two "letter" papers vary in size by almost half a
centimeter!
Oooh well,
On 21 May 2001, Sven Neumann wrote:
Hi,
I'd suggest you use this mailing list to discuss the future of
www.gimp.org so we can all contribute. I'd also suggest you don't try
to tackle it all by your own but try to find a group of people willing
to do the work.
Adrian and I discussed the
On 2 Jun 2001, Sven Neumann wrote:
Hi,
Marc Lehmann [EMAIL PROTECTED] writes:
It's simple: i had(!) a script which loaded and analyzed thousands of
(checked) jpegs and (unchecked) gifs. Broken gifs tend to hurt gimp badly,
with effects ranging from gimp filling all virtual memory to
On Thu, 7 Jun 2001, Federico Mena Quintero wrote:
Agreed. Just pick a reasonable default based on the amount of memory
in the system. And please use libgtop to figure that out instead of
some horrid hack like cat /proc/meminfo.
If we're going to depend on Yet Another Library, might I
On Mon, 11 Jun 2001, Gustaf Barkstrom wrote:
Hi,
I joined this newsgroup to see if I could get some help compiling gimp
1.2.1. Am I in the right place? Is there a help list for sysadmins etc.
who are having compilation/configure problems? deja news (groups.google.com)
has yielded
On 6 Oct 2001, Daniel Egger wrote:
Am Die, 2001-10-02 um 19.14 schrieb 1002042874:
there is probably no need for XML as there are no attributes etc.
If you use XML for texts like tips or dialogparts then attributes
are being used for specifying the language the text is in.
We can also
I'm currently in end-of-semester crunch time, so I won't be working on
Gimp until after all of my semester projects are done.
The IRC addicts are probably already aware that my plans for after that
are:
* implement tool plug-ins with as little disturbance to the rest of Gimp
as is reasonable.
On 17 Dec 2001, Sven Neumann wrote:
Hi,
Nathan C Summers [EMAIL PROTECTED] writes:
Some horrible kludge could also be dreamed up involving GTKPlugs. That
would move the windowing system dependance down to the GDK level, but
would also make things ineligant, and it would
On Wed, 6 Feb 2002, Nick Lamb wrote:
http://www.ecs.soton.ac.uk/~njl98r/chocbox2.png
^^^
Looks very nice, but please, please call the last field Copyright
instead of Digital Rights Management.
Rockwlrs
On Wed, 6 Feb 2002, Dave Neary wrote:
If we go with the more generic metadata option, then we would have
the option of gimp-metadata-*. But that's minutiae at the moment.
Isn't the fact that it's a parasite metadata-y enough? I suppose it's
possible to attach a parasite to an image for
On Thu, 7 Feb 2002, Dave Neary wrote:
Marc Lehmann wrote:
There is no such thing as non-standard naming in this case. exif
doesn't provide a standard name, so you need to make one up. Wether
oyu make up one or 50 doesn't really matter, as long as it's
documented.
That's the major
Stage 1 of tool plug-ins is complete. That means that loadable modules
can be used as tools. An example plug-in (just the color picker hacked to
be a plug-in instead of a builtin) is available at
http://students.cs.byu.edu/~rockwlrs/testmodule.tgz
That file should be untarred in your
On Fri, 22 Feb 2002, Carol Spears wrote:
On 2002-02-22 at 1256.39 +0100, Sven Neumann typed this mail:
Hi,
Carol Spears [EMAIL PROTECTED] writes:
tonight i decided to try the cvs gimp-1.3. i found it very difficult to
convince the cvs server that i wanted the new gimp now,
I am going to need to make some changes to facilitate tool plug-ins.
First, a good amount of code needs to be shared between the core and the
plug-in. I've split off a libgimptool to contain this code.
Second, a lot of the information contained in the gimptool object needs to
be syncronized
On 23 Feb 2002, Sven Neumann wrote:
Nathan C Summers [EMAIL PROTECTED] writes:
[snip]
a good amount of code needs to be shared between the core and the
plug-in. I've split off a libgimptool to contain this code.
[snip]
Any comments? I will probably commit tommorow.
well, if you
On Sun, 24 Feb 2002, Branko Collin wrote:
Here's a PS 7 announcement:
http://www.adobe.com/products/photoshop/newfeatures.html
I wonder if that texture generator is a sort of resynthesizer plug-
in?
The healing brush sounds like a good idea. We could probably implement
it using a
There are three kinds of sharing that needs to take place. The base
classes (GimpTool, GimpSelectionTool, GimpTransformTool, GimpPaintTool,
GimpDrawTool, and k! GimpObject) need to share their structure
definitions in order to maintain and ensure binary compatibility.
The other tool
On Sat, 30 Mar 2002, Nick Lamb wrote:
On 29 Mar 2002, at 11:37, Piotr Legiecki wrote:
Does Gimp 1.3 work include making it possible (easier? maybe it was already
possible) to provide plug-ins/ modules that make Gimp understand more +
different types of palette, gradient, brush etc.
On 9 Apr 2002, Sven Neumann wrote:
Someone wanted a way to a enter zoom value numerically, so we might want
to use an entry/spinbutton instead.
Seems to me that an entry/spinbutton has all the advantages of the other
ui proposal with the extra advantage that you can quickly and easily go to
On 10 Apr 2002, Sven Neumann wrote:
Hi,
Nathan C Summers [EMAIL PROTECTED] writes:
- Provide an API that allows the plug-in developer to use the same
function for manipulating the image as well as the preview. The
preview would have to provide a drawable API and pixel-regions
On Fri, 12 Apr 2002, Jeff Trefftzs wrote:
(2) Is there a sensible workaround for the (apparently) limited string
length?
Have you tried using lists of single charactors instead? Note quite as
memory efficient, sure, but you can make a list as big as available
memory.
Rockwalrus
On 23 Apr 2002, Michael Natterer wrote:
Hi Rock,
sorry I did not comment on this earlier, I was quite busy since
returning from Guadec.
After a few weeks of silence, I figured that you didn't have anything
more to say, so I started commiting again. I have my own schedule, too.
As
On Thu, 25 Apr 2002, Hai Nguyen wrote:
Hi,
I am trying to modify GIMP to add some extra features but it's not
really something that I can do as plugin, does anyone know of any where
I can find detailed information on the way gimp actually works, any sort
of info especially on the actual
On Fri, 26 Apr 2002, Hai Nguyen wrote:
I did post a message on here before, basically what I would like to do is to
modify GIMP to be able to handle 48-bit images, I would then like to write a
plugin that would then be able read in a digital cameras RAW mode image
(36-bit interpolated into
Thumbing through the Gnome GTK Widget Repository, I found that someone has
already implemented pie menus for GTK. I'm still not sold on having pie
menus in GIMP, but at least it means that if we do find a way to make
useful pie menus, it won't take much work to implement them.
Hmm, maybe we
26 matches
Mail list logo
