Greetings, all.
I was updating part of my web site when I ran across some Script-Fu
scripts. I decided it was time to test some of the scripts to see if the
scripts would work with the 1.3 version of GIMP. The scripts didn't so I
have started to update them. In the process I have a few question
Hi, Sven.
> In the days of GIMP 1.1.x there used to be a
> script which aided in the updating of Script-Fu scripts from the 1.0
> API to the 1.1/1.2 API but I don't see one in the 1.3 CVS copy of GIMP.
This script still needs to be written. The header file gimpcompat.h is
probably the best source
At 06:54 AM 12/17/2003 +0100, Marc Lehmann wrote:
> > Script-Fu scripts? In the days of GIMP 1.1.x there used to be a
> > script which aided in the updating of Script-Fu scripts from the 1.0
> > API to the 1.1/1.2 API but I don't see one in the 1.3 CVS copy of GIMP.
If you talk about scm2scm, it's
At 04:40 PM 12/24/2003 +0100, you wrote:
Here's the list of names on the Friends of GIMP list at the
momenta
What is supposed to be the point of such a list? If you pulled names from a
changelog you are probably making a list of the more active developers of
the GIMP who are probably already on t
At 03:14 PM 12/30/2003 -0800, you wrote:
> It is not as if people dislike the new site; the only thing that
> remains is replacing the old site with it.
One possibility for the short term would be to create a redirect from
www.gimp.org to the new site.
Cheers!
Kevin. (http://www.interlog.com/~k
At 07:57 PM 12/31/2003 -0500, david gowers wrote:
in the realm of 'discussion', does anyone here know why GimpPalette is
implemented using a list? it seems a lot saner to use an array.
Just as a guess, if you mean 'linked list' by 'list', then its probably to
avoid the headaches created by using a
Greetings, all.
I am doing a number of things in the GIMP related to Script-Fu scripts.
One of the things I noticed is that in libgimp/gimpcompat.h it appears
that the 'img' argument has not been dropped for a couple of Script-Fu
scripts that also take a layer argument. For 1.2, many of the functi
Greetings.
I reported something I saw as a bug [bugzilla #132698] and Sven replied
that DB Browser shows enum values used for arguments (ie. GIMP_RGB_IMAGE)
as they would be used from C plug-ins. It would seem I haven't been
following the GIMP development closely enough since I wasn't aware of
At 12:45 PM 01/29/2004, Sven wrote:
What are you advocating instead? Perhaps I just missed something but I
have not been able to figure out what change you are proposing.
The issue you raise has been around forever and it seems that so far
you are the first one to find it disturbing enough to talk
Thank you, Sven and Michael.
Oops, my mistake. It was late and I looked up the deprecated functions to
see they still need 'img'. I thought I had looked up their replacements
before I commented. You are both right of course, that the replacement
functions don't take the extra argument.
I was l
At 04:06 PM 01/29/2004, you wrote:
So the easiest solution would be to make script-fu accept the enums
with or without prefix.
That would be the easiest solution and maintains compatibility with
existing scripts.
The point is that it is already way too late to do any major
incompatible change. Ou
At 12:54 AM 12/17/2003, Marc Lehman wrote:
If you talk about scm2scm, it's part of the gimp-perl distro and
Thank you for the heads up, Marc. I found the old script.
If anybody wants to give it a try, I think modifying it for the 2.0 api
might take about as long as modifying the scripts manually :
At 11:06 PM 01/29/2004, Jeff wrote:
Before you put too much more work into a script converter - take a look
at this one which I just got working this afternoon. I based it on Marc
Lehmann's old scm2scm script, but tweaked it to (a) convert the
deprecated functions and (b) add some additional para
At 09:01 AM 01/30/2004, Marc Lehmann wrote:
Just FYI, perl uses the enums.pl from the gimp core which lists all the
enums. It does, however, do this:
$const =~ s/^GIMP_//;
i.e.., strip the GIMP_-prefix, so the contants are the names with "_"
(easier to type in perl than "-"), but withouth th
On Fri, 2004-01-30 at 13:06, [EMAIL PROTECTED] wrote:
> On Fri, Jan 30, 2004 at 11:57:32AM -0500, Kevin Cozens <[EMAIL PROTECTED]> wrote:
> > > A third set? I was afraid that might be the case.
>
> Well, a set extremely similar and in-sync (at least loosely) to th
Greetings.
While trying to determine if I found a bug in the GIMP (or possibly
undocumented behaviour), I ran across what looks like a bit of redundant
code.
In the file app/pdb/convert_cmds.c around line 153 is an if statement
that checks for a valid range for dither_type. Later (around line 175
Greetings.
The 1.3.2 of the sample plug-in (gimp-plugin-template) uses some
features that are deprecated in the latest CVS version of the GIMP. It
is also missing an argument to one function call. The attached patch
allows the template plugin to compile.
--
Cheers!
Kevin. (http://www.interlog
At 03:28 AM 02/01/2004, you wrote:
On Sat, Jan 31, 2004 at 11:46:35PM -0500, Kevin Cozens wrote:
> Greetings.
>
> The 1.3.2 of the sample plug-in (gimp-plugin-template) uses some
> features that are deprecated in the latest CVS version of the GIMP. It
> is also missing an argument
At 08:24 PM 01/30/2004, you wrote:
> What type of plug-in am I writing again? :-) You get the idea.
Frankly, people forgetting which type of plug-in (in which language) they
are currently writing need professional help *g*.
You are right, the probably would need help. :-) Of course, what I was
ge
At 08:48 AM 02/02/2004, Sven wrote:
Given the state of the guash code and that it never got the reputation
of being stable, I'd advocate to write a new plug-in instead of
attempting to port this code. I've been playing with a thumbnail
browser plug-in to make some more use of libgimpthumb.
The GUAS
At 08:24 PM 01/30/2004, Marc Lehmann wrote:
Constant names are a much smaller difference than calling conventions
between languages. It is, in general, impossible to use an API for one
language in another without adapting it to the target language.
[snip]
I'd also find it cool if you looked into th
At 12:58 PM 02/02/2004, Marc Lehmann wrote:
Constant names for one thing, I thought?
Do you have any specific examples in mind I can look at to see what it
shows. An idea of what you think it should show would also be useful.
During normal development, examples are a hundred times better than lot
Greetings.
For those of you working with Script-Fu scripts for the GIMP, I have
made a minor change to the Perl script I wrote to update scripts from
the 1.2 to the 2.0 API.
The latest change allows named constants to be recognized (and updated
as needed) regardless of whether they use _ or -. Th
Greetings.
I have a patch which removes all of the deprecated named constants from
the Script-Fu based scripts which are part of a standard GIMP
installation.
I haven't attached the patch to this message since it is a bit over
50,000 bytes. The patch file is available with the following URL:
http
On Mon, 2004-02-02 at 18:42, Henrik Brix Andersen wrote:
> Please do that - bugzilla helps us track bugs along with patches and
> enhancement requests much better than a mailing list does.
Done. The patch affects 48 different scripts. It will allow for the
eventual removal of some code in siod-wra
Greetings.
In the file plug-ins/script-fu/script-fu-scripts.c is a typedef for
SFScript. The third member is 'description'. The contents of the
structure is filled in by the routine script_fu_add_script() further
down the file. This routine is processing the arguments of the
script-fu-register cal
On Tue, 2004-02-03 at 04:48, Sven Neumann wrote:
> Well, it is not only used as a menu-path but also as a (short)
> description. Basically, Script-Fu is a mess. Wouldn't you want to
> rewrite it? We keep looking for someone who wants to redo Script-Fu
> for quite a while already.
Looking at that
On Tue, 2004-02-03 at 04:49, Sven Neumann wrote:
> > Done. The patch affects 48 different scripts. It will allow for the
> > eventual removal of some code in siod-wrapper.c (for the 2.2 release?).
>
> I don't think we want to break backward compatibility so this code
> will have to stay.
The code
On Tue, 2004-02-03 at 18:18, Daniel Rogers wrote:
> Sven Neumann wrote:
> > All of this would probably be best solved by redoing Script-Fu using a
> > full-featured and actively maintained Scheme implementation.
>
> Might I suggest Guile?
> http://www.gnu.org/software/guile/guile.html
>
> It seem
On Thu, 2004-02-05 at 17:12, David Neary wrote:
> 9) A decent image browser/thumbnail viewer + cover-sheet support
This sounds a bit like the old GUASH (which I have started to port
to GTK+ 2.x/GIMP 2.0) but I'm not sure what you mean by "cover-sheet
support".
___
At 06:18 AM 02/06/2004, Sven wrote:
> 7) Move from SIOD to guile for script-fu
Guile or another interpreter or fix the current implementation. All
nice but we keep asking for this for years now and I don't see it
happen until summer. Let's say, it would be nice to have but it
shouldn't block 2.2.
At 02:13 PM 02/05/2004, Carol Spears wrote:
okay, i dont really like script-fu. i cant read it and it has this way
of not telling gimp when it has made an image.
I am starting to notice a lot of people saying they don't like Script-Fu.
As for not being able to read it, that is not helped by the f
At 07:06 AM 02/06/2004, Sven wrote:
What Mitch did there was to prepare the SIOD implementation for an
update to the latest released version which is at least two years
newer that what we are using now.
The most recent copy of SIOD I could find was from 1998, IIRC. So, if the
current SIOD part of
On Fri, 2004-02-06 at 19:34, Daniel Egger wrote:
> On Feb 7, 2004, at 1:14 am, Tim Mooney wrote:
> > As I recall, the SIOD that's part of gimp is not a "stock" version of
> > SIOD, as there were various bugs detected and fixed in SIOD in the
> > 0.99.x
> > and 1.2.x gimp releases. There *may* be
Greetings.
This is too trivial to bugzilla so I'll just mention it here.
The word 'spacified' appears in the following list of files:
app/pdb/image_cmds.c
devel-docs/libgimp/xml/gimpimage.xml
devel-docs/libgimp/html/libgimp-gimpimage.html
libgimp/gimpimage_pdb.c
On Mon, 2004-03-22 at 13:42, Tor Lillqvist wrote:
> Is there any way to get a verbose trace from the script-fu
> interpreter, or from the PDB mechanism?
The Scheme interpreter in SIOD normally runs with its verbosity level
set to 2. To change it, use '(verbose n)', where n is the verbosity
level y
On Sun, 2004-04-04 at 20:44:44, Gezim wrote:
> I was really excited to find this layer-effect
> script-fu. I found out though that it only works for
> gimp 1.2* and not 2.
It was very simple to fix. I used the Perl script I created which
updates Script-Fu scripts from GIMP 1.2 to GIMP 2.0. The upd
On Mon, 2004-05-10 at 18:53, Stephan Menzel wrote:
> Well, it does here.
> I can reproduce it every time.
> 0. Load Gimp and load any picture (tried with RGB and Greyscale)
> 1. press O
> 2. pick a color from the picture
> 3. close the little color chooser window
> 4. press T or click the Text butt
Greetings, everyone.
For some months now I have been working on a new plug-in for the 2.1
version of GIMP. I have been calling this new plug-in Tiny-Fu. Some of the
people on this list who use the #gimp IRC channel have already heard about
this plug-in.
Tiny-Fu is a plug-in for the 2.1 (and lat
At 01:18 PM 07/06/2004, Sven Neumann wrote:
We talked about script-fu and tiny-fu at GIMPCon and agreed that we'd
like to see Script-Fu removed from the GIMP source tree as soon as
Tiny-Fu is available as a separate package that can replace it.
The Tiny-Fu tarball can exist in the GIMP source tree
At 02:18 PM 07/06/2004, Markus wrote:
TinyScheme does not support arrays at the moment - do you plan to implement
this feature (i.e., fork TinyScheme), or is such a feature planned by the
TinyScheme developers?
No, I do NOT want to fork TinyScheme. I am trying to keep patches to
TinyScheme which w
At 03:27 PM 07/06/2004, Joao wrote:
One of the major showstopers for script-fu as of lately is it inability to
handle UTF-8 strings. Is tiny scheme able to do so?
No, TinyScheme does not handle UTF-8 strings. UTF-8 support is already on
the ToDo list since Sven already raised the issue on #gimp.
On Tue, 2004-07-06 at 19:45, Sven Neumann wrote:
> The fact that the PDB uses arrays doesn't necessarily mean that a
> language binding such as Tiny-Fu needs to represent them as arrays.
> One of the most annoying bits of Script-Fu is that it forces you to
> work with arrays even though the natural
At 05:17 AM 07/07/2004, Shlomi Fish wrote:
Are you sure using lists instead of vectors is the right thing to do? Lists
are linked lists and as such accessing the i'th element is O(i). In vectors
it is O(1). This can cause an order of complexity increase in handling them.
No, I'm not sure. For the f
At 08:09 PM 07/07/2004, Markus Triska wrote:
I also opt for vector because apart from being the natural Scheme equivalent
to PDB's one-dimensional arrays, it makes writing plug-ins easier for people
that have no to little practice in converting common "for/while" loops using
tail-recursion, and cur
At 01:38 PM 07/09/2004, you wrote:
Now since there is essentially a one-to-one correspondence between Tiny-Fu's
vectors and Script-Fu's "arrays", it might be worth considering adding
compatibility definitions to "init.scm" (similar to gimpcompat.h for
plug-ins), that would, depending on a certain "
At 06:00 AM 07/10/2004, Sven wrote:
Kevin Cozens <[EMAIL PROTECTED]> writes:
> I don't really want a "compatibility"-switch. Instead, old Script-Fu
> scripts should be updated so they do things the way they are supposed
> to be done in Scheme rather than how the old
On Sat, 2004-07-10 at 19:19, Markus Triska wrote:
> I have explained this above - re-define "set!" to use the TinyScheme
> "defined?" command to see if a variable is already defined, and if this is
> not the case, define it.
Now I understand what you were getting at earlier. That would work only
Greetings, everyone.
Announcing the second public release of a tarball for the Tiny-Fu plug-in
for the 2.1 version of GIMP. The tarball must currently be hooked in to a
copy of the GIMP 2.1.x source tree by using the supplied gimp.patch patch
file. As of last night (Wednesday, July 14) the new
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
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
[snip]
I'm giving this another shot (after bug #145370, taking your feedback into
account - TinyScheme currently lacks a similar feature), because it s
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 *ni
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 FIL
Greetings, Markus.
At 05:05 PM 07/22/2004, you wrote:
I was not aware of all the useful
extensions you are incorporating into Tiny-Fu.
There are only two extensions for the TinyScheme interpreter I'm using them
both since they each add something useful for scripts. I have used the
extensions to c
The fourth public release of a tarball for the Tiny-Fu plug-in for GIMP
2.1.x is now available. This release contains a number of important bug
fixes and changes. If you are using a previous version, I strongly
recommend you update to this latest release.
With this release, the status of Tiny-Fu h
Greetings, all.
A tarball of version 0.9.0 of Tiny-Fu is now available at:
http://www.interlog.com/~kcozens/software/gimp/tiny-fu.html
This is the first tarball which has been released with a version number rather than a
release date marking another milestone in the evolution of Tiny-Fu.
As of thi
Greetings, all.
A tarball of version 0.9.1 of Tiny-Fu is now available at:
http://www.interlog.com/~kcozens/software/gimp/tiny-fu.html
This is primarily a maintenance release. It fixes a problem with the
definition of some constants used by the ftx extension, and includes an
improved contact sheet
Greetings, all.
In a previous message written by Sven about preparing for GIMP 2.2, he
wrote the following:
Script-Fu vs. Tiny-Fu
We should come to a conclusion whether and how Tiny-Fu can replace
Script-Fu. I'd suggest we make separate packages gimp-script-fu and
gimp-tiny-fu and remove Scrip
Joao S. O. Bueno Calligaris wrote:
Ok, just to drop my 2 cents in here:
I think that changing the units on the new image dialog should not
convert the numbers typed in, unless if explicitly desired.
Just another thought. What about adding some sort of "lock" icon beside
the X&Y values that, wh
Greetings, all.
A tarball of version 0.9.2 of Tiny-Fu is now available at:
http://www.interlog.com/~kcozens/software/gimp/tiny-fu.html
This is the second maintenance release of Tiny-Fu. The most important
change is a fix related to the handling of PDB *ARRAY data types. It
also allows more data c
Greetings, one and all.
Now that I have released a new tarball of Tiny-Fu I am letting you know
I will be going back over a few of the message threads related. I just
wanted to let you know I wasn't ignoring the messages. If you have
questions about Tiny-Fu, you may want to hold off for a couple
Greetings, all.
For those of you who would like to stay on the leading edge of the
development of the Script-Fu replacement known as Tiny-Fu you may now do
so using GNOME CVS. To retrieve the latest development version of
Tiny-Fu from CVS you can use the following commands to get it from the
an
Greetings, all.
A tarball of version 0.9.4 of Tiny-Fu is now available at:
http://www.interlog.com/~kcozens/software/gimp/tiny-fu.html
This is the first standalone release of Tiny-Fu. In other words, you no
longer need to have the full GIMP source tree available in order to build
Tiny-Fu. My thanks
Andreas Røsdal wrote:
is there any documentation for developers about Tiny-Fu? Will Tiny-Fu be
in Gimp 2.2?
There is no formal documentation for Tiny-Fu at the present time. The
current "documentation" consists of the comments I have on the Tiny-Fu
web page, the R5RS (the Scheme standards docu
Campbell Barton wrote:
just wondering how Tiny-fu is differentr to Script-fu?
There is little if any difference between the two to a person who is
only using Tiny-Fu to run Scheme based scripts. The most visible
difference between the two is the two extra buttons ("Clear Output" and
"Save Output
Campbell Barton wrote:
I tried and couldent get a Scheme script running in python- (Could
have been a silly mistake but I tried for ages)
If you were trying to get a Scheme script running in Python, that was a
mistake. A Scheme script is run using either the Script-Fu or Tiny-Fu
plug-in. Scheme
Greetings, all.
A tarball of version 0.9.3 of Tiny-Fu is now available at:
http://www.interlog.com/~kcozens/software/gimp/tiny-fu.html
This is the third maintenance release of Tiny-Fu. Most of the changes in
this release were to keep Tiny-Fu in sync with changes and cleanups in
Script-Fu, in the
Greetings, all.
One of my side projects while working on Tiny-Fu has been creating and
running a script which calls all PDB routines with bad data to see how
the various routines handle the bad data. My test script passes -1 for
the image, drawable, layer, channel, and all INT arguments. I also
miriam clinton (iriXx) wrote:
i'm familiar with sodipodi - its close, but no banana... needs a lot
of work, but i'd like to help there too...
havent seen inkscape yet - is it new?
IIRC, inkscape started life as an off-shoot of sodipodi but it is now a
separate project. The answer to the first que
Greetings, all.
A tarball of version 0.9.5 of Tiny-Fu is now available at:
http://www.interlog.com/~kcozens/software/gimp/tiny-fu.html
The code changes were fixes for a few minor bugs, and to keep in up-to-date
with changes in GIMP and the Script-Fu plug-in. Most of the change made
since the 0.9
Sven Neumann wrote:
Yes, the plan's to move the scripts out of the script-fu menu into the
places they belong to. What's missing here though is a better menu
registration functionality in Script-Fu. Kevin wanted to add a bug
report about this.
Actually, I was originally expecting Sven to add the bu
Joao S. O. Bueno Calligaris wrote:
Script fu is acting strange in the last days - I'd say it started with
this change:
2004-11-22 Michael Natterer <[EMAIL PROTECTED]>
* plug-ins/script-fu/script-fu-scripts.c: sort the SFMenu
There is definitely a change in behaviour between 2.0.5 and
GSR - FR wrote:
Of course, in past years the algoritms have evolved, see for example
the concept of freehand sketch selection:
http://vision.ai.uiuc.edu/~tankh/Selection/selection.html
This is the second time I have seen something which really only exist as
a research paper but would be really
Greetings, all.
A tarball of version 0.9.6 of Tiny-Fu is now available at:
http://www.interlog.com/~kcozens/software/gimp/tiny-fu.html
The biggest change affected all script files which now use a separate
tiny-fu-menu-register call to place an entry in the menu hierarchy. This
means scripts can n
Tomasz Grobelny wrote:
Where can I find a decent script-fu documentation? I mean a document where I
can find most supported functions especially string manipulation functions
(like split, chop, substring, find etc.). TIA
The Script-Fu plug-in of GIMP uses SIOD as its Scheme interpreter. The
m
Campbell Barton wrote:
Will thge gimp move to tiny-fu compleately?
I am not aware of any plans to replace Script-Fu with Tiny-Fu in the
GIMP source tree. Although that might change now that I am about to
start testing the Tiny-Fu changes which added UTF-8 support. If
Script-Fu was pulled out as
[EMAIL PROTECTED] wrote:
I would hope that if ScriptFu is pulled out,
TinyFu will also provide an interpreter
directly in GIMP's GUI that one can use
interactively. (I haven't used TinyFu)...
Tiny-Fu was built using the framework of Script-Fu. It has all the main
features of Script-Fu (except
Campbell Barton wrote:
Script X dosent work with Tiny fu but and VsVercer for other scripts
,.. you know, it just gets messy.
Its best top keep to one, newbies will ask which to use and get
confusticated answeres by opinionated experts.
Forgetting about Tiny-Fu for a moment there are still pr
Nathan Summers <[EMAIL PROTECTED]> writes:
This still doesn't meet the definition of "spreading FUD." To spread
FUD you must:
1) Either lie or deliberately misrepresent the truth (this includes
selective retelling of the facts)
2) In one or more fora such that a large number of poorly-informed
peo
Sven Neumann wrote:
Daniel Egger <[EMAIL PROTECTED]> writes:
Hm, there's still no idea floating around how to benchmark.
There are very clear ideas on how to do it. Someone just needs to sit
down and write the script (or dig out script-fu-bench.scm which is
what we used to use a long time a
Kent Loobey wrote:
I would like to know how to insert a string into a cons-array using Script-Fu.
Specifically how do I get the following to work?
(let (
(foo (cons-array 1 'string))
)
(aset foo 0 "my string"))
)
Clearly "aset" is not the function to use...
I am not trying to get you
Greetings, all.
A tarball of version 0.9.7 of Tiny-Fu is now available at:
http://www.interlog.com/~kcozens/software/gimp/tiny-fu.html
It has been almost two and a half months since the last release of Tiny-Fu.
In that time a number of changes and a few important bug fixes have
accumulated. Apart
Greetings, all.
A tarball of version 0.9.8 of Tiny-Fu is now available at:
http://www.interlog.com/~kcozens/software/gimp/tiny-fu.html
It was barely a week between the release of the 0.9.7 and 0.9.8 versions.
The main work for this new release was started before 0.9.7 was made
available. The 0.9.
Joao S. O. Bueno Calligaris wrote:
It seems this fucntionality exists in other programs but not in the
GIMP - i.e.: the ability to apply a palette to an already indexed
image, keeping the color numbers.
This is easily doable in script, but it could also be done in the core
One of the scri
Andrei Simion wrote:
I managed to start X:
Xvfb :1.0 -screen 0 10x10x16
So, the display is 1.
Now, I start the Gimp server:
gimp --display 1 --no-interface --batch \('extension-perl-server 0 0 0'\)
If the above is all you have done, you have not done what Sven told you
to do. After startin
Joao S. O. Bueno Calligaris wrote:
Anyway - the person needing this right now is on win32 - Will this
script work in script-fu?
It should work but you will need to change the filename to end in .scm
and change all occurances of 'tiny-fu' in the script to 'script-fu'
(preserving case). You
Alan Horkan wrote:
It should call 'gimp_image_set_colormap' instead!
Normally I'd be in favour of expanding abbreviations to make things
clearer but in this case the shorter deprecated name avoids the confusion
caused by the American mispelling of Colour (damned Webster and his
patriotic
Alan Horkan wrote:
I really like the idea of providing information about menu items but not
the proposed implementation. The way many other Gnome and GTK give the
information applications do is to show a description of a menu item in the
status bar. Perhaps the existing short description/summ
Dave Neary wrote:
The two suggestions which seemed to get the most traction were a
plug-in distribution system and a vector-based shapes tool. Simon
agreed to mentor someone on the shapes tool, we need a mentor for the
plug-in system. There is a related resource distribution project for
gDesk
Alan Horkan wrote:
Great topic. Personally I'd love to see the Script-Fu and Python
entries go away, for the same reason as in the Filters menu:
the user shouldn't have to know.
I don't have a problem with that either. But as someone pointed out, we
need a place to put the menu entries that a
Sven Neumann wrote:
> The idea of the menu reorganization is to hide the language from the
user because the user shouldn't have to care what language a filter is
written in. Adding a language specific icon is contradicting this
effort. There will always be the plug-in browser if someone wants to
pepster wrote:
Say I have a scrip-fu plugin (I am thinking about wrap sharp), and I
want to add a preview window to make it more useful.
Does it mean I must re-write the plugin in C, or is there an easier way?
You would have to re-write it in C. There is no easy way to add a preview
window t
On Monday 01 August 2005 13:01, Akkana Peck wrote:
Joao S. O. Bueno Calligaris writes:
I am not so sure about Image->Modes , unless tehre is a ubmenu
Colors->Image to indicate taht thos ewill operate ont eh whole
image instead of a drawable. But then, they could just stay were
they are.
How
Greetings, all.
After almost a year and a half of development, Tiny-Fu has reached a major
milestone with the release of the 1.0.0 version. Although it is now at version
1.0, there are a few minor issues remaining. Mainly, the translation files are
not all up-to-date yet and there is one (or poss
[EMAIL PROTECTED] wrote:
I've got a suggestion about the GUI/Layout. You can se the idea at
http://www.linet.se/gimp/
Looks rather like a request along the lines of bug #7379.
--
Cheers!
Kevin.
http://www.interlog.com/~kcozens/ |"What are we going to do today, Borg?"
Owner of Elecraft K2 #21
Michael Schumacher wrote:
Building GIMP isn't hard. Getting the build environment working is the
harder part, and something you'll have to do for plug-in building as well.
There's a section in the wiki covering this
http://wiki.gimp.org/gimp/HowToCompileGimp/MicrosoftWindows
In can be very dif
Scott wrote:
Sorry, I seem to have unwittingly stepped into some hornet's nest.
Yes, you certainly did. :-) Some bright GTK+ developer decided to make some
changes to the dialog box sometime ago leading to the current situation. To
avoid rehashing this issue here you should look at the outsta
Sven Neumann wrote:
It is somewhat futile to point out that support for the PSD format
needs to be improved. We know that. We know that for several years
now. We simply need someone who invests the time to improve it.
The trick is to find someone willing to work on this AND who has a copy of
P
[EMAIL PROTECTED] wrote:
Output from Script-fu can be sent to "stdout" by first performing a:
(gimp-message-set-handler 1)
The Procedure Browser shows that the arguments '1' has an equivalent (C style)
name of GIMP_CONSOLE. In Script-Fu you remove the leading GIMP_ from named
constants sho
Michael Schumacher wrote:
Michael Schumacher said:
[snip]
They must be able to build current CVS.
[snip]
They can do it in days only if their platform of choice has the required
prerequisites. For example, you're out of luck with Debain stable or
another older release of a distro.
If you ha
1 - 100 of 261 matches
Mail list logo
