dallasgroot/Gimp
dallasgroot/Gimp
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Makefile.am removed this file.

Browse source 
2003-02-23  Sven Neumann  <sven@gimp.org>

	* Makefile.am
	* README.perl: removed this file.

	* INSTALL
	* README
	* README.i18n
	* gimp.spec.in: removed traces of gimp-perl and added some
	pointers to the new CVS module.
This commit is contained in:
Sven Neumann 2003-02-23 16:29:30 +00:00 committed by Sven Neumann
parent 4b42b55bf4
commit 7f5054b12f
7 changed files with 71 additions and 365 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
ChangeLog
View file

@ -1,3 +1,14 @@
2003-02-23 Sven Neumann <sven@gimp.org>
* Makefile.am
* README.perl: removed this file.
* INSTALL
* README
* README.i18n
* gimp.spec.in: removed traces of gimp-perl and added some
pointers to the new CVS module.
2003-02-23 Sven Neumann <sven@gimp.org>
* app/gui/convert-dialog.c (convert_to_indexed): set the correct

11
INSTALL
View file

@ -103,10 +103,6 @@ recognizes. These are:
having gimp-1.2 installed. If you want to compile GIMP without
support for printing, use the --disable-print option.
--enable-perl and --disable-perl. The perl extension is currently
disabled since has not yet been updated for gimp-1.3. You can
enforce its build by using the --enable-perl option.
--enable-mp. This options control whether to build GIMP with or without
support for multiple processors. This option is off by default. If
you do have multiply processors and run GIMP with an OS supporting
@ -181,13 +177,6 @@ several reasons why this might fail:
Fix: remove the old libraries and include files.
* The perl extension does not detect all combinations of libraries and
packages it needs to built properly, causing compilation to stop
prematurely.
Fix: use configure with the "--disable-perl" switch or install perl
(version>=5.005) and the Perl-Gtk-interface.
A detailed log of the ./configure output is written to the file
config.log. This may help diagnose problems.

1
Makefile.am
View file

@ -48,7 +48,6 @@ EXTRA_DIST = \
PLUGIN_MAINTAINERS \
README \
README.i18n \
README.perl \
README.win32 \
TODO.xml \
config.h.win32 \

116
README
View file

