From 309146d1cb5eb4a4201f058640c43b5009b335c5 Mon Sep 17 00:00:00 2001 From: Sven Neumann Date: Wed, 6 Jun 2007 09:21:42 +0000 Subject: [PATCH] reverted the change here. This document only has historical value and must 2007-06-06 Sven Neumann * papers/script-fu/script-fu.tex: reverted the change here. This document only has historical value and must not be changed. svn path=/trunk/; revision=22717 --- docs/papers/script-fu/script-fu.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/papers/script-fu/script-fu.tex b/docs/papers/script-fu/script-fu.tex index f2d385584b..ef7c730733 100644 --- a/docs/papers/script-fu/script-fu.tex +++ b/docs/papers/script-fu/script-fu.tex @@ -795,12 +795,12 @@ through extension modules: independent applications which implement additional features and then make them available to the main application. -GIMP and its extensions communicate by invoking commands from a +The GIMP and its extensions communicate by invoking commands from a database of procedures. Procedures are pieces of functionality provided by GIMP, its plug-ins, and its extensions. Procedures take as input a list of arguments, execute based on the values of those arguments, and finally return a list of values. There are procedures -for every piece of internal functionality in GIMP as well as for +for every piece of internal functionality in the GIMP as well as for every plug-in written to date. In total, there are over 275 procedures stored in GIMP's ``procedural database''. The following are examples of procedures called by the simple script from Appendix A: