9c6b0b0c33
2000-05-21 Michael Natterer <mitch@gimp.org> These changes enable help support for 3rd party plug-ins which install their help files outside GIMP's main help dir. Instead of calling gimp_help(), gimp_plugin_help_func() etc., all help callbacks now have to call gimp_standard_help_func() which has different implementations in the app and in libgimp. There is a new function gimp_plugin_help_register() which can be called during plug-in query. plug_in.c keeps a list of executable_name/help_path pairs. Plug-ins have to pass their exec. name to gimp_help() which uses the list to find the plug-in's help directory. * app/gimphelp.[ch]: gimp_help() now takes a help_path parameter. help_path == NULL means the standard help directory. Various changes to pass the help_path to the help browser. * app/gimprc.c: save the plug-in's help_path in the pluginrc file. * app/menus.c: ugly hack to enable help_paths in the "F1" callback. * app/plug_in.[ch]: many help_path related changes. Use g_basename() instead of strrchr(str,G_DIR_SEPARATOR), cosmetic cleanups. * app/internal_procs.c * app/gimphelp_cmds.c * tools/pdbgen/pdb/gimphelp.pdb: new procedure gimp_plugin_help_register(). gimp_help() takes a second parameter which is the executable name (not the help_path). * app/color_notebook.c * app/commands.c * app/lc_dialog.c * app/preferences_dialog.c * app/tools.c: call gimp_standard_help_func() instead of gimp_help(). * libgimp/gimp.c: new function gimp_get_progname() which returns the full path of the plug-in's executable. * libgimp/gimp.h: export the new function, removed gimp_plugin_help_func(), gimp_help() takes the executable name as second parameter. * libgimp/gimpcompat.h: added gimp_plugin_help_func(). * libgimp/gimphelp.c: a wrapper for gimp_plugin_help_register(), changed the calls to gimp_help. * libgimp/gimphelpui.[ch]: call gimp_standard_help_func() instead of gimp_help(). * plug-ins/helpbrowser/helpbrowser.c: now called with an additional help_path parameter. Various changes to enable help_path != gimp_standard_help_path. Unrelated stuff: * app/batch.h: added missing GPL header. * app/gimpunit.c: had a LGPL header, merged some fprintf's into one call. * app/procedural_db.[ch]: cosmetic: g* types, s/g_malloc/g_new/, prototypes, indentation. * app/resize.c: use less packing widgets. didn't find the "offset" redraw bug :(
The GIMP: The GNU Image Manipulation Program
============================================
This is an unstable release of the GIMP, intended for developers only.
For production use, please use the 1.0.x series.
The GIMP is designed to be a professional image manipulation program
for both print and on-line based outputs.
For installation instructions, see the file INSTALL.
1. Web Resources
================
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.
The automated plug-in registry is located at:
http://registry.gimp.org/
There you can get the latest versions of plug-ins using a convenient
forms-based interface.
The latest version of The GIMP can be found at:
http://www.gimp.org/download/
2. Mailing Lists
================
We have several mailing lists dedicated to GIMP user and development
discussion. To subscribe, send an empty message to
<listname>-subscribe@xcf.berkeley.edu
substituting <listname> for "gimp-user", "gimp-announce" or
"gimp-developer" (without the quotes, of course) depending on the list you
want to subscribe to. The mailing list archives can be found at:
http://www.egroups.com/messages/gimp-developer/
http://www.egroups.com/messages/gimp-user/
Gimp-user is a mailing list dedicated to user problems, hints and
tips, discussion of cool effects, etc. Gimp-announce is a low-traffic list
with announcements about new releases of GIMP and plug-ins. 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
gimpwin-users-subscribe@egroups.com
or
gimpwin-dev-subscribe@egroups.com
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.
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:
irc.gimp.org:6667
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.1/gtkrc so you
can have settings that only apply to The GIMP.
Included is a set of keybindings similar to those in Adobe Photoshop (tm).
You can find them in the ps-menurc file. To use them, copy this file to
~/.gimp-1.1/menurc. You can also manually change the keybindings to any of
your choice by editing ~/.gimp-1.1/menurc.
5. Bugs
=======
We sincerely hope you enjoy the program. Please report problems to
bugs@gimp.org. Before reporting a problem, you may want to see if someone
else did already - check http://bugs.gnome.org/db/pa/lgimp.html for this.
Have fun,
Spencer Kimball
Peter Mattis
Federico Mena
Manish Singh