Greetings, everyone.
Before I get to todays announcement I need to clear up a possible
misunderstanding about the Tiny-Fu plug-in. One person on #gimp thought
they might lose the ability to use Script-Fu if they installed Tiny-Fu.
Applying the patch file to hook Tiny-Fu in to a copy of the GIMP
On Wednesday 21 July 2004 09:42 am, Sven Neumann wrote:
Sure, the plug-in is far from perfect. There's some code in compose.c
that tries to guess some useful default values for the layers it
preselects. This code could certainly be improved. I am not sure
though if it makes sense to attempt
Hi,
Alan Horkan [EMAIL PROTECTED] writes:
If you still reject the idea I would ask you to keep the toys in mind when
it comes to menu reorganisation. (Wiki is still down otherwise I'd add
this to the menu reorganisation document we had there).
The Gnome HIG recommends:
Thanks for all the people who answered.
It turned out to be as simple as attaching a gimp-comment and jpeg-exif-data
parasites to the image.
(of course generating jpeg-exif-data is not trivial. Only implemented for my
Nikon D70 at the moment. I guess others who like more formats will have to
Greetings, Markus (and everyone else).
At 07:47 PM 07/16/2004, you wrote:
this is a trivial plug-in that implements one single call:
file-get-type path
[snip]
I'm giving this another shot (after bug #145370, taking your feedback into
account - TinyScheme currently lacks a similar feature), because
Greetings, all.
I want to define some constants related to file type for use in Tiny-Fu. My
current thinking is to use FILE_TYPE_FILE (0), FILE_TYPE_DIR (1), and
FILE_TYPE_LINK (2). The last one being for *nix systems only. Are
there any other file types that should be handled (ie. nodes on
On Sun, 18 Jul 2004 17:47:05 +0200, Daniel Egger [EMAIL PROTECTED] wrote:
... with the integration of GEGL and more flexible data
types it might be worth to look into that again. I'd certainly
enjoy the idea of doing the composition using the GPU and
shader programs.
The problem might be when
Hi!
Im wondering, how powerfull is the plugin variations from photoshop.
Its really usefull for face drawing. (My friend have showed it to me.
And equally I have a video tutorial of this)
How its accessible from the menu:
http://www.pvvbitech.hu/fotok/variationMenu.png
How it is look like:
On Wednesday 21 July 2004 09:20 pm, you wrote:
For a start, I'm attaching a patch that makes compose use the layers in
reverse order (if the image has more than MIN_COMPOSE_LAYERS = 3 layers,
otherwise use old behavior). No attempt is currently made to guess the
mode.
Sorry, should read
On Wed, 21 Jul 2004, Alan Horkan wrote:
http://bugzilla.gnome.org/show_bug.cgi?id=148027
Given that some less used file formats have been removed in recently
releases on the basis of less code to maintain and less general clutter I
suggested that the old Toys be removed from the Gimp for
So at the most concrete possible level, here is a suggestion on
how to start:
Step 1: Add a Color Management page to the Preferences.
Step 2: Add enable/disable color management and working
colorspace options to the page. To start with, sRGB will
be the only option for the latter, but the
Here is what I would do, and it wouldn't be very hard to code up:
1) Make decompose attach a parasite called decompose-info to
each layer it produces, specifying the type of decomposition
and listing the source layer and the layers that are created.
2) Split compose into two PDB
This is not a gimp question, but perhaps there is someone here who can shed
light on this issue,
How (or can you) combine errors/noise in HSV into one error/noise figure
which reflects the total human visual error perception.
I am sure this is not a good formulation of the question. Here is
If you still reject the idea I would ask you to keep the toys in mind when
it comes to menu reorganisation. (Wiki is still down otherwise I'd add
this to the menu reorganisation document we had there).
The Gnome HIG recommends:
On 21 Jul 2004, Sven Neumann wrote:
Dave Neary [EMAIL PROTECTED] writes:
I think it would be even more useful to set the compose mode to the
last used decompose mode, rather than the last used compose mode (if
you get my meaning).
Well, this is doable but it would require closer
Hello all,
Short version:
I am looking for a very simple utility for annotating graphics. I can't find
anything suitable so I may have to make one. I think a sub-set of the Gimp
might work. If there are any persons who would be interested in discussing
this I would like to hear from you.
Long
Hi,
I don't understand what you want... GIMP's Filter Pack plug-in
is apparently the same as photoshop's Variations...
What exactly do you miss?
ciao,
--mitch
khiraly [EMAIL PROTECTED] writes:
Im wondering, how powerfull is the plugin variations from photoshop.
Its really usefull for face
Joseph Heled writes:
How (or can you) combine errors/noise in HSV into one error/noise
figure which reflects the total human visual error perception.
HSV is the wrong colorspace to use for this purpose. The LA*B*
colorspace was designed to do what you are trying to accomplish:
supposedly,
FYI, Windows 2000 and XP both (partially) support variaties of hard and
symbolic links under NTFS in certain scenarios. Then of course there are
also the half-ass implemented Windows shortcut files (*.lnk). Finally,
software also exists that allows Windows to access a *nix based file system
Joseph Heled writes:
It turned out to be as simple as attaching a gimp-comment and
jpeg-exif-data parasites to the image.
Note that in Gimp 2.1 the exif data parasite has been renamed
exif-data, because it is not specific to jpeg files.
Best,
-- Bill
__ __
Hi, I'm a student who's developing a GIMP plug-in.
I've been reading the API's documents but i haven't found the solution.
Two questions:
1º When i execute my plug-in for 2nd time, i'd like to configure the
parameters like the user introduce the first time. Is there any gimp
memory to save the
Hi Javi,
javi palau wrote:
Two questions:
1º When i execute my plug-in for 2nd time, i'd like to configure the
parameters like the user introduce the first time. Is there any gimp
memory to save the values introduced by the user?
You can tell when a plug-in is re-run by testing the run
On Wednesday 21 July 2004 08:07 pm, Kevin Cozens wrote:
This is just a taste of the possibilities for scripting in GIMP using
Scheme based scripts with Tiny-Fu. What would you like to do today? :-)
Thank you for your explanation, Kevin. I was not aware of all the useful
extensions you are
I want to define some constants related to file type for use in Tiny-Fu. My
current thinking is to use FILE_TYPE_FILE (0), FILE_TYPE_DIR (1), and
FILE_TYPE_LINK (2). The last one being for *nix systems only. Are
there any other file types that should be handled (ie. nodes on *nix
systems)?
javi palau ([EMAIL PROTECTED]) wrote:
2ºHow i can know the language used by GIMP?. I've been searching in the
gimprc file, but i haven't found anything.
We use the gettext library to determine what language the text in our
user interface should be. In fact gettext does all the hard work for
On Thu, 2004-07-22 at 17:17, Markus Triska wrote:
Maybe I have not given this enough thought, but I would opt for
FILE_TYPE_NONEXISTANT (although this can hardly be called a file type) so
there is some well-defined behaviour if the path to check points nowhere.
I have decided to use
On 22.07.2004, at 23:19, Simon Budig wrote:
We use the gettext library to determine what language the text in our
user interface should be. In fact gettext does all the hard work for
us.
Not quite but almost. :) The choice of language is expressed by
setting environment variables. Those are
On Sat, Jul 17, 2004 at 01:40:16AM +0200, Niklas Mattisson wrote:
New things:
* User-FAQ - This needs to be added to the website as soon as possible.
I do not think we have problems with questions but problems with how to
design the FAQ.
Yeah - i collected some questions because
Hi,
William Skaggs [EMAIL PROTECTED] writes:
A) Compose would allow you to use any set of equal-sized
grayscale layers to assemble into an RGB layer. (One of
the annoyances of compose now is that it only works on
layers that were produced using decompose.)
Huh? At the
Hi,
William Skaggs [EMAIL PROTECTED] writes:
So at the most concrete possible level, here is a suggestion on
how to start:
Step 1: Add a Color Management page to the Preferences.
Step 2: Add enable/disable color management and working
colorspace options to the page. To start with, sRGB
Hi Sven,
Sven Neumann wrote:
William Skaggs [EMAIL PROTECTED] writes:
So at the most concrete possible level, here is a suggestion on
how to start:
Step 1: Add a Color Management page to the Preferences.
Step 2: Add enable/disable color management and working
colorspace options to the page. To
Hi,
javi palau [EMAIL PROTECTED] writes:
Hi, I'm a student who's developing a GIMP plug-in.
I've been reading the API's documents but i haven't found the solution.
I strongly suggest you look at some of the plug-ins distributed with
GIMP and also get your hands on the gimp-plugin-template
(repeat) I am developing a plugin which loads raw images from digital cameras
(CRW,NEF etc).
There is actually lots of the functionality I need support (and some I need to
do) in the gimp already, if only the gimp was 16 bits ready.
So, I wonder, any estimate how far in the future it is?
33 matches
Mail list logo
