Re: [Gimp-developer] GIMP-Python

2009-04-07 Thread Michael Schumacher
Andrei Simion wrote:

 Does anybody know where I can download GIMP-Python from? Our sysadmin 
 says that whatever he found on the Internet does not work.

What did he find, and why does it not work?


Michael

-- 
GIMP  http://www.gimp.org  | IRC: irc://irc.gimp.org/gimp
Wiki  http://wiki.gimp.org | .de: http://gimpforum.de
Plug-ins  http://registry.gimp.org |
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp python

2006-10-05 Thread Sven Neumann
Hi,

On Fri, 2006-09-22 at 00:16 +0200, Sven Neumann wrote:

http://bugzilla.gnome.org/show_bug.cgi?id=351287
 
 In the meantime, while Carol is trying to steal your time with pointless
 mails, the Python i18n effort is basically done. It would be nice if
 someone could review the strings that have been marked for translation.
 I would like to point translators to the new set of translatable
 messages soon and they would probably appreciate if the strings would
 not have to be changed before 2.4.

Should we consider the messages as fine then?


Sven


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp python

2006-10-05 Thread Alexandre Prokoudine

On 10/5/06, Sven Neumann wrote:


 In the meantime, while Carol is trying to steal your time with pointless
 mails, the Python i18n effort is basically done. It would be nice if
 someone could review the strings that have been marked for translation.
 I would like to point translators to the new set of translatable
 messages soon and they would probably appreciate if the strings would
 not have to be changed before 2.4.

Should we consider the messages as fine then?


Does reviewing mean that someone goes through scripts, marks forgotten
messages and err... unmarks those that should not be translated?

Alexandre
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp python

2006-10-05 Thread Sven Neumann
Hi,

On Thu, 2006-10-05 at 11:36 +0400, Alexandre Prokoudine wrote:

 Does reviewing mean that someone goes through scripts, marks forgotten
 messages and err... unmarks those that should not be translated?

Sure, I might have forgotten a message or two. But the main point of
such a review is that someone else, preferably a native speaker, looks
over the messages and checks them for spelling and grammatical errors.
The easiest way to do this is by looking at the gimp20.pot file in the
po-python directory.


Sven


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp python

2006-09-21 Thread Sven Neumann
Hi,

On Sun, 2006-09-17 at 15:51 +0200, Sven Neumann wrote:

   http://bugzilla.gnome.org/show_bug.cgi?id=351287

In the meantime, while Carol is trying to steal your time with pointless
mails, the Python i18n effort is basically done. It would be nice if
someone could review the strings that have been marked for translation.
I would like to point translators to the new set of translatable
messages soon and they would probably appreciate if the strings would
not have to be changed before 2.4.


Sven


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp python

2006-09-17 Thread Sven Neumann
Hi,

On Wed, 2006-09-13 at 10:31 +0200, Sven Neumann wrote:

 the internationalisation of the Gimp Python bindings and plug-ins is
 still pending:
 
  http://bugzilla.gnome.org/show_bug.cgi?id=351287

We have come a good deal further here in the meantime. The framework for
internationalisation is now in place. What's missing is the review of
the strings (basically the same job as what's needed for Script-Fu, only
much fewer strings) and marking them for translation. Any volunteer who
wants to go over the python plug-ins, check that the strings are OK and
that the procedure blurbs have the same style as what is used by the
plug-ins? The files to look at are (from the plug-ins/pygimp/plug-ins
folder):

 clothify.py
 colorxhtml.py
 foggify.py
 happy-valley-relief.py
 palette-offset.py
 palette-sort.py
 palette-to-gradient.py
 pdbbrowse.py
 py-slice.py
 shadow_bevel.py

This list does intentionally leave out plug-ins that are already
internationalized or are not installed in a stable release and are only
included as examples.


Sven




___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp python

2006-09-13 Thread Sven Neumann
Hi,