@ -1,19 +1,20 @@
The GIMP: The GNU Image Manipulation Program
============================================
This is version 1.3, the developers version of The GIMP. Only use it
if you are brave and curious and want to participate development
towards the next stable release version 1.4. This is a developers
version. We know it has bugs and it might not even compile. You have
been warned!
This is version 1.3, the developers version of The GIMP. Only use it if you
are brave and curious and want to participate development towards the next
stable release version 1.4. This is a developers version. We know it has bugs
and it might not even compile. You have been warned!
Some features that were present in GIMP 1.2 are disabled or not even
included in this release. This includes the Perl extension and thus
all the perl plug-ins. The new text tool is only halfway done and
various other tools and functions are broken. Almost everything is under
construction. Don't even think about using this for daily work. If you
are a software distributor, dont' dare to ship this package to innocent
users.
Some features that were present in GIMP 1.2 are disabled or not even included
in this release. The perl bindings as well as all the perl scripts are not any
longer included in this source tree. They have been moved into its own module
called gimp-perl and await being porting to GIMP-1.3 and GTK+-2.0.
The new text tool is only halfway done and various other tools and functions
are broken. Almost everything is under construction. Don't even think about
using this for daily work. If you are a software distributor, dont' dare to
ship this package to innocent users.
For installation instructions, see the file INSTALL.
@ -25,8 +26,8 @@ The GIMP's home page is at:
http://www.gimp.org/
Please be sure to visit this site for information, documentation,
tutorials, news, etc. All things GIMP-ish are available from there.
Please be sure to visit this site for information, documentation, tutorials,
news, etc. All things GIMP-ish are available from there.
The automated plug-in registry is located at:
@ -48,22 +49,21 @@ discussion. There is more info at
https://lists.xcf.berkeley.edu/mailman/listinfo/<listname>
substituting <listname> for "gimp-announce", "gimp-user",
"gimp-win-user", or "gimp-developer" (without the quotes, of course)
depending on the list you want to subscribe to. Links to the mailing
list archives can be found at the same addresses as given above.
substituting <listname> for "gimp-announce", "gimp-user", "gimp-win-user", or
"gimp-developer" (without the quotes, of course) depending on the list you
want to subscribe to. Links to the mailing list archives can be found at the
same addresses as given above.
Gimp-announce is a low-traffic list with announcements about new
releases of GIMP and plug-ins. Gimp-user is a mailing list dedicated
to user problems, hints and tips, discussion of cool effects, etc.
Gimp-developer is oriented to GIMP core and plug-in developers. Most
people will only want to be subscribed to gimp-user. If you want to
help develop The GIMP, the gimp-developer mailing list is a good
starting point.
Gimp-announce is a low-traffic list with announcements about new releases of
GIMP and plug-ins. Gimp-user is a mailing list dedicated to user problems,
hints and tips, discussion of cool effects, etc. Gimp-developer is oriented
to GIMP core and plug-in developers. Most people will only want to be
subscribed to gimp-user. If you want to help develop The GIMP, the
gimp-developer mailing list is a good starting point.
There are two mailing lists dedicated to the Win32 port, "gimpwin-users"
and "gimpwin-dev". Especially the latter also carries traffic about the
GTk+ port to Win32 in general. To subscribe, send an empty message to
There are two mailing lists dedicated to the Win32 port, "gimpwin-users" and
"gimpwin-dev". Especially the latter also carries traffic about the GTk+ port
to Win32 in general. To subscribe, send an empty message to
gimpwin-users-subscribe@egroups.com
or
@ -74,18 +74,17 @@ respectively. You can also use the web interface at
http://www.egroups.com/group/gimpwin-users/ and
http://www.egroups.com/group/gimpwin-dev/
Note that as these mailing lists are hosted on egroups.com, the
messages from the list contain relatively unintrusive and easily
ignored advertisements at the end. But if you are absolutely allergic
to ads, don't subscribe.
Note that as these mailing lists are hosted on egroups.com, the messages from
the list contain relatively unintrusive and easily ignored advertisements at
the end. But if you are absolutely allergic to ads, don't subscribe.
3. IRC
======
And finally, for the real junkies, there is an IRC channel devoted to
the GIMP. On Byxnet (a private mostly-GIMP network) there is #gimp.
Many of the developers hang out there. One of the Byxnet servers are:
And finally, for the real junkies, there is an IRC channel devoted to the
GIMP. On Byxnet (a private mostly-GIMP network) there is #gimp. Many of the
developers hang out there. One of the Byxnet servers are:
irc.gimp.org:6667
@ -93,37 +92,34 @@ Many of the developers hang out there. One of the Byxnet servers are:
4. Customizing
==============
The look of GIMP's interface can be customized like any other GTK app
by editing the ~/.gtkrc file or by using "themes" (ready-made
customizations). For downloadable themes and further details, see
http://gtk.themes.org. Additionally GIMP reads ~/.gimp-1.3/gtkrc so
you can have settings that only apply to The GIMP.
The look of GIMP's interface can be customized like any other GTK app by
editing the ~/.gtkrc file or by using "themes" (ready-made customizations).
For downloadable themes and further details, see http://gtk.themes.org.
Additionally GIMP reads ~/.gimp-1.3/gtkrc so you can have settings that
only apply to The GIMP.
Included is a set of keybindings similar to those in Adobe Photoshop.
You can find them in the ps-menurc file. To use them, copy this file
to ~/.gimp-1.3/menurc. You can also manually change the keybindings to
any of your choice by editing ~/.gimp-1.3/menurc.
Included is a set of keybindings similar to those in Adobe Photoshop. You
can find them in the ps-menurc file. To use them, copy this file to
~/.gimp-1.3/menurc. You can also manually change the keybindings to any of
your choice by editing ~/.gimp-1.3/menurc.
5. Bugs
=======
Since this is a developers version, we are at the moment not really
interested in receiving too many bug-reports. Some parts of the code
are unfinished and under heavy development and we know that.
Bug-reports for incomplete or missing are features are therefore often
not helpful. Instead of filing a bug you should try to contact the
person who is working on this particular part of the program (see the
ChangeLog) or try to fix it yourself. You should report crashes and
other severe bugs at Bugzilla (http://bugzilla.gnome.org/). Your
bug-report needs to provide detailed instruction of how to reproduce
the problem. For reports on crashes, please also include a stack
trace.
Since this is a developers version, we are at the moment not really interested
in receiving too many bug-reports. Some parts of the code are unfinished and
under heavy development and we know that. Bug-reports for incomplete or
missing are features are therefore often not helpful. Instead of filing a bug
you should try to contact the person who is working on this particular part of
the program (see the ChangeLog) or try to fix it yourself. You should report
crashes and other severe bugs at Bugzilla (http://bugzilla.gnome.org/). Your
bug-report needs to provide detailed instruction of how to reproduce the
problem. For reports on crashes, please also include a stack trace.
If you experience crashes whenever you try to start gimp-1.3, you are
most probably using gdkxft or another LD_PRELOAD hack designed for
gtk+-1.2. These hacks will not work with GTK+-2.0 applications like
this version of The GIMP.
If you experience crashes whenever you try to start gimp-1.3, you are most
probably using gdkxft or another LD_PRELOAD hack designed for gtk+-1.2. These
hacks will not work with GTK+-2.0 applications like this version of The GIMP.
Have fun,
@ -133,4 +129,4 @@ Have fun,
Federico Mena
Manish Singh
Sven Neumann
Michael Natterer
Michael Natterer

6
README.i18n
View file

@ -167,10 +167,8 @@ this one may not necessarily fit.
po-script-fu/gimp14-script-fu.pot -- the script-fu scripts
tips/gimp-tips14.pot -- the startup tips
(plug-ins/perl/po/gimp14-perl.pot -- the gimp-perl scripts)
The perl translation is in brackets since gimp-perl is not built at
the moment and it is not sure whether it will be in GIMP-1.4 or not.
If you are looking for the translations of gimp-perl, please note that
gimp-perl has been moved into it's own CVS module called gimp-perl.
When translating menu_paths, please do not translate the name of the
item_factory (that is the one in brackets at the front), e.g.

262
README.perl
View file

@ -1,262 +0,0 @@
NAME
Gimp - Perl extension for writing Gimp Extensions/Plug-ins/Load &
Save-Handlers
SYNOPSIS
my $img = new Image (600, 300, RGB);
my $bg = $img->layer_new(600,300,RGB_IMAGE,"Background",100,NORMAL_MODE);
$img->add_layer($bg, 1);
$img->edit_fill($bg);
$img->display_new;
A complete & documented example script can be found at the end of
this document (search for EXAMPLE).
DOCUMENTATION
The Manpages in html format, the newest version, links and more
information can be found on the gimp-perl homepage, where you
should get an overview over the gimp-perl extension:
http://gimp.pages.de/
-or-
http://www.goof.com/pcg/marc/gimp.html
PREREQUISITES
To install/use this perl extension, you need to have the following
software packages installed (the given order is best):
Perl5.004 (or higher):
While this extension should run fine with older versions (it has
been tested with 5.004_04), I work with Perl5.005 or higher,
which has much more bugs fixed than the old 5.004.
When in doubt, upgrade.
GTK+, the X11 toolkit:
http://www.gtk.org/
ftp://ftp.gimp.org/pub/gtk/
gtk+-1.2 or higher is recommended, but older versions mostly
work (some features not implemented in gtk+-1.0 do not work
properly, of course).
Gtk, the perl extension for the above:
ftp://ftp.gimp.org/pub/gtk/perl/
Gtk-0.6123 (or higher) is recommended. You might encounter some
problems compiling it for Perl5.004 (or any version), in that
case you might want to try the updated gnome-perl version on the
gnome-cvs-server. See the the gimp-perl pages for more info.
The GNU Image Manipulation Program, i.e. The GIMP:
http://www.gimp.org/
ftp://ftp.gimp.org/pub/gimp/
gimp-1.2 (or newer, e.g. CVS or CVS snapshots) is recommended
for full functionality, but any version since 1.0.2 should do,
some features not implemented in 1.0 don't work, though.
PDL, the Perl Data Language
http://www.cpan.org/
Optionally, you can install the PDL module to be able to
manipulate pixel data (or to be able to run the example plug-ins
that do pixel manipulation). PDL is available at any CPAN
mirror, version 1.9906 or higher is recommended. Without PDL,
some plug-ins do not work, and accessing raw image data is
impossible.
INSTALLATION
On unix, you should be able to run "perl Makefile.PL" make, make
test && make install. To get a listing of configuration options,
enter
perl ./Makefile.PL --help
a straight "perl Makefile.PL" should do the job on most systems,
but watch out for warnings. If everything went fine, enter "make",
"make test", "make install".
After installation, these perl plug-ins should be visible from
within the Gimp (and many, many more):
<Toolbox>/Xtns/Perl Control Center
<Toolbox>/Xtns/Perl-Server
<Image>/Filters/Artistic/Windify
<Image>/Filters/Misc/Prepare for GIF
<Image>/Filters/Misc/Webify
If you don't have unix, you can install linux instead
(http://www.linux.org/)
OVERWRITING INSTALL LOCATIONS (PREFIX)
In the rare case that you want to install the Gimp-Perl modules
somewhere else than in the standard location then there is a
standard way to accomplish this.
Usually, you can just use the PREFIX=/path option to the
Makefile.PL, or the other common solution of adding the INST* path
definitions onto the "make install" commandline.
These options are described in the "perldoc ExtUtils::MakeMaker"
manpage.
If you are configuring the gimp-pelr module that comes with the
Gimp sourcetree this won't work. In that case you can set the
environment variable:
PERL_MM_OPT='whatever options you want to pass to MakeMaker'
before running configure. The arguments that you put into that
variable will be passed to the Makefile.PL as if given on the
commandline.
If you are building a slp/deb/rpm/whatever package you usually want
to use the normal prefix, while overwriting the prefix at "make
install" time. In that case, just build gimp-perl (or the whole
gimp) as usual, but instead of just calling "make install", use
something like the following command (this example is for debian):
make prefix=`pwd`/debian/tmp/usr PREFIX=`pwd`/debian/tmp/usr \
install
The lowercase prefix is used by the Gimp, the uppercase PREFIX is
used by perl. Rarely you also want to specifiy manpage directories
etc.. you can also overwrite these (see "man ExtUtils::MakeMaker")
as well, e.g. for debian:
make prefix=`pwd`/debian/tmp/usr PREFIX=`pwd`/debian/tmp/usr \
INSTALLMAN1DIR=`pwd`/debian/tmp/usr/man/man1 \
INSTALLMAN3DIR=`pwd`/debian/tmp/usr/man/man3 \
install
PS: I'm not a debian developer/fan. If at all, I'd recommend
www.stampede.org (since they are using my compiler ;), but the
_best_ thing is DIY.
SUPPORT/MAILING LISTS/MORE INFO
There is a mailinglist for general discussion about Gimp-Perl. To
subscribe, send a mail with the single line
subscribe
to gimp-perl-request@lists.netcentral.net.
If you want to get notified of new versions automatically, send a
mail with the single line:
subscribe notify-gimp
to majordomo@gcc.ml.org.
You can also upload your scripts to the gimp registry at
http://registry.gimp.org/, part of it is dedicated to gimp-perl.
BLURB
Scheme is the crappiest language ever. Have a look at Haskell
(http://www.haskell.org) to see how functional is done right. I am
happy to receive opinions on both languages, don't hesitate to tell
me.
LICENSE
The gimp-perl module is currently available under the GNU Public
License (see COPYING.GPL for details) and the Artistic License (see
COPYING.Artistic for details). Many of the scripts in the example
section follow these rules, but some of them have a different
licensing approach, please consult their source for more info.
THREATS
Future versions of this package might be distributed under the
terms of the GPL only, to be consistent with the rest of the
Gimp. Andreas keeps me from doing this, though.
(c)1998,1999 Marc Lehmann <pcg@goof.com>
EXAMPLE PERL PLUG-IN
To get even more look & feel, here is a complete plug-in source,
its the examples/example-fu.pl script from the distribution.
#!/usr/bin/perl
use Gimp;
use Gimp::Fu;
register "gimp_fu_example_script", # fill in a function name
"A non-working example of Gimp::Fu usage", # and a short description,
"Just a starting point to derive new ". # a (possibly multiline) help text
"scripts. Always remember to put a long".
"help message here!",
"Marc Lehmann", # don't forget your name (author)
"(c) 1998, 1999 Marc Lehmann", # and your copyright!
"19990316", # the date this script was written
"<Toolbox>/Xtns/Gimp::Fu Example", # the menu path
"RGB*, GRAYA", # image types to accept (RGB, RGAB amnd GRAYA)
[
# argument type, switch name , a short description , default value, extra arguments
[PF_SLIDER , "width" , "The image width" , 360, [300, 500]],
[PF_SPINNER , "height" , "The image height" , 100, [100, 200]],
[PF_STRING , "text" , "The Message" , "example text"],
[PF_INT , "bordersize" , "The bordersize" , 10],
[PF_FLOAT , "borderwidth" , "The borderwidth" , 1/5],
[PF_FONT , "font" , "The Font Family" ],
[PF_COLOUR , "text_colour" , "The (foreground) text colour", [10,10,10]],
[PF_COLOUR , "bg_colour" , "The background colour" , "#ff8000"],
[PF_TOGGLE , "ignore_cols" , "Ignore colours" , 0],
[PF_IMAGE , "extra_image" , "An additonal picture to ignore"],
[PF_DRAWABLE , "extra_draw" , "Somehting to ignroe as well" ],
[PF_RADIO , "type" , "The effect type" , 0, [small => 0, large => 1]],
[PF_BRUSH , "a_brush" , "An unused brush" ],
[PF_PATTERN , "a_pattern" , "An unused pattern" ],
[PF_GRADIENT , "a_gradients" , "An unused gradients" ],
],
sub {
# now do sth. useful with the garbage we got ;)
my($width,$height,$text,$font,$fg,$bg,$ignore,$brush,$pattern,$gradient)=@_;
# set tracing
Gimp::set_trace(TRACE_ALL);
my $img=new Image($width,$height,RGB);
# put an undo group around any modifications, so that
# they can be undone in one step. The eval shields against
# gimp-1.0, which does not have this function.
eval { $img->undo_push_group_start };
my $l=new Layer($img,$width,$height,RGB,"Background",100,NORMAL_MODE);
$l->add_layer(0);
# now a few syntax examples
Palette->set_foreground($fg) unless $ignore;
Palette->set_background($bg) unless $ignore;
fill $l BG_IMAGE_FILL;
# the next function only works in gimp-1.2
$text_layer=$img->text_fontname(-1,10,10,$text,5,1,xlfd_size($font),$font);
gimp_palette_set_foreground("green");
# close the undo push group
eval { $img->undo_push_group_end };
$img; # return the image, or an empty list, i.e. ()
};
exit main;

29
gimp.spec.in
View file

@ -58,15 +58,6 @@ Install gimp-devel if you're going to create plug-ins and/or
extensions for the GIMP. You'll also need to install gimp-limpgimp
and gimp, and you may want to install gimp-data-extras.
%package perl
Summary: GIMP perl extensions and plugins.
Group: Applications/Graphics
Requires: gimp
Requires: perl
%description perl
The gimp-perl package contains all the perl extensions and perl plugins.
%prep
%setup -q
@ -104,24 +95,11 @@ if [ -d $RPM_BUILD_ROOT/%{prefix}/man ]; then
find $RPM_BUILD_ROOT/%{prefix}/man -type f -exec gzip -9nf {} \;
fi
#
# This perl madness will drive me batty
#
eval perl '-V:archname'
find $RPM_BUILD_ROOT/%{prefix}/lib/perl5 -type f -print | sed "s@^$RPM_BUILD_ROOT@@g" | grep -v perllocal.pod > gimp-perl
#
# Plugins and modules change often (grab the executeable ones)
#
echo "%defattr (0555, bin, bin)" > gimp-plugin-files
find $RPM_BUILD_ROOT/%{prefix}/lib/gimp/%{subver} -type f -exec file {} \; | grep -v perl | cut -d':' -f 1 | sed "s@^$RPM_BUILD_ROOT@@g" >>gimp-plugin-files
#
# Now pull the perl ones out.
#
echo "%defattr (0555, bin, bin)" > gimp-perl-plugin-files
echo "%dir %{prefix}/lib/gimp/%{subver}/plug-ins" >> gimp-perl-plugin-files
find $RPM_BUILD_ROOT/%{prefix}/lib/gimp/%{subver} -type f -exec file {} \; | grep perl | cut -d':' -f 1 | sed "s@^$RPM_BUILD_ROOT@@g" >>gimp-perl-plugin-files
find $RPM_BUILD_ROOT/%{prefix}/lib/gimp/%{subver} -type f -exec file {} \; | cut -d':' -f 1 | sed "s@^$RPM_BUILD_ROOT@@g" >>gimp-plugin-files
#
# Auto detect the lang files.
@ -149,7 +127,6 @@ done
# Build the master filelists generated from the above mess.
#
cat gimp-plugin-files gimp-all.lang gimp-tips-files > gimp.files
cat gimp-perl gimp-perl-plugin-files > gimp-perl-files
%clean
[ -n "$RPM_BUILD_ROOT" -a "$RPM_BUILD_ROOT" != / ] && rm -rf $RPM_BUILD_ROOT
@ -160,7 +137,7 @@ cat gimp-perl gimp-perl-plugin-files > gimp-perl-files
%files -f gimp.files
%attr (0555, bin, man) %doc AUTHORS COPYING ChangeLog MAINTAINERS NEWS README TODO
%attr (0555, bin, man) %doc docs/*.txt docs/*.eps ABOUT-NLS README.i18n README.perl README.win32 TODO
%attr (0555, bin, man) %doc docs/*.txt docs/*.eps ABOUT-NLS README.i18n README.win32 TODO
%defattr (0444, bin, bin, 0555)
%dir %{prefix}/share/gimp/%{subver}
%dir %{prefix}/share/gimp/%{subver}/tips
@ -231,8 +208,6 @@ cat gimp-perl gimp-perl-plugin-files > gimp-perl-files
%{prefix}/include/gck/
%{prefix}/man/man1/gimptool.1*
%files perl -f gimp-perl-files
%changelog
* Fri Apr 14 2000 Matt Wilson <msw@redhat.com>
- include subdirs in the help find