Hi,
Joao S. O. Bueno [EMAIL PROTECTED] writes:
I have also one other improvement I think I could work on, and this
would be great, so I might even postpone the above PDB stuff:
Postscript saving plug-in.
Actually, I have a similar list of things I believe I can implement in
it, more or
On Monday 29 March 2004 07:21, Sven Neumann wrote:
Hi,
Hm,, I talk that much about postscript, because I have learned it, as it is
supposed to be human writable. PDF however is a neat subset, and although I
know little of it, I suppose I could handle PDF saving with ADOBE docs - that
is all of
Hi,
Joao S. O. Bueno [EMAIL PROTECTED] writes:
My idea of saving text as curves would be: - having implemented a
save vectors to postscript curves (which I had done in python-fu
for gimp 1.2), create a vector from text thouhgh the PDB, and them
use this vector to save as postscript curves,
Hi,
Joao S. O. Bueno schrieb:
Hi,
On Sunday 28 March 2004 16:47, Sven Neumann wrote:
snip
I have also one other improvement I think I could work on, and this
would be great, so I might even postpone the above PDB stuff:
Postscript saving plug-in.
Actually, I have a similar list of things I
Hi,
I have been thinking about how to improve the consistency of the
user interface for plug-ins, and have come up with a tentative plan
and the mechanism for implementing it, which I will outline here to
see if people think it is reasonable and workable.
First, though, a little terminology.
On Mon, Mar 29, 2004 at 10:09:37AM -0800, William Skaggs wrote:
First, though, a little terminology. As I will use the terms, a
plug-in is an external executable that interacts with the Gimp core
via the plug-in mechanism. A filter is a plug-in that changes a
drawable in some way. Only
From: Carol Spears [EMAIL PROTECTED]
would it be reasonable to have plug-ins that change the drawable to work
on a copy of the drawable? that would take away the need to
differentiate between the two.
The point is that things like Cancel and Okay buttons are only relevant
to a subset of
Hi,
William Skaggs [EMAIL PROTECTED] writes:
1) Every filter should produce a dialog when called interactively.
At the moment, some just do their thing without showing any dialog:
this is bad.
Why is this bad? There are plug-ins that are supposed to be completely
non-interactive. You call
1) Every filter should produce a dialog when called interactively.
At the moment, some just do their thing without showing any dialog:
this is bad.
Why is this bad? There are plug-ins that are supposed to be completely
non-interactive. You call them from the menu, they do their job. What
is
The problem is that the blurb and help strings as they are
registered with the PDB are (a) not meant to be user help and (b)
missing or not helpful in almost all plug-ins. Also these strings
would have to be translatable. This could be easily changed but before
you call for translation there
You have valid points Bill. However, popping up unnecessary dialogues will
also undesirably slow down and get in the way of many users. If you proceed
with your suggested changes, then I would strongly suggest an option to
bypass the dialogue for plug-ins that don't really need one.
Well, the
[EMAIL PROTECTED] (2004-03-29 at 1218.49 -0800):
1) Every filter should produce a dialog when called interactively.
At the moment, some just do their thing without showing any dialog:
this is bad.
Why is this bad? There are plug-ins that are supposed to be completely
non-interactive. You
a) Menu entries have a rule about Only those that request extra
interaction must have the dots. Non interactive things have no dots.
Interesting. I just automatically assumed that the dots meant that the
name was truncated, and never paid attention to them again.
c) Maybe over menu? Maybe
On Mon, 2004-03-29 at 23:53, William Skaggs wrote:
a) Menu entries have a rule about Only those that request extra
interaction must have the dots. Non interactive things have no dots.
Please include a line which states who you are quoting.
./Brix
--
Henrik Brix Andersen [EMAIL PROTECTED]
Hi,
William Skaggs [EMAIL PROTECTED] writes:
The problem is that the blurb and help strings as they are
registered with the PDB are (a) not meant to be user help
You didn't address point (a). Really, these strings are meant as a
description for developers, not for users. They don't explain
From: Sven Neumann [EMAIL PROTECTED]
You didn't address point (a). Really, these strings are meant as a
description for developers, not for users. They don't explain what the
plug-in does when being called interactively, they explain what the
particular PDB function does. There are plug-ins that
* Daniel Rogers [EMAIL PROTECTED] [040320 14:10]:
Michael Natterer wrote:
Dave Neary [EMAIL PROTECTED] writes:
We could even consider having a quickish stable release after 2.2 with
just GeglImage replacing GimpLayer, which would give us a chance to
work out any wrinkles in that milestone
Hi,
William Skaggs [EMAIL PROTECTED] writes:
From: Sven Neumann [EMAIL PROTECTED]
You didn't address point (a). Really, these strings are meant as a
description for developers, not for users. They don't explain what the
plug-in does when being called interactively, they explain what the
18 matches
Mail list logo
