Re: [Gimp-developer] undoo history and automatic script creation
Hi, On Wed, 2006-10-04 at 18:07 -0700, Saul Goode wrote: I am unaware of any PDB function that would permit and would be interested in any input as to how this might be accomplished -- including which code in the core I might avail if I were to create such a PDB function. The undo functionality is intentionally not exported to the PDB because it would be too easy for scripts and plug-ins to mess with the fragile internals of it then. What you described as a possible use case seems to be a very special case and I expect that anyone but the script author himself would only find it confusing. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Pygimp plugin built and installed on Win, but not accessible
Hi, On Thu, 2006-10-05 at 15:54 +1000, Williams, Andrew wrote: With some difficulty I built Gimp 2.3.7 with Python using MinGW on Win XP. Make and make install completed without error. Why would you waste your time building such an outdated version of GIMP 2.3? 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
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] Script-Fu procedure blurb review
Hi, we still need the Script-Fu blurbs reviewed for GIMP 2.4. http://bugzilla.gnome.org/show_bug.cgi?id=351283 Might you perhaps find time to finish this task anytime soon? Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Pygimp plugin built and installed on Win, but not accessible
On 05.10.2006 07:54, Williams, Andrew wrote: With some difficulty I built Gimp 2.3.7 with Python using MinGW on Win XP. Make and make install completed without error. Gimp starts, but there is no Python in the Toolbars/Xtns menu (or any others); Script explorer shows NO python scrips. You need to make GLib's g_file_test() aware of additional 'executables' by adding .PY to the PATHEXT environment variable. See: http://developer.gnome.org/doc/API/2.0/glib/glib-File-Utilities.html#g-file-test I did NOT disable-python. My python 2.4.2 has all the +gtk* installs. The gimp python plugin files all appear to be installed correctly. There are no startup error messages. (And I can import gimp from python.) (Also, my \msys\local\lib\gimp\2.0\environ\pygimp.env and ..\interp\pygimp.interp appear to be ok.) Using the prebuilt Python 2.4 may be a problem as well cause it links with a newer C-runtime than gtk+ (msvcr71.dll vs. msvcrt.dll). I'm not sure if mixing runtimes is fatal for gimp python plug-ins, but at least when embedding Python in Dia this is definitely a problem. See also: http://mail.gnome.org/archives/dia-list/2006-September/msg00045.html Hans Hans at Breuer dot Org --- Tell me what you need, and I'll tell you how to get along without it.-- Dilbert ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp python
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] Pygimp plugin built and installed on Win, but not accessible
On Thursday, October 5, 2006, 8:32:46, Hans Breuer wrote: On 05.10.2006 07:54, Williams, Andrew wrote: With some difficulty I built Gimp 2.3.7 with Python using MinGW on Win XP. Make and make install completed without error. Gimp starts, but there is no Python in the Toolbars/Xtns menu (or any others); Script explorer shows NO python scrips. You need to make GLib's g_file_test() aware of additional 'executables' by adding .PY to the PATHEXT environment variable. See: http://developer.gnome.org/doc/API/2.0/glib/glib-File-Utilities.html#g-file-test Actually, with GIMP, you just need to edit GIMP-2.0\lib\gimp\2.0\interpreters\pygimp.interp to contain something like this: python=R:\Python24\pythonw.exe /usr/bin/python=R:\Python24\pythonw.exe :Python:E::py::python: (the 2.3 installer generates this file automatically) Using the prebuilt Python 2.4 may be a problem as well cause it links with a newer C-runtime than gtk+ (msvcr71.dll vs. msvcrt.dll). I'm not sure if mixing runtimes is fatal for gimp python plug-ins, but at least when embedding Python in Dia this is definitely a problem. See also: http://mail.gnome.org/archives/dia-list/2006-September/msg00045.html I build GIMP with Python 2.4, and as far as I can see, it works. -- Jernej Simonèiè http://deepthought.ena.si/ If not controlled, work will flow to the competent man until he submerges. -- Boyle's Tenth Law ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] Switch to Tiny-Fu, end of Script-Fu maintenance?
Since last week, Tiny-Fu is able to run many of the old Script-Fu scripts unmodified: it reads files with the *.scm extension and uses the script-fu-* namespace so that it can process the calls to script-fu-register. I tested Tiny-Fu with several third-party scripts or scripts that are not in the gimp module (e.g., scripts from gimp-gap). I tried a few dozen scripts written for GIMP 2.0 and 2.2, and most of them ran without problems: there were no difference when the scripts were executed with the old Script-Fu interpreter (siod) or with the new Tiny-Fu interpreter (tinyscheme). I only got problems in a couple of scripts that were not declaring variables correctly or were incorrectly mixing the scope of some variables (global/local). For example, this occured in the smart remove object script that came with with the resynthesizer plug-in. But most of the scripts worked fine with Tiny-Fu. In fact, some of them even worked better: for example, Script-Fu's text circle had problems processing text containing foreign characters, while Tiny-Fu processes these characters without problems. Besides these improvements, the main visible difference is that Tiny-Fu registers some menu entries using the name Tiny-Fu instead of Script-Fu. For example: Xtns - Tiny-Fu - Tiny-Fu Console. However, even that could be changed easily if most developers or documenters prefer to keep the old name for historical reasons. From my point of view, Tiny-Fu is now ready to replace Script-Fu and I would like to encourage everybody to make the switch so that we can fix any remaining bugs. Considering that Tiny-Fu solves some real problems (i18n), the sooner we can do the switch, the better. Unless anyone objects, I would like to commit a trivial patch tomorrow that disables Script-Fu by default in configure.in. It will still be possible to use the old interpreter by using --enable-script-fu explicitely, but otherwise Script-Fu should be considered as obsolete. -Raphaël ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Script-Fu procedure blurb review
we still need the Script-Fu blurbs reviewed for GIMP 2.4. http://bugzilla.gnome.org/show_bug.cgi?id=351283 Might you perhaps find time to finish this task anytime soon? I have submitted a patch which hopefully will be close to what you are expecting. It is amazing what you can accomplish if you do not care who gets the credit. -- Harry S. Truman ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Switch to Tiny-Fu, end of Script-Fu maintenance?
Hi, On Thu, 2006-10-05 at 10:10 +0200, Raphaël Quinet wrote: From my point of view, Tiny-Fu is now ready to replace Script-Fu and I would like to encourage everybody to make the switch so that we can fix any remaining bugs. Considering that Tiny-Fu solves some real problems (i18n), the sooner we can do the switch, the better. First of all, I would like to hear Kevin on this. I have asked him to tell us about his goals for Tiny-Fu and in order to evaluate this question, we absolutely need to know what the goals are. Then, I would suggest that instead of ending maintainance of Script-Fu that we switch the Scheme interpreter in Script-Fu to tiny-scheme. Instead of removing our only platform independent language binding, we should apply the changes that Kevin has done in the gimp-tiny-fu module to the plug-ins/script-fu directory in the GIMP tree. This should be a relatively small change since it only involves replacing the Scheme interpreter. The scripts itself and probably most of the UI code can be left untouched. Development on Script-Fu can then continue as usual and hopefully under the lead of Kevin and the tiny-fu CVS module has fulfilled its role and can be declared as merged and closed. Unless anyone objects, I would like to commit a trivial patch tomorrow that disables Script-Fu by default in configure.in. It will still be possible to use the old interpreter by using --enable-script-fu explicitely, but otherwise Script-Fu should be considered as obsolete. Definitely not. Not unless we have discussed this. 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
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] Switch to Tiny-Fu, end of Script-Fu maintenance?
Unless anyone objects, I would like to commit a trivial patch tomorrow that disables Script-Fu by default in configure.in. It will still be possible to use the old interpreter by using --enable-script-fu explicitely, but otherwise Script-Fu should be considered as obsolete. I should like to try out Tiny-fu on its own but I have been unable to compile the GIMP without Script-fu. I have performed an uninstall, make clean, and configured with the --disable-script-fu but SIOD is still installed. Could you shed any light on what I am doing wrong? It is amazing what you can accomplish if you do not care who gets the credit. -- Harry S. Truman ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