the internationalisation of the Gimp Python bindings and plug-ins is
still pending:

 http://bugzilla.gnome.org/show_bug.cgi?id=351287

Does this mean that noone is interested in having the existing Python
scripts in GIMP 2.4? It should not be difficult to make the plug-ins use
the existing gettext module for Python
(http://docs.python.org/lib/module-gettext.html) and that's basically
all that needs to be done.

Perhaps someone can look over the strings in the meantime and make sure
that there are no typos or other errors?


Sven


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp python

2006-08-31 Thread Sven Neumann
Moin,

Regarding http://bugzilla.gnome.org/show_bug.cgi?id=351287 some progress
has been made in CVS. To avoid i18n problems, the procedure registration
in pygimp has been changed (in a hopefully backwards compatible way). It
shouldn't be too difficult to add i18n now. But still, there hasn't been
any further progress on this. We urgently need this to happen so that we
can enter string freeze. Any volunteers?


Sven


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp python

2006-08-14 Thread Sven Neumann
Hi,

I have opened a bug report on what I believe to be the remaining issues
with gimp-python:

http://bugzilla.gnome.org/show_bug.cgi?id=351287

Even though I said earlier that's it's perhaps too late for adding i18n
support, I feel now that we absolutely need to do this if we want to
install any Python plug-ins by default.

But still, if i18n support is added, the usefulness of the plug-ins
should be reviewed and only the plug-ins that are considered useful
should be installed and have their strings marked for translation (and
reviewed).


Sven


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp python

2006-08-14 Thread Joao S. O. Bueno Calligaris
On Monday 14 August 2006 04:17 pm, Sven Neumann wrote:
 Hi,

 I have opened a bug report on what I believe to be the remaining
 issues with gimp-python:

 http://bugzilla.gnome.org/show_bug.cgi?id=351287

 Even though I said earlier that's it's perhaps too late for adding
 i18n support, I feel now that we absolutely need to do this if we
 want to install any Python plug-ins by default.

 But still, if i18n support is added, the usefulness of the plug-ins
 should be reviewed and only the plug-ins that are considered useful
 should be installed and have their strings marked for translation
 (and reviewed).


 Sven



Hi Sven - 
thank you for getting to this. 

I am rather busy these days, but I will dig into it as soon as I have 
some time to the GIMP. I that is too late to 2.4 - well, thats is 
life. 

And in fact, even very simple scripts can be more usefull than the 
ones that ship by default, and at once be so simple taht could 
encourage more people to give a try at editing then. 
(center layer, apply a filter varying its parameters in a sequence o 
vertical slices of an image, and so on).

Lets see what we all can come up with.

JS
--
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp-python: Artefacts when creating layer

2006-06-04 Thread Sven Neumann
Hi,

On Sat, 2006-06-03 at 12:07 +0200, Sebastian Breuers wrote:

 The plug-in, I'm writing, creates a number of layers, every layer receives an 
 object, for example a circle (created by ellipse selection, an selection 
 fill), but somewhen, don't know why, the layer contains not only the desired 
 circle but also some artefacts. Stripes, areas of white, the mouse cursor, 
 things they should not be there.
 Is that a problem that can be solved by a certain programmable handling or do 
 I have to remove these artefacts by hand?

Clearing the layers before use would probably help.


Sven


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp-python: Artefacts when creating layer

2006-06-04 Thread Sven Neumann
Hi,

On Sat, 2006-06-03 at 11:58 -0300, Joao S. O. Bueno Calligaris wrote:

 For C plug-ins  that might be true. However, python plug-ins are not 
 good in dealing directly with pixels - that is, for rendering things.

There is no need to access pixels directly. We are not asking the C
programmer to iterate over the pixels and clear them directly. Calling
gimp-drawable-fill is sufficient, no matter what language binding is
being used.


Sven


___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp-python: Artefacts when creating layer

2006-06-04 Thread Joao S. O. Bueno Calligaris
On Sunday 04 June 2006 02:45 pm, Sven Neumann wrote:
 Hi,

 On Sat, 2006-06-03 at 11:58 -0300, Joao S. O. Bueno Calligaris 
wrote:
  For C plug-ins  that might be true. However, python plug-ins are
  not good in dealing directly with pixels - that is, for rendering
  things.

 There is no need to access pixels directly. We are not asking the C
 programmer to iterate over the pixels and clear them directly.
 Calling gimp-drawable-fill is sufficient, no matter what language
 binding is being used.

That was not what I meant anyway. The matter is: the only advantadge 
of not having a layer automatically cleared when it is created, is 
sparing somw cycles if you are generating the layers content. 

Generate the layers content from within thew python code is something 
that, although can be done, is so slow, that the time spent 
auto-clearing the table becomes negligible.

It may look as a single extra line of code for us.  For one trying 
with the scripts, it is one more secret to be found or overcame, 
that might not take negligible time. That is the motive for my 
suggestion.

JS
--



 Sven


 ___
 Gimp-developer mailing list
 Gimp-developer@lists.XCF.Berkeley.EDU
 https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-python: checking if point is in selection

2006-06-03 Thread Sebastian Breuers
Am Freitag, 2. Juni 2006 19:44 schrieb [EMAIL PROTECTED]:
 Quoting Sebastian Breuers [EMAIL PROTECTED]:
  i wondered if there is a possibility to check, if a point is in a given
  selection by using an internal gimp function.
  If it's not, could someone give me a hint, how to achieve this in
  creating an own function?

 I don't use Python-fu but the following Script-fu function should be
 easily ported (or perhaps you can find a better way):

 (define (point-in-selection image x y)
(let* (
(saved (car (gimp-selection-save image)))
(return-value)
)
  (gimp-rect-select image x y 1 1 CHANNEL-OP-INTERSECT 0 0)
  (set! return-value (car (gimp-selection-is-empty image)))
  (gimp-selection-load saved)
  (if (= return-value 0)
1
0
)
  )
)


Hi.

thanks for the tip. works fine.

seb

 Note that the selection does not include the points at the rightmost
 and bottommost edges. For example, if the selection is from (0,0) to
 (10,10) then the point (10,10) is *not* in the selection but (9,9)
 is. You may need to adjust things to account for this.
 ___
 Gimp-developer mailing list
 Gimp-developer@lists.XCF.Berkeley.EDU
 https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp-python: Artefacts when creating layer

2006-06-03 Thread Simon Budig
Sebastian Breuers ([EMAIL PROTECTED]) wrote:
 The plug-in, I'm writing, creates a number of layers, every layer receives an 
 object, for example a circle (created by ellipse selection, an selection 
 fill), but somewhen, don't know why, the layer contains not only the desired 
 circle but also some artefacts. Stripes, areas of white, the mouse cursor, 
 things they should not be there.
 Is that a problem that can be solved by a certain programmable handling or do 
 I have to remove these artefacts by hand?

That sounds as if you don't clear the layer before you use it for the
first time. Layers created from a Plugin are not initialized from the
very beginning. They need to be cleared using e.g. gimp_drawable_fill.

Hope this helps,
Simon
-- 
  [EMAIL PROTECTED]  http://simon.budig.de/
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp-python: Artefacts when creating layer

2006-06-03 Thread Alan Horkan

On Sat, 3 Jun 2006, Simon Budig wrote:

 Date: Sat, 3 Jun 2006 14:29:02 +0200
 From: Simon Budig [EMAIL PROTECTED]
 To: gimp-developer@lists.XCF.Berkeley.EDU
 Subject: Re: [Gimp-developer] Gimp-python: Artefacts when creating layer

 Sebastian Breuers ([EMAIL PROTECTED]) wrote:
  The plug-in, I'm writing, creates a number of layers, every layer receives 
  an
  object, for example a circle (created by ellipse selection, an selection
  fill), but somewhen, don't know why, the layer contains not only the desired
  circle but also some artefacts. Stripes, areas of white, the mouse cursor,
  things they should not be there.
  Is that a problem that can be solved by a certain programmable handling or 
  do
  I have to remove these artefacts by hand?

 That sounds as if you don't clear the layer before you use it for the
 first time. Layers created from a Plugin are not initialized from the
 very beginning. They need to be cleared using e.g. gimp_drawable_fill.

I remember getting caught out by this too.  Why is necessary to manually
clear a new layer rather than have it done automatically?

-- 
Alan

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp-python: Artefacts when creating layer

2006-06-03 Thread Simon Budig
Alan Horkan ([EMAIL PROTECTED]) wrote:
 On Sat, 3 Jun 2006, Simon Budig wrote:
  That sounds as if you don't clear the layer before you use it for the
  first time. Layers created from a Plugin are not initialized from the
  very beginning. They need to be cleared using e.g. gimp_drawable_fill.
 
 I remember getting caught out by this too.  Why is necessary to manually
 clear a new layer rather than have it done automatically?

I have no strong opinions on that. I guess the reasoning behind this
behaviour was a speed optimization: If a plugin later renders stuff to
a new layer anyway it would be a waste of time to clear it
automatically. If it doesn't it would just invoke gimp_drawable_fill. No
harm done, except that you have to know about it.

It might even matter for big images...

Bye,
 Simon
-- 
  [EMAIL PROTECTED]  http://simon.budig.de/
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp-python: Artefacts when creating layer

2006-06-03 Thread Joao S. O. Bueno Calligaris
On Saturday 03 June 2006 09:53 am, Simon Budig wrote:
 Alan Horkan ([EMAIL PROTECTED]) wrote:
  On Sat, 3 Jun 2006, Simon Budig wrote:
   That sounds as if you don't clear the layer before you use it
   for the first time. Layers created from a Plugin are not
   initialized from the very beginning. They need to be cleared
   using e.g. gimp_drawable_fill.
 
  I remember getting caught out by this too.  Why is necessary to
  manually clear a new layer rather than have it done
  automatically?

 I have no strong opinions on that. I guess the reasoning behind
 this behaviour was a speed optimization: If a plugin later renders
 stuff to a new layer anyway it would be a waste of time to clear it
 automatically. If it doesn't it would just invoke
 gimp_drawable_fill. No harm done, except that you have to know
 about it.

 It might even matter for big images...



For C plug-ins  that might be true. However, python plug-ins are not 
good in dealing directly with pixels - that is, for rendering things.

I guess the python api for creating a layer could create an empty one 
with no problems.

Regards,
JS
--

 Bye,
  Simon
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp-python: Artefacts when creating layer

2006-06-03 Thread Sebastian Breuers
Am Samstag, 3. Juni 2006 16:58 schrieb Joao S. O. Bueno Calligaris:
 On Saturday 03 June 2006 09:53 am, Simon Budig wrote:
  Alan Horkan ([EMAIL PROTECTED]) wrote:
   On Sat, 3 Jun 2006, Simon Budig wrote:
That sounds as if you don't clear the layer before you use it
for the first time. Layers created from a Plugin are not
initialized from the very beginning. They need to be cleared
using e.g. gimp_drawable_fill.
  

Thanks a lot,

that helped. Did it with:

newLayer.fill(TRANSPARENT_FILL)

seb

   I remember getting caught out by this too.  Why is necessary to
   manually clear a new layer rather than have it done
   automatically?
 
  I have no strong opinions on that. I guess the reasoning behind
  this behaviour was a speed optimization: If a plugin later renders
  stuff to a new layer anyway it would be a waste of time to clear it
  automatically. If it doesn't it would just invoke
  gimp_drawable_fill. No harm done, except that you have to know
  about it.
 
  It might even matter for big images...

 For C plug-ins  that might be true. However, python plug-ins are not
 good in dealing directly with pixels - that is, for rendering things.

 I guess the python api for creating a layer could create an empty one
 with no problems.

 Regards,
   JS
   --

  Bye,
   Simon

 ___
 Gimp-developer mailing list
 Gimp-developer@lists.XCF.Berkeley.EDU
 https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

-- 
Sebastian Breuers
Huhnsgasse 53
50676 Köln

Tel: 0221-2954235
Mobil: 0179-7841404
Mail: [EMAIL PROTECTED]
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-python: checking if point is in selection

2006-06-02 Thread saulgoode

Quoting Sebastian Breuers [EMAIL PROTECTED]:

i wondered if there is a possibility to check, if a point is in a given
selection by using an internal gimp function.
If it's not, could someone give me a hint, how to achieve this in creating an
own function?


I don't use Python-fu but the following Script-fu function should be  
easily ported (or perhaps you can find a better way):


(define (point-in-selection image x y)
  (let* (
  (saved (car (gimp-selection-save image)))
  (return-value)
  )
(gimp-rect-select image x y 1 1 CHANNEL-OP-INTERSECT 0 0)
(set! return-value (car (gimp-selection-is-empty image)))
(gimp-selection-load saved)
(if (= return-value 0)
  1
  0
  )
)
  )

Note that the selection does not include the points at the rightmost  
and bottommost edges. For example, if the selection is from (0,0) to  
(10,10) then the point (10,10) is *not* in the selection but (9,9)  
is. You may need to adjust things to account for this.

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-python: checking if point is in selection

2006-06-02 Thread Sven Neumann
Hi,

On Fri, 2006-06-02 at 13:48 +0200, Sebastian Breuers wrote:

 i wondered if there is a possibility to check, if a point is in a given 
 selection by using an internal gimp function.
 If it's not, could someone give me a hint, how to achieve this in creating an 
 own function?

Use gimp-image-get-selection to get the selection mask and check the
value of the pixel you are interested in.


Sven



___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-python: checking if point is in selection

2006-06-02 Thread Sebastian Breuers
Am Freitag, 2. Juni 2006 19:54 schrieben Sie:
 Hi,

 On Fri, 2006-06-02 at 13:48 +0200, Sebastian Breuers wrote:
  i wondered if there is a possibility to check, if a point is in a given
  selection by using an internal gimp function.
  If it's not, could someone give me a hint, how to achieve this in
  creating an own function?

 Use gimp-image-get-selection to get the selection mask and check the
 value of the pixel you are interested in.

Hi, Sven,

i've already found the selection function, but could you tell me how to check 
the value of the pixel?


 Sven

seb
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-python: checking if point is in selection

2006-06-02 Thread Michael Natterer
On Fri, 2006-06-02 at 23:16 +0200, Sebastian Breuers wrote:
 Am Freitag, 2. Juni 2006 19:54 schrieben Sie:
  Hi,
 
  On Fri, 2006-06-02 at 13:48 +0200, Sebastian Breuers wrote:
   i wondered if there is a possibility to check, if a point is in a given
   selection by using an internal gimp function.
   If it's not, could someone give me a hint, how to achieve this in
   creating an own function?
 
  Use gimp-image-get-selection to get the selection mask and check the
  value of the pixel you are interested in.
 
 Hi, Sven,
 
 i've already found the selection function, but could you tell me how to check 
 the value of the pixel?

Use gimp-selection-value

ciao,
--mitch

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp-Python with no ui? (external script)

2006-04-01 Thread Ministeyr

Manish Singh wrote:

 By the way, I thought the batch mode only understood scheme, so it 
would make the whole thing even more complicated.


 One line of scheme to call your python script won't increase the
 complexity appreciably.

The problem is that if i have huge lists and complex python objects in 
my external scripts, and i want to access them in the gimp's python-fu 
script, i have to pass them through scheme, and thus it means converting 
back and forth.

I will try to adapt with pickle if it works.

 If you want something better, why don't you contribute it?

I would make a mess, since i'm not really a good programmer (plus i 
don't know anything about gimp's internal structure or python's...).



Ministeyr
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp-Python with no ui? (external script)

2006-04-01 Thread Ministeyr

Carol Spears wrote:

i asked because i put instructions of how to do this online.

i have a crontab that runs gimp.

that being said, it has been running for so long now, i have no idea
what sort of mess it is making, but it was all so easy that it was a
pleasure to put the instructions online.


Well, i don't know if that is exactly what i meant, but i would still be 
grateful if you could give me the url to that document.

Thanks.


Ministeyr
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp-Python with no ui? (external script)

2006-04-01 Thread Carol Spears
On Sat, Apr 01, 2006 at 03:01:31PM +0200, Ministeyr wrote:
 Carol Spears wrote:
 i asked because i put instructions of how to do this online.
 
 i have a crontab that runs gimp.
 
 that being said, it has been running for so long now, i have no idea
 what sort of mess it is making, but it was all so easy that it was a
 pleasure to put the instructions online.
 
 Well, i don't know if that is exactly what i meant, but i would still be 
 grateful if you could give me the url to that document.
 Thanks.
 
http://carol.gimp.org/gimp/scripting/routines.html#shell

carol

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp-Python with no ui? (external script)

2006-04-01 Thread Manish Singh
On Sat, Apr 01, 2006 at 02:58:12PM +0200, Ministeyr wrote:
 Manish Singh wrote:
 
  By the way, I thought the batch mode only understood scheme, so it 
 would make the whole thing even more complicated.
 
  One line of scheme to call your python script won't increase the
  complexity appreciably.
 
 The problem is that if i have huge lists and complex python objects in 
 my external scripts, and i want to access them in the gimp's python-fu 
 script, i have to pass them through scheme, and thus it means converting 
 back and forth.
 I will try to adapt with pickle if it works.

You could serialize them to a temporary file, or choose from a number of
IPC methods python ships with. No need to pass stuff like that over the
command line.

How were you planning on doing it via your original though of having
having a gimp_noui anyway? The issues are more or less the same.
 
-Yosh
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp-Python with no ui? (external script)

2006-03-30 Thread Carol Spears
On Thu, Mar 30, 2006 at 03:31:12PM +0200, Ministeyr wrote:
 I need to make an external Python administration script, wich 
 occasionnally uses gimp functionnality (especially to convert to/from 
 xcf files). Is there a way to use this functionnality without starting 
 the ui?
 I need something like that:
 
   import gimp_noui as gimp
   gimp.startgimp()#start the gimp in background process
   pdb.file_load(whatever...)
   #do something here...
   pdb.file_save(whatever...)
   gimp.stopgimp()
 Thanks.

what os will you be using this on?

carol

___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp-Python with no ui? (external script)

2006-03-30 Thread Ministeyr

what os will you be using this on?

carol


I'm developping it for and under a Debian-testing system (on amd k7), 
and plan to use it possibly also on an Ubuntu Linux.

I won't need windows support.


Ministeyr
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer


Re: [Gimp-developer] Gimp-Python with no ui? (external script)

2006-03-30 Thread Manish Singh
On Thu, Mar 30, 2006 at 07:59:08PM +0200, Ministeyr wrote:
 Just write a pygimp script normally, and call it via gimp's batch mode.
 
 -Yosh
 
 I would prefer another solution, since I have some processing to do in 
 the external script and possibly a bunch of data to transfer back and 
 forth, so it would make the script quite complex to have to use the 
 batch interpreter.

Why would it?

 By the way, I thought the batch mode only understood scheme, so it would 
 make the whole thing even more complicated.

One line of scheme to call your python script won't increase the
complexity appreciably.

 I hope there is a simpler solution possible.

Well, it's kind of hacky yes, but it's not *complex*.

If you want something better, why don't you contribute it?

-Yosh
___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer