*** empty log message ***

This commit is contained in:
Marc Lehmann 1999-05-31 22:25:40 +00:00
parent 33ed6263d5
commit 98dcea4838
3 changed files with 44 additions and 27 deletions

View File

@ -1,3 +1,9 @@
Mon May 31 06:48:56 CEST 1999 Marc Lehmann <pcg@goof.com>
* configure.in, README: Set the PREFIX env. var. to the value of
--enable-perl.
* docs/parasites.txt: updated.
1999-05-31 Michael Natterer <mitschel@cs.tu-berlin.de>
* app/info_dialog.c

View File

@ -526,7 +526,8 @@ if test $ac_cv_path_LPC_COMMAND != ":"; then
fi
dnl This is for the gimp-perl plug-in
AC_ARG_ENABLE(perl, [ --disable-perl do not build perl extension [by default enabled]])
AC_ARG_ENABLE(perl, [ --disable-perl do not build perl extension [by default enabled]
--enable-perl[=prefix] use specified prefix for perl (see INSTALL)])
AC_ARG_WITH(pdbgen, [ --with-pdbgen use 'pdbgen' code generation tool],
,
@ -562,9 +563,12 @@ if test "x$enable_perl" != xno; then
sinclude(plug-ins/perl/etc/configure.frag)
dnl we ignore prefix
if test -n "$enable_perl" && test "$enable_perl" != xyes; then
perl_prefix="PREFIX=$enable_perl"
fi
cat >plug-ins/perl/config.status <<EOF
echo invoking perl for configuration...
$PERL Makefile.PL --writemakefile
$PERL Makefile.PL --writemakefile $perl_prefix
EOF
GIMP_PERL=perl
else

View File

@ -1,5 +1,5 @@
PARASITE REGISTRY - 1998/10/09
PARASITE REGISTRY - 1999-05-31
=================
This document is designed for the convenience of GIMP developers.
@ -11,43 +11,50 @@ It does not need to concern users.
------------------------------------------------------------------
*** PREFIXES:
*** NAMESPACE
Plug-in-specific data should be prefixed by the plug-in function name and
a slash, i.e. private data of plug_in_displace should be named like:
plug_in_displace/data1
plug_in_displace/data2
etc.
Global data follows no strict rules.
------------------------------------------------------------------
*** KNOWN PREFIXES:
"tiff" : The standard GIMP TIFF plugin
"jpeg" : The standard GIMP JPEG plugin
"gimp" : For common and standard parasites
"perl-fu" : Internal data by the Gimp-perl interface
------------------------------------------------------------------
*** PARASITES:
*** KNOWN PARASITES:
"gimp-comment" : Standard GIF-style comments. This parasite is
human-readable text in unspecified 8-bit ASCII. It
includes a trailing \0 string terminator. The size
of the parasite data may not exceed 241 bytes. This
parasite attaches to images only. It is persistent,
which means it is saved in XCF files.
"gimp-comment" (IMAGE, PERSISTENT)
Standard GIF-style comments. This parasite is human-readable text
in unspecified 8-bit ASCII. It includes a trailing \0 string
terminator. The size of the parasite data may not exceed 241
bytes.
"tiff-save-options" : The TiffSaveVals structure from the TIFF plugin.
This parasite attaches to images only. It is not
persistent.
"tiff-save-options" (IMAGE)
The TiffSaveVals structure from the TIFF plugin.
"jpeg-save-options" : The JpegSaveVals structure from the JPEG plugin.
This parasite attaches to images only. It is not
persistent.
"jpeg-save-options" (IMAGE)
The JpegSaveVals structure from the JPEG plugin.
"perl-fu-last-vals-<plug-in>" : The Gimp::Fu module might store the
arguments of the last plug-in invocation. It is usually
attached to images, but might also be found globally. It
might also be persistent. The data format is either
pure character data (Data::Dumper) or a serialized data
stream created by Storable::nfreeze.
"<plug-in>/_fu_data" (GLOBAL, IMAGE, DRAWABLE, PERSISTENT)
The Gimp::Fu module might store the arguments of the last plug-in
invocation. It is usually attached to images, but might also
be found globally. The data format is either pure character
data (Data::Dumper) or a serialized data stream created by
Storable::nfreeze.
------------------------------------------------------------------
*** FORMAT:
*** PARASITE FORMAT:
The parasite data format is not rigidly specified. For non-persistant
parasites you are entirely free, as the parasite data does not survive the
@ -90,7 +97,7 @@ non-persistant data might be fine as well):
One way out around this is to prefix your data with a version identifier
(remember to use a guchar, i.e. something without endian-ness problems).
Depending on that (remember to skip it before deserializing)
Remember to skip it before deserializing.
Another very easy way is to add a version tag to your parasite name,
i.e. "foo-bar-v1", "foo-bar-v2". Your plug-in could then check for older