0c922cd3b0
1999-11-14 Michael Natterer <mitch@gimp.org> * app/airbrush.c * app/apptypes.h * app/brushes_cmds.c * tools/pdbgen/pdb/brushes.pdb * app/bucket_fill.c * app/clone.c * app/gimpbrushpipe.c * app/paint_core.c * app/patterns.h * app/patterns_cmds.c * tools/pdbgen/pdb/patterns.pdb: removed the GimpBrushP and GPatternP types and use ordinary pointers instead. The following stuff makes the "no_data" behaviour consistent. As a side-effect it should make the gimp work when there are _really_ no brushes/patterns/gradients. * app/brush_select.c * app/pattern_select.c: set the initial brush/pattern name to "No Brushes/Patterns available" instead of "Active". * app/devices.c: set the device contexts' brush/pattern/gradient names if we started with no_data, so we find them on refresh. * app/gimpbrushlist.c: set the name of the standard_brush to "Standard". * app/gimpcontext.c: don't replace the current brush/pattern/gradient's name if the new one to be set is the standard one. Together with the change in devices.c, this ensures that we get what is set in devicerc. Minor fixes. * app/gradient.c: changed gradients_init() to work like the other data init functions. Only insert a default gradient in the gradients list when the editor is opened (this means that the gradients now behave like brushes/patterns when we start with "no_data"). New function gradient_update() avoids tons of useless redraws of all clist gradient previews whenever the gradient editor wants to update it's large preview. * app/gradient_select.c: don't segfault when the user tries to drag from an empty gradient list. * app/patterns.c: set the index of the standard_pattern to -1 to indicate that it's not part of the pattern list.
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'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.
We have several mailing lists dedicated to GIMP user and development
discussion. To subscribe, send mail to
majordomo@scam.xcf.berkeley.edu
and in the body of the message put
subscribe <list-name> your@email.address
substituting <list-name> for "gimp-user" 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.findmail.com/listsaver/gimp-developer/
http://www.findmail.com/listsaver/gimp-user/
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.
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. Some of the Byxnet servers are:
irc.gimp.org:6667
You can customize the look of the interface quite a bit my editing the
~/.gimp/gtkrc file. A sample file, gtkrc.forest, is included (Thanks to
Tuomas Kuosmanen)
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/menurc
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 has already did (check the http://www.wilberworks.com/bugs.cgi for
this).
Have fun,
Spencer Kimball
Peter Mattis
Federico Mena
Manish Singh