RSS News FeedGimp Plug ins
Message-ID:<fGojl.16325$yr3.3831@nlpi068.nbdc.sbc.com>
Subject:
Gimp Plug-ins
Date:Sun, 8 Feb 2009 00:19:39 +0100
Can someone describe in DETAIL the steps necessary to install plug-ins in Gimp and then how to find them in the menu and use them. I found the website where you can see plug-ins so where do we go from there?
Message-ID:<1a01b4a6-02a2-4c60-8e35-72106765f174@z6g2000pre.googlegroups.com>
Subject:
Re: Gimp Plug-ins
Date:Sun, 8 Feb 2009 06:51:20 +0100
On Feb 8, 10:19 am, measekite <inkysti...@oem.com> wrote: > Can someone describe in DETAIL the steps necessary to install plug-ins in > Gimp and then how to find them in the menu and use them. > > I found the website where you can see plug-ins so where do we go from > there? Say the plug in has a 'scm' extension Place the script into your .gimp/scripts directory (note the dot . before the gimp) To find where it will appear, open in a text editor and look for something like (script-fu-register "script-fu-image-subdivide" _"<Image>/_ATG/_Tools/_Image subdivide" "Subdivide the image in MxN Rows and Columns and save any rectangular portion in the new files." That third line tells you where to find it Owen
Message-ID:<GVvjl.17196$c45.7943@nlpi065.nbdc.sbc.com>
Subject:
Re: Gimp Plug-ins
Date:Sun, 8 Feb 2009 08:33:58 +0100
On Sat, 07 Feb 2009 21:51:20 -0800, Owen wrote: > On Feb 8, 10:19 am, measekite <inkysti...@oem.com> wrote: >> Can someone describe in DETAIL the steps necessary to install plug-ins in >> Gimp and then how to find them in the menu and use them. >> >> I found the website where you can see plug-ins so where do we go from >> there? > > Say the plug in has a 'scm' extension > > Place the script into your .gimp/scripts directory (note the dot . > before the gimp) > > To find where it will appear, open in a text editor and look for > something like > > (script-fu-register > "script-fu-image-subdivide" > _"<Image>/_ATG/_Tools/_Image subdivide" > "Subdivide the image in MxN Rows and Columns and save any rectangular > portion in the new files." > > That third line tells you where to find it > > > > Owen Thanks but I am not familiar enough with Gimp and plugins to fully understand what you are saying. I did download a scm file.
Message-ID:<h%vjl.17197$c45.12777@nlpi065.nbdc.sbc.com>
Subject:
Re: Gimp Plug-ins
Date:Sun, 8 Feb 2009 08:39:57 +0100
On Sat, 07 Feb 2009 21:51:20 -0800, Owen wrote: > On Feb 8, 10:19 am, measekite <inkysti...@oem.com> wrote: >> Can someone describe in DETAIL the steps necessary to install plug-ins in >> Gimp and then how to find them in the menu and use them. >> >> I found the website where you can see plug-ins so where do we go from >> there? > > Say the plug in has a 'scm' extension > > Place the script into your .gimp/scripts directory (note the dot . > before the gimp) > > To find where it will appear, open in a text editor and look for > something like > > (script-fu-register > "script-fu-image-subdivide" > _"<Image>/_ATG/_Tools/_Image subdivide" > "Subdivide the image in MxN Rows and Columns and save any rectangular > portion in the new files." > > That third line tells you where to find it > > > > Owen I found a .gimp hidden folder in my home folder. Under that there were two folders. One was called plugins and the other scripts. Both were empty. I also have a gimp folder under /usr/share Under there I found a scripts folder with bunch of scm files. Do I copy the scm files there or what?
Message-ID:<5a9e1bd5-aac9-40ab-834a-d1f954072271@j8g2000yql.googlegroups.com>
Subject:
Re: Gimp Plug-ins
Date:Sun, 8 Feb 2009 09:16:50 +0100
On Feb 8, 2:39=A0am, measekite <inkysti...@oem.com> wrote:
> On Sat, 07 Feb 2009 21:51:20 -0800, Owen wrote:
> > On Feb 8, 10:19 am, measekite <inkysti...@oem.com> wrote:
> >> Can someone describe in DETAIL the steps necessary to install plug-ins=
in
> >> Gimp and then how to find them in the menu and use them.
>
> >> I found the website where you can see plug-ins so where do we go from
> >> there?
>
> > Say the plug in has a 'scm' extension
>
> > Place the script into your .gimp/scripts directory (note the dot =A0.
> > before the gimp)
>
> > To find where it will appear, open in a text editor and look for
> > something like
>
> > (script-fu-register
> > =A0"script-fu-image-subdivide"
> > =A0_"<Image>/_ATG/_Tools/_Image subdivide"
> > =A0"Subdivide the image in MxN Rows and Columns and save any rectangula=
r
> > portion in the new files."
>
> > That third line tells you where to find it
>
> > Owen
>
> I found a .gimp hidden folder in my home folder. =A0Under that there were
> two folders. =A0One was called plugins and the other scripts. =A0Both wer=
e
> empty.
>
> I also have a gimp folder under /usr/share
>
> Under there I found a scripts folder with bunch of scm files. =A0Do I cop=
y
> the scm files there or what?
Hi, I've been placing my .scm files into the "scripts" folder which I
have here in my folder hierarchy:
gimp-2,0/
share/
gimp/
2.0/
scripts
This should work for you.
Message-ID:<fHDjl.13274$as4.5949@nlpi069.nbdc.sbc.com>
Subject:
Re: Gimp Plug-ins
Date:Sun, 8 Feb 2009 17:24:43 +0100
On Sun, 08 Feb 2009 00:16:50 -0800, veyoung52 wrote: > On Feb 8, 2:39 am, measekite <inkysti...@oem.com> wrote: >> On Sat, 07 Feb 2009 21:51:20 -0800, Owen wrote: >> > On Feb 8, 10:19 am, measekite <inkysti...@oem.com> wrote: >> >> Can someone describe in DETAIL the steps necessary to install plug-ins in >> >> Gimp and then how to find them in the menu and use them. >> >> >> I found the website where you can see plug-ins so where do we go from >> >> there? >> >> > Say the plug in has a 'scm' extension >> >> > Place the script into your .gimp/scripts directory (note the dot . >> > before the gimp) >> >> > To find where it will appear, open in a text editor and look for >> > something like >> >> > (script-fu-register >> > "script-fu-image-subdivide" >> > _"<Image>/_ATG/_Tools/_Image subdivide" >> > "Subdivide the image in MxN Rows and Columns and save any rectangular >> > portion in the new files." >> >> > That third line tells you where to find it >> >> > Owen >> >> I found a .gimp hidden folder in my home folder. Under that there were >> two folders. One was called plugins and the other scripts. Both were >> empty. >> >> I also have a gimp folder under /usr/share >> >> Under there I found a scripts folder with bunch of scm files. Do I copy >> the scm files there or what? > > Hi, I've been placing my .scm files into the "scripts" folder which I > have here in my folder hierarchy: > gimp-2,0/ > share/ > gimp/ > 2.0/ > scripts > This should work for you. Thanks
Message-ID:<vHLjl.15723$YU2.14300@nlpi066.nbdc.sbc.com>
Subject:
Re: Gimp Plug-ins
Date:Mon, 9 Feb 2009 02:31:07 +0100
On Sun, 08 Feb 2009 00:16:50 -0800, veyoung52 wrote: > On Feb 8, 2:39 am, measekite <inkysti...@oem.com> wrote: >> On Sat, 07 Feb 2009 21:51:20 -0800, Owen wrote: >> > On Feb 8, 10:19 am, measekite <inkysti...@oem.com> wrote: >> >> Can someone describe in DETAIL the steps necessary to install plug-ins in >> >> Gimp and then how to find them in the menu and use them. >> >> >> I found the website where you can see plug-ins so where do we go from >> >> there? >> >> > Say the plug in has a 'scm' extension >> >> > Place the script into your .gimp/scripts directory (note the dot . >> > before the gimp) >> >> > To find where it will appear, open in a text editor and look for >> > something like >> >> > (script-fu-register >> > "script-fu-image-subdivide" >> > _"<Image>/_ATG/_Tools/_Image subdivide" >> > "Subdivide the image in MxN Rows and Columns and save any rectangular >> > portion in the new files." >> >> > That third line tells you where to find it >> >> > Owen >> >> I found a .gimp hidden folder in my home folder. Under that there were >> two folders. One was called plugins and the other scripts. Both were >> empty. >> >> I also have a gimp folder under /usr/share >> >> Under there I found a scripts folder with bunch of scm files. Do I copy >> the scm files there or what? > > Hi, I've been placing my .scm files into the "scripts" folder which I > have here in my folder hierarchy: > gimp-2,0/ > share/ > gimp/ > 2.0/ > scripts > This should work for you. Finally downloaded a bunch of .scm files and placed them in the .Gimp2/scripts folder. I did find most of them in various places in the menu system and am learning how to use them notwithstanding spartan documentation. I also downloaded a .py file and placed it also in the scripts folder but it does not appear in the Gimp menu. Where do you place the python .py files? One of the major problems with Gimp is it does not force the plug-in writer to place all of their files in one plug-in folder wither in the users home folder to restrict it to one user or in the usr/share/??? folder for all users to use.
Message-ID:<dxSjl.20323$aJ3.680@newsfe23.ams2>
Subject:
Re: Gimp Plug-ins
Date:Mon, 9 Feb 2009 10:18:01 +0100
On Mon, 09 Feb 2009 01:31:07 +0000, measekite wrote: > On Sun, 08 Feb 2009 00:16:50 -0800, veyoung52 wrote: > >> On Feb 8, 2:39 am, measekite <inkysti...@oem.com> wrote: >>> On Sat, 07 Feb 2009 21:51:20 -0800, Owen wrote: >>> > On Feb 8, 10:19 am, measekite <inkysti...@oem.com> wrote: >>> >> Can someone describe in DETAIL the steps necessary to install >>> >> plug-ins in Gimp and then how to find them in the menu and use >>> >> them. >>> >>> >> I found the website where you can see plug-ins so where do we go >>> >> from there? >>> >>> > Say the plug in has a 'scm' extension >>> <snip> > > Finally downloaded a bunch of .scm files and placed them in the > .Gimp2/scripts folder. I did find most of them in various places in the > menu system and am learning how to use them notwithstanding spartan > documentation. > > I also downloaded a .py file and placed it also in the scripts folder > but it does not appear in the Gimp menu. > > Where do you place the python .py files? > <snip> You don't say which Gimp version you are using, so depending on 2.4 or 2.6 some menu items might be in different places and some scripts / plugins might or might not work. Pleased that you have the scripts working but you should really use your home folder, if only for ease of copying. Did you check in "preferences" -> "folders" to see if the home folder was included. You can have the scripts anywhere providing you tell gimp where they are. The same applies to .py - check the folder locations. The .py files are python scripts so you need the python libraries installed. These should already be there but check. The .py files should go in the plugin folder and each script should be made executable. Depending on the script they can appear in different places, I have a couple which make their own menu "Python-fu" and another which appears in the image menu, so no hard and fast rule. I'm still on gimp 2.4.4 so take that into account. -- rich
Message-ID:<250d8e4f-6aac-4f2b-9789-5de532483a63@l16g2000yqo.googlegroups.com>
Subject:
Re: Gimp Plug-ins
Date:Mon, 9 Feb 2009 14:13:13 +0100
On 9 Feb., 02:31, measekite <inkysti...@oem.com> wrote: > One of the major problems with Gimp is it does not force the plug-in > writer to place all of their files in one plug-in folder wither in the > users home folder to restrict it to one user or in the usr/share/??? > folder for all users to use. You can have as many plug-in folders as you wish - that's configurable in GIMP's preferences. If you are referring to the fact that scripts are kept separate from plug-ins - well, maybe this could be because they are different? HTH, Michael
Message-ID:<CV_jl.4236$%54.2689@nlpi070.nbdc.sbc.com>
Subject:
Re: Gimp Plug-ins
Date:Mon, 9 Feb 2009 19:50:10 +0100
On Mon, 09 Feb 2009 05:13:13 -0800, Michael Schumacher wrote: > On 9 Feb., 02:31, measekite <inkysti...@oem.com> wrote: > >> One of the major problems with Gimp is it does not force the plug-in >> writer to place all of their files in one plug-in folder wither in the >> users home folder to restrict it to one user or in the usr/share/??? >> folder for all users to use. > > You can have as many plug-in folders as you wish - that's configurable > in GIMP's preferences. > > If you are referring to the fact that scripts are kept separate from > plug-ins - well, maybe this could be because they are different? > > > HTH, > Michael Then what is the difference between a script and a plug-in?
Message-ID:<MPG.23faaf22e8b5c32698974c@127.0.0.1>
Subject:
Re: Gimp Plug-ins
Date:Mon, 9 Feb 2009 21:23:18 +0100
In article <CV_jl.4236$%54.2689@nlpi070.nbdc.sbc.com>, inkystinky@oem.com says... > > Then what is the difference between a script and a plug-in? plugin is a piece of program code, doing some action, which is called by gimp. script is interpreted text ( similar as bat, cmd, vbs or js ), that tells gimp what todo ( either by internal features, either by external plugins ) There are dedicated folders for both, either in machine and user scope. -- Poutnik
Message-ID:<20090210091347@usenet.piggo.com>
Subject:
Re: Gimp Plug-ins
Date:Tue, 10 Feb 2009 00:16:26 +0100
* measekite wrote : > On Mon, 09 Feb 2009 05:13:13 -0800, Michael Schumacher wrote: > >> On 9 Feb., 02:31, measekite <inkysti...@oem.com> wrote: >> >>> One of the major problems with Gimp is it does not force the plug-in >>> writer to place all of their files in one plug-in folder wither in the >>> users home folder to restrict it to one user or in the usr/share/??? >>> folder for all users to use. >> >> You can have as many plug-in folders as you wish - that's configurable >> in GIMP's preferences. >> >> If you are referring to the fact that scripts are kept separate from >> plug-ins - well, maybe this could be because they are different? > > Then what is the difference between a script and a plug-in? Scripts have the .scm file extension and are basically a text file with GIMP commands scripted in them. Plugins are typically binary executable files that can do things not native to GIMP. eg run UFRAW That's my layman's was of thinking of it. :) -- Troy Piggins
Message-ID:<22f7db5c-765d-4158-9f1c-e4ea0e8b89f2@j1g2000yqi.googlegroups.com>
Subject:
Re: Gimp Plug-ins
Date:Tue, 10 Feb 2009 10:53:23 +0100
On 10 Feb., 00:16, Troy Piggins <usenet-0...@piggo.com> wrote: > Plugins are typically binary executable files that can do things > not native to GIMP. =A0eg run UFRAW Python, Perl? Yes, these are plug-ins :) Although at least the former do get compiled on load. They are executables, though. And do not work if their executable bit is not set, at least on platforms that do require this for executables. Michael
Message-ID:<3f91ada0-731e-4681-8bec-3fa69922ac36@g38g2000yqd.googlegroups.com>
Subject:
Re: Gimp Plug-ins
Date:Tue, 10 Feb 2009 12:09:45 +0100
On 9 Feb., 19:50, measekite <inkysti...@oem.com> wrote:
> Then what is the difference between a script and a plug-in?
There are four main differences:
1. Programing language
----------------------------
- Scripts are written in Scheme.
- Plug-ins are written in C, C++, Python, Perl, C# or any other
language that can
a) make use of the libgimp* header files and/or libraries and
b) create executables that can be run by GIMP, sometimes by using
the language's own interpreter
This is a weak distinction, of course - nobody would prevent you from
creating modules for a Scheme interpreter (a more sophisticated one
than TinyScheme, most probably) and create plug-ins in Scheme.
2. Execution workflow
----------------------------
- Scripts are run by the Script-Fu extension of GIMP (think of it as a
plug-in, although it stays around the whole time an instance of GIMP
is running). All scripts are read completely when GIMP starts or when
you do manually refresh them. This is why Script-Fu does use a
considerable amount of GIMP's start-up time.
The procedures that are implemented by the scripts do stay in memory
all this time.
If you call a script-fu-* procedure, the procedure is executed by the
Script-Fu extension.
- Plug-ins are called ("queried") once when GIMP starts for the first
time, and then only if the plug-in executable has changed (this is
determined by the file's timestamp). A cache file (pluginrc) is
written in your GIMP profile directory, containing the signatures of
the procedures (a description containing its name and its parameters).
If you call one of these procedures, then the plug-in is executed.
You can change a plug-in while GIMP is running, and the new code will
be used (you may have to compile it, of course; for Python plug-in
that's again done automatically).
3. Accessible API
----------------------------
- Scripts have limited access to the GIMP (only via the PDB) and GTK+
API ("none") (and other libraries, for that matter). You won't be
working with image tiles in GIMP scripts, for example - a performance
issue. You won't be creating your own user interface - Script-fu does
provide a set of elements for data entry, and that it. You won't be
using an arbitrary C library in your script, e.g. to do FFT or face
recognition.
- Plug-ins do have full access to the GIMP and GTK+ API (at least not
limited by these), and can use any other library that is available for
their programming languages.
Again, that's a weak distinction - you could create extensions for the
TinyScheme interpreter that do use e.g. an FFT library, or add GTK+
support.
4. Intended use
----------------------------
Scripts are intended for using existing GIMP functionality and making
it easier to use, for example by grouping tasks.
"Select, copy, duplicate, blur, move" would be a workflow that is done
with a script.
Plug-ins are intended for adding to GIMP functionality in ways that
can't be done - or can't be done efficiently - using the existing
procedures.
Possible future developments
----------------------------
There are plans to make script behave more like plug-ins - not keep
them in memory, only execute them when their installed procedures are
called. This will reduce the memory footprint as well as the
overloading problem - currently, all script procedures share the same
name space. This is very interesting if two script authors decide to
use the same names for helper functions (think "(add 5 3)").
There is also the plan to obsolete Script-Fu and make Python the
default language for extending GIMP. There is an emulation layer that
does provide almost the same interface for writing simply script-like
plug-ins in Python (have a look at the plug-ins that do come with GIMP
by default, most of them should have a "import gimpfu" at the
beginning.
HTH,
Michael
Message-ID:<PThkl.15874$YU2.12259@nlpi066.nbdc.sbc.com>
Subject:
Re: Gimp Plug-ins
Date:Tue, 10 Feb 2009 17:25:19 +0100
On Tue, 10 Feb 2009 03:09:45 -0800, Michael Schumacher wrote:
> On 9 Feb., 19:50, measekite <inkysti...@oem.com> wrote:
>
>> Then what is the difference between a script and a plug-in?
>
> There are four main differences:
>
>
> 1. Programing language
> ----------------------------
>
> - Scripts are written in Scheme.
>
> - Plug-ins are written in C, C++, Python, Perl, C# or any other
> language that can
> a) make use of the libgimp* header files and/or libraries and
> b) create executables that can be run by GIMP, sometimes by using
> the language's own interpreter
>
> This is a weak distinction, of course - nobody would prevent you from
> creating modules for a Scheme interpreter (a more sophisticated one
> than TinyScheme, most probably) and create plug-ins in Scheme.
>
>
> 2. Execution workflow
> ----------------------------
>
> - Scripts are run by the Script-Fu extension of GIMP (think of it as a
> plug-in, although it stays around the whole time an instance of GIMP
> is running). All scripts are read completely when GIMP starts or when
> you do manually refresh them. This is why Script-Fu does use a
> considerable amount of GIMP's start-up time.
> The procedures that are implemented by the scripts do stay in memory
> all this time.
> If you call a script-fu-* procedure, the procedure is executed by the
> Script-Fu extension.
>
> - Plug-ins are called ("queried") once when GIMP starts for the first
> time, and then only if the plug-in executable has changed (this is
> determined by the file's timestamp). A cache file (pluginrc) is
> written in your GIMP profile directory, containing the signatures of
> the procedures (a description containing its name and its parameters).
> If you call one of these procedures, then the plug-in is executed.
> You can change a plug-in while GIMP is running, and the new code will
> be used (you may have to compile it, of course; for Python plug-in
> that's again done automatically).
>
>
> 3. Accessible API
> ----------------------------
>
> - Scripts have limited access to the GIMP (only via the PDB) and GTK+
> API ("none") (and other libraries, for that matter). You won't be
> working with image tiles in GIMP scripts, for example - a performance
> issue. You won't be creating your own user interface - Script-fu does
> provide a set of elements for data entry, and that it. You won't be
> using an arbitrary C library in your script, e.g. to do FFT or face
> recognition.
>
> - Plug-ins do have full access to the GIMP and GTK+ API (at least not
> limited by these), and can use any other library that is available for
> their programming languages.
> Again, that's a weak distinction - you could create extensions for the
> TinyScheme interpreter that do use e.g. an FFT library, or add GTK+
> support.
>
>
> 4. Intended use
> ----------------------------
>
> Scripts are intended for using existing GIMP functionality and making
> it easier to use, for example by grouping tasks.
> "Select, copy, duplicate, blur, move" would be a workflow that is done
> with a script.
>
> Plug-ins are intended for adding to GIMP functionality in ways that
> can't be done - or can't be done efficiently - using the existing
> procedures.
>
>
> Possible future developments
> ----------------------------
>
>
> There are plans to make script behave more like plug-ins - not keep
> them in memory, only execute them when their installed procedures are
> called. This will reduce the memory footprint as well as the
> overloading problem - currently, all script procedures share the same
> name space. This is very interesting if two script authors decide to
> use the same names for helper functions (think "(add 5 3)").
>
> There is also the plan to obsolete Script-Fu and make Python the
> default language for extending GIMP. There is an emulation layer that
> does provide almost the same interface for writing simply script-like
> plug-ins in Python (have a look at the plug-ins that do come with GIMP
> by default, most of them should have a "import gimpfu" at the
> beginning.
>
>
> HTH,
> Michael
Thanks
Message-ID:<6v7jlcFicajrU1@mid.uni-berlin.de>
Subject:
Re: Gimp Plug-ins
Date:Sun, 8 Feb 2009 09:32:45 +0100
On Sun, 08 Feb 2009 07:39:57 +0000, measekite wrote: > On Sat, 07 Feb 2009 21:51:20 -0800, Owen wrote: > >> Say the plug in has a 'scm' extension >> >> Place the script into your .gimp/scripts directory (note the dot . >> before the gimp) >> >> […] > > I found a .gimp hidden folder in my home folder. Under that there were > two folders. One was called plugins and the other scripts. Both were > empty. > > I also have a gimp folder under /usr/share > > Under there I found a scripts folder with bunch of scm files. Do I copy > the scm files there or what? Depends if you want to install the script for all users on that machine or just for one user. The home folder is for you and `/usr/share/…` is for all users. Needs root privileges to install the script there. Ciao, Marc 'BlackJack' Rintsch
Message-ID:<fGojl.16325$yr3.3831@nlpi068.nbdc.sbc.com>
Subject:
Gimp Plug-ins
Date:Sun, 8 Feb 2009 00:19:39 +0100
Can someone describe in DETAIL the steps necessary to install plug-ins in Gimp and then how to find them in the menu and use them. I found the website where you can see plug-ins so where do we go from there?
Message-ID:<1a01b4a6-02a2-4c60-8e35-72106765f174@z6g2000pre.googlegroups.com>
Subject:
Re: Gimp Plug-ins
Date:Sun, 8 Feb 2009 06:51:20 +0100
On Feb 8, 10:19 am, measekite <inkysti...@oem.com> wrote: > Can someone describe in DETAIL the steps necessary to install plug-ins in > Gimp and then how to find them in the menu and use them. > > I found the website where you can see plug-ins so where do we go from > there? Say the plug in has a 'scm' extension Place the script into your .gimp/scripts directory (note the dot . before the gimp) To find where it will appear, open in a text editor and look for something like (script-fu-register "script-fu-image-subdivide" _"<Image>/_ATG/_Tools/_Image subdivide" "Subdivide the image in MxN Rows and Columns and save any rectangular portion in the new files." That third line tells you where to find it Owen
Message-ID:<GVvjl.17196$c45.7943@nlpi065.nbdc.sbc.com>
Subject:
Re: Gimp Plug-ins
Date:Sun, 8 Feb 2009 08:33:58 +0100
On Sat, 07 Feb 2009 21:51:20 -0800, Owen wrote: > On Feb 8, 10:19 am, measekite <inkysti...@oem.com> wrote: >> Can someone describe in DETAIL the steps necessary to install plug-ins in >> Gimp and then how to find them in the menu and use them. >> >> I found the website where you can see plug-ins so where do we go from >> there? > > Say the plug in has a 'scm' extension > > Place the script into your .gimp/scripts directory (note the dot . > before the gimp) > > To find where it will appear, open in a text editor and look for > something like > > (script-fu-register > "script-fu-image-subdivide" > _"<Image>/_ATG/_Tools/_Image subdivide" > "Subdivide the image in MxN Rows and Columns and save any rectangular > portion in the new files." > > That third line tells you where to find it > > > > Owen Thanks but I am not familiar enough with Gimp and plugins to fully understand what you are saying. I did download a scm file.
Message-ID:<h%vjl.17197$c45.12777@nlpi065.nbdc.sbc.com>
Subject:
Re: Gimp Plug-ins
Date:Sun, 8 Feb 2009 08:39:57 +0100
On Sat, 07 Feb 2009 21:51:20 -0800, Owen wrote: > On Feb 8, 10:19 am, measekite <inkysti...@oem.com> wrote: >> Can someone describe in DETAIL the steps necessary to install plug-ins in >> Gimp and then how to find them in the menu and use them. >> >> I found the website where you can see plug-ins so where do we go from >> there? > > Say the plug in has a 'scm' extension > > Place the script into your .gimp/scripts directory (note the dot . > before the gimp) > > To find where it will appear, open in a text editor and look for > something like > > (script-fu-register > "script-fu-image-subdivide" > _"<Image>/_ATG/_Tools/_Image subdivide" > "Subdivide the image in MxN Rows and Columns and save any rectangular > portion in the new files." > > That third line tells you where to find it > > > > Owen I found a .gimp hidden folder in my home folder. Under that there were two folders. One was called plugins and the other scripts. Both were empty. I also have a gimp folder under /usr/share Under there I found a scripts folder with bunch of scm files. Do I copy the scm files there or what?
Message-ID:<5a9e1bd5-aac9-40ab-834a-d1f954072271@j8g2000yql.googlegroups.com>
Subject:
Re: Gimp Plug-ins
Date:Sun, 8 Feb 2009 09:16:50 +0100
On Feb 8, 2:39=A0am, measekite <inkysti...@oem.com> wrote:
> On Sat, 07 Feb 2009 21:51:20 -0800, Owen wrote:
> > On Feb 8, 10:19 am, measekite <inkysti...@oem.com> wrote:
> >> Can someone describe in DETAIL the steps necessary to install plug-ins=
in
> >> Gimp and then how to find them in the menu and use them.
>
> >> I found the website where you can see plug-ins so where do we go from
> >> there?
>
> > Say the plug in has a 'scm' extension
>
> > Place the script into your .gimp/scripts directory (note the dot =A0.
> > before the gimp)
>
> > To find where it will appear, open in a text editor and look for
> > something like
>
> > (script-fu-register
> > =A0"script-fu-image-subdivide"
> > =A0_"<Image>/_ATG/_Tools/_Image subdivide"
> > =A0"Subdivide the image in MxN Rows and Columns and save any rectangula=
r
> > portion in the new files."
>
> > That third line tells you where to find it
>
> > Owen
>
> I found a .gimp hidden folder in my home folder. =A0Under that there were
> two folders. =A0One was called plugins and the other scripts. =A0Both wer=
e
> empty.
>
> I also have a gimp folder under /usr/share
>
> Under there I found a scripts folder with bunch of scm files. =A0Do I cop=
y
> the scm files there or what?
Hi, I've been placing my .scm files into the "scripts" folder which I
have here in my folder hierarchy:
gimp-2,0/
share/
gimp/
2.0/
scripts
This should work for you.
Message-ID:<fHDjl.13274$as4.5949@nlpi069.nbdc.sbc.com>
Subject:
Re: Gimp Plug-ins
Date:Sun, 8 Feb 2009 17:24:43 +0100
On Sun, 08 Feb 2009 00:16:50 -0800, veyoung52 wrote: > On Feb 8, 2:39 am, measekite <inkysti...@oem.com> wrote: >> On Sat, 07 Feb 2009 21:51:20 -0800, Owen wrote: >> > On Feb 8, 10:19 am, measekite <inkysti...@oem.com> wrote: >> >> Can someone describe in DETAIL the steps necessary to install plug-ins in >> >> Gimp and then how to find them in the menu and use them. >> >> >> I found the website where you can see plug-ins so where do we go from >> >> there? >> >> > Say the plug in has a 'scm' extension >> >> > Place the script into your .gimp/scripts directory (note the dot . >> > before the gimp) >> >> > To find where it will appear, open in a text editor and look for >> > something like >> >> > (script-fu-register >> > "script-fu-image-subdivide" >> > _"<Image>/_ATG/_Tools/_Image subdivide" >> > "Subdivide the image in MxN Rows and Columns and save any rectangular >> > portion in the new files." >> >> > That third line tells you where to find it >> >> > Owen >> >> I found a .gimp hidden folder in my home folder. Under that there were >> two folders. One was called plugins and the other scripts. Both were >> empty. >> >> I also have a gimp folder under /usr/share >> >> Under there I found a scripts folder with bunch of scm files. Do I copy >> the scm files there or what? > > Hi, I've been placing my .scm files into the "scripts" folder which I > have here in my folder hierarchy: > gimp-2,0/ > share/ > gimp/ > 2.0/ > scripts > This should work for you. Thanks
Message-ID:<vHLjl.15723$YU2.14300@nlpi066.nbdc.sbc.com>
Subject:
Re: Gimp Plug-ins
Date:Mon, 9 Feb 2009 02:31:07 +0100
On Sun, 08 Feb 2009 00:16:50 -0800, veyoung52 wrote: > On Feb 8, 2:39 am, measekite <inkysti...@oem.com> wrote: >> On Sat, 07 Feb 2009 21:51:20 -0800, Owen wrote: >> > On Feb 8, 10:19 am, measekite <inkysti...@oem.com> wrote: >> >> Can someone describe in DETAIL the steps necessary to install plug-ins in >> >> Gimp and then how to find them in the menu and use them. >> >> >> I found the website where you can see plug-ins so where do we go from >> >> there? >> >> > Say the plug in has a 'scm' extension >> >> > Place the script into your .gimp/scripts directory (note the dot . >> > before the gimp) >> >> > To find where it will appear, open in a text editor and look for >> > something like >> >> > (script-fu-register >> > "script-fu-image-subdivide" >> > _"<Image>/_ATG/_Tools/_Image subdivide" >> > "Subdivide the image in MxN Rows and Columns and save any rectangular >> > portion in the new files." >> >> > That third line tells you where to find it >> >> > Owen >> >> I found a .gimp hidden folder in my home folder. Under that there were >> two folders. One was called plugins and the other scripts. Both were >> empty. >> >> I also have a gimp folder under /usr/share >> >> Under there I found a scripts folder with bunch of scm files. Do I copy >> the scm files there or what? > > Hi, I've been placing my .scm files into the "scripts" folder which I > have here in my folder hierarchy: > gimp-2,0/ > share/ > gimp/ > 2.0/ > scripts > This should work for you. Finally downloaded a bunch of .scm files and placed them in the .Gimp2/scripts folder. I did find most of them in various places in the menu system and am learning how to use them notwithstanding spartan documentation. I also downloaded a .py file and placed it also in the scripts folder but it does not appear in the Gimp menu. Where do you place the python .py files? One of the major problems with Gimp is it does not force the plug-in writer to place all of their files in one plug-in folder wither in the users home folder to restrict it to one user or in the usr/share/??? folder for all users to use.
Message-ID:<dxSjl.20323$aJ3.680@newsfe23.ams2>
Subject:
Re: Gimp Plug-ins
Date:Mon, 9 Feb 2009 10:18:01 +0100
On Mon, 09 Feb 2009 01:31:07 +0000, measekite wrote: > On Sun, 08 Feb 2009 00:16:50 -0800, veyoung52 wrote: > >> On Feb 8, 2:39 am, measekite <inkysti...@oem.com> wrote: >>> On Sat, 07 Feb 2009 21:51:20 -0800, Owen wrote: >>> > On Feb 8, 10:19 am, measekite <inkysti...@oem.com> wrote: >>> >> Can someone describe in DETAIL the steps necessary to install >>> >> plug-ins in Gimp and then how to find them in the menu and use >>> >> them. >>> >>> >> I found the website where you can see plug-ins so where do we go >>> >> from there? >>> >>> > Say the plug in has a 'scm' extension >>> <snip> > > Finally downloaded a bunch of .scm files and placed them in the > .Gimp2/scripts folder. I did find most of them in various places in the > menu system and am learning how to use them notwithstanding spartan > documentation. > > I also downloaded a .py file and placed it also in the scripts folder > but it does not appear in the Gimp menu. > > Where do you place the python .py files? > <snip> You don't say which Gimp version you are using, so depending on 2.4 or 2.6 some menu items might be in different places and some scripts / plugins might or might not work. Pleased that you have the scripts working but you should really use your home folder, if only for ease of copying. Did you check in "preferences" -> "folders" to see if the home folder was included. You can have the scripts anywhere providing you tell gimp where they are. The same applies to .py - check the folder locations. The .py files are python scripts so you need the python libraries installed. These should already be there but check. The .py files should go in the plugin folder and each script should be made executable. Depending on the script they can appear in different places, I have a couple which make their own menu "Python-fu" and another which appears in the image menu, so no hard and fast rule. I'm still on gimp 2.4.4 so take that into account. -- rich
Message-ID:<250d8e4f-6aac-4f2b-9789-5de532483a63@l16g2000yqo.googlegroups.com>
Subject:
Re: Gimp Plug-ins
Date:Mon, 9 Feb 2009 14:13:13 +0100
On 9 Feb., 02:31, measekite <inkysti...@oem.com> wrote: > One of the major problems with Gimp is it does not force the plug-in > writer to place all of their files in one plug-in folder wither in the > users home folder to restrict it to one user or in the usr/share/??? > folder for all users to use. You can have as many plug-in folders as you wish - that's configurable in GIMP's preferences. If you are referring to the fact that scripts are kept separate from plug-ins - well, maybe this could be because they are different? HTH, Michael
Message-ID:<CV_jl.4236$%54.2689@nlpi070.nbdc.sbc.com>
Subject:
Re: Gimp Plug-ins
Date:Mon, 9 Feb 2009 19:50:10 +0100
On Mon, 09 Feb 2009 05:13:13 -0800, Michael Schumacher wrote: > On 9 Feb., 02:31, measekite <inkysti...@oem.com> wrote: > >> One of the major problems with Gimp is it does not force the plug-in >> writer to place all of their files in one plug-in folder wither in the >> users home folder to restrict it to one user or in the usr/share/??? >> folder for all users to use. > > You can have as many plug-in folders as you wish - that's configurable > in GIMP's preferences. > > If you are referring to the fact that scripts are kept separate from > plug-ins - well, maybe this could be because they are different? > > > HTH, > Michael Then what is the difference between a script and a plug-in?
Message-ID:<MPG.23faaf22e8b5c32698974c@127.0.0.1>
Subject:
Re: Gimp Plug-ins
Date:Mon, 9 Feb 2009 21:23:18 +0100
In article <CV_jl.4236$%54.2689@nlpi070.nbdc.sbc.com>, inkystinky@oem.com says... > > Then what is the difference between a script and a plug-in? plugin is a piece of program code, doing some action, which is called by gimp. script is interpreted text ( similar as bat, cmd, vbs or js ), that tells gimp what todo ( either by internal features, either by external plugins ) There are dedicated folders for both, either in machine and user scope. -- Poutnik
Message-ID:<20090210091347@usenet.piggo.com>
Subject:
Re: Gimp Plug-ins
Date:Tue, 10 Feb 2009 00:16:26 +0100
* measekite wrote : > On Mon, 09 Feb 2009 05:13:13 -0800, Michael Schumacher wrote: > >> On 9 Feb., 02:31, measekite <inkysti...@oem.com> wrote: >> >>> One of the major problems with Gimp is it does not force the plug-in >>> writer to place all of their files in one plug-in folder wither in the >>> users home folder to restrict it to one user or in the usr/share/??? >>> folder for all users to use. >> >> You can have as many plug-in folders as you wish - that's configurable >> in GIMP's preferences. >> >> If you are referring to the fact that scripts are kept separate from >> plug-ins - well, maybe this could be because they are different? > > Then what is the difference between a script and a plug-in? Scripts have the .scm file extension and are basically a text file with GIMP commands scripted in them. Plugins are typically binary executable files that can do things not native to GIMP. eg run UFRAW That's my layman's was of thinking of it. :) -- Troy Piggins
Message-ID:<22f7db5c-765d-4158-9f1c-e4ea0e8b89f2@j1g2000yqi.googlegroups.com>
Subject:
Re: Gimp Plug-ins
Date:Tue, 10 Feb 2009 10:53:23 +0100
On 10 Feb., 00:16, Troy Piggins <usenet-0...@piggo.com> wrote: > Plugins are typically binary executable files that can do things > not native to GIMP. =A0eg run UFRAW Python, Perl? Yes, these are plug-ins :) Although at least the former do get compiled on load. They are executables, though. And do not work if their executable bit is not set, at least on platforms that do require this for executables. Michael
Message-ID:<3f91ada0-731e-4681-8bec-3fa69922ac36@g38g2000yqd.googlegroups.com>
Subject:
Re: Gimp Plug-ins
Date:Tue, 10 Feb 2009 12:09:45 +0100
On 9 Feb., 19:50, measekite <inkysti...@oem.com> wrote:
> Then what is the difference between a script and a plug-in?
There are four main differences:
1. Programing language
----------------------------
- Scripts are written in Scheme.
- Plug-ins are written in C, C++, Python, Perl, C# or any other
language that can
a) make use of the libgimp* header files and/or libraries and
b) create executables that can be run by GIMP, sometimes by using
the language's own interpreter
This is a weak distinction, of course - nobody would prevent you from
creating modules for a Scheme interpreter (a more sophisticated one
than TinyScheme, most probably) and create plug-ins in Scheme.
2. Execution workflow
----------------------------
- Scripts are run by the Script-Fu extension of GIMP (think of it as a
plug-in, although it stays around the whole time an instance of GIMP
is running). All scripts are read completely when GIMP starts or when
you do manually refresh them. This is why Script-Fu does use a
considerable amount of GIMP's start-up time.
The procedures that are implemented by the scripts do stay in memory
all this time.
If you call a script-fu-* procedure, the procedure is executed by the
Script-Fu extension.
- Plug-ins are called ("queried") once when GIMP starts for the first
time, and then only if the plug-in executable has changed (this is
determined by the file's timestamp). A cache file (pluginrc) is
written in your GIMP profile directory, containing the signatures of
the procedures (a description containing its name and its parameters).
If you call one of these procedures, then the plug-in is executed.
You can change a plug-in while GIMP is running, and the new code will
be used (you may have to compile it, of course; for Python plug-in
that's again done automatically).
3. Accessible API
----------------------------
- Scripts have limited access to the GIMP (only via the PDB) and GTK+
API ("none") (and other libraries, for that matter). You won't be
working with image tiles in GIMP scripts, for example - a performance
issue. You won't be creating your own user interface - Script-fu does
provide a set of elements for data entry, and that it. You won't be
using an arbitrary C library in your script, e.g. to do FFT or face
recognition.
- Plug-ins do have full access to the GIMP and GTK+ API (at least not
limited by these), and can use any other library that is available for
their programming languages.
Again, that's a weak distinction - you could create extensions for the
TinyScheme interpreter that do use e.g. an FFT library, or add GTK+
support.
4. Intended use
----------------------------
Scripts are intended for using existing GIMP functionality and making
it easier to use, for example by grouping tasks.
"Select, copy, duplicate, blur, move" would be a workflow that is done
with a script.
Plug-ins are intended for adding to GIMP functionality in ways that
can't be done - or can't be done efficiently - using the existing
procedures.
Possible future developments
----------------------------
There are plans to make script behave more like plug-ins - not keep
them in memory, only execute them when their installed procedures are
called. This will reduce the memory footprint as well as the
overloading problem - currently, all script procedures share the same
name space. This is very interesting if two script authors decide to
use the same names for helper functions (think "(add 5 3)").
There is also the plan to obsolete Script-Fu and make Python the
default language for extending GIMP. There is an emulation layer that
does provide almost the same interface for writing simply script-like
plug-ins in Python (have a look at the plug-ins that do come with GIMP
by default, most of them should have a "import gimpfu" at the
beginning.
HTH,
Michael
Message-ID:<PThkl.15874$YU2.12259@nlpi066.nbdc.sbc.com>
Subject:
Re: Gimp Plug-ins
Date:Tue, 10 Feb 2009 17:25:19 +0100
On Tue, 10 Feb 2009 03:09:45 -0800, Michael Schumacher wrote:
> On 9 Feb., 19:50, measekite <inkysti...@oem.com> wrote:
>
>> Then what is the difference between a script and a plug-in?
>
> There are four main differences:
>
>
> 1. Programing language
> ----------------------------
>
> - Scripts are written in Scheme.
>
> - Plug-ins are written in C, C++, Python, Perl, C# or any other
> language that can
> a) make use of the libgimp* header files and/or libraries and
> b) create executables that can be run by GIMP, sometimes by using
> the language's own interpreter
>
> This is a weak distinction, of course - nobody would prevent you from
> creating modules for a Scheme interpreter (a more sophisticated one
> than TinyScheme, most probably) and create plug-ins in Scheme.
>
>
> 2. Execution workflow
> ----------------------------
>
> - Scripts are run by the Script-Fu extension of GIMP (think of it as a
> plug-in, although it stays around the whole time an instance of GIMP
> is running). All scripts are read completely when GIMP starts or when
> you do manually refresh them. This is why Script-Fu does use a
> considerable amount of GIMP's start-up time.
> The procedures that are implemented by the scripts do stay in memory
> all this time.
> If you call a script-fu-* procedure, the procedure is executed by the
> Script-Fu extension.
>
> - Plug-ins are called ("queried") once when GIMP starts for the first
> time, and then only if the plug-in executable has changed (this is
> determined by the file's timestamp). A cache file (pluginrc) is
> written in your GIMP profile directory, containing the signatures of
> the procedures (a description containing its name and its parameters).
> If you call one of these procedures, then the plug-in is executed.
> You can change a plug-in while GIMP is running, and the new code will
> be used (you may have to compile it, of course; for Python plug-in
> that's again done automatically).
>
>
> 3. Accessible API
> ----------------------------
>
> - Scripts have limited access to the GIMP (only via the PDB) and GTK+
> API ("none") (and other libraries, for that matter). You won't be
> working with image tiles in GIMP scripts, for example - a performance
> issue. You won't be creating your own user interface - Script-fu does
> provide a set of elements for data entry, and that it. You won't be
> using an arbitrary C library in your script, e.g. to do FFT or face
> recognition.
>
> - Plug-ins do have full access to the GIMP and GTK+ API (at least not
> limited by these), and can use any other library that is available for
> their programming languages.
> Again, that's a weak distinction - you could create extensions for the
> TinyScheme interpreter that do use e.g. an FFT library, or add GTK+
> support.
>
>
> 4. Intended use
> ----------------------------
>
> Scripts are intended for using existing GIMP functionality and making
> it easier to use, for example by grouping tasks.
> "Select, copy, duplicate, blur, move" would be a workflow that is done
> with a script.
>
> Plug-ins are intended for adding to GIMP functionality in ways that
> can't be done - or can't be done efficiently - using the existing
> procedures.
>
>
> Possible future developments
> ----------------------------
>
>
> There are plans to make script behave more like plug-ins - not keep
> them in memory, only execute them when their installed procedures are
> called. This will reduce the memory footprint as well as the
> overloading problem - currently, all script procedures share the same
> name space. This is very interesting if two script authors decide to
> use the same names for helper functions (think "(add 5 3)").
>
> There is also the plan to obsolete Script-Fu and make Python the
> default language for extending GIMP. There is an emulation layer that
> does provide almost the same interface for writing simply script-like
> plug-ins in Python (have a look at the plug-ins that do come with GIMP
> by default, most of them should have a "import gimpfu" at the
> beginning.
>
>
> HTH,
> Michael
Thanks
Message-ID:<6v7jlcFicajrU1@mid.uni-berlin.de>
Subject:
Re: Gimp Plug-ins
Date:Sun, 8 Feb 2009 09:32:45 +0100
On Sun, 08 Feb 2009 07:39:57 +0000, measekite wrote: > On Sat, 07 Feb 2009 21:51:20 -0800, Owen wrote: > >> Say the plug in has a 'scm' extension >> >> Place the script into your .gimp/scripts directory (note the dot . >> before the gimp) >> >> […] > > I found a .gimp hidden folder in my home folder. Under that there were > two folders. One was called plugins and the other scripts. Both were > empty. > > I also have a gimp folder under /usr/share > > Under there I found a scripts folder with bunch of scm files. Do I copy > the scm files there or what? Depends if you want to install the script for all users on that machine or just for one user. The home folder is for you and `/usr/share/…` is for all users. Needs root privileges to install the script there. Ciao, Marc 'BlackJack' Rintsch