mirror of
https://gitlab.gnome.org/GNOME/gimp
synced 2024-10-21 03:52:33 +00:00
ef751a454d
2000-04-30 Michael Natterer <mitch@gimp.org> * gimprc.in * app/gimprc.[ch]: replaced "color-cube" by "min-colors". * app/app_procs.c: read unitrc/gimprc before displaying the splash. * app/colormaps.c: set min_colors and install_cmap before initializing GdkRGB. * app/gimprc.[ch] * app/gimpunit.c: don't call the splash's progress_update function. * app/plug_in.c: pass min_colors instead of color_cube to plugins. * app/preferences_dialog.c: widget for min_colors. * libgimp/gimp.[ch]: s/color_cube/min_colors/ but left gimp_color_cube() there for source level compatibility. * libgimp/gimpprotocol.[ch]: changed the GPConfig message accordinly and increased the gimp protocol version number because the change breaks binary compatibility. Also actually pass the use_xshm variable over the wire (was only in the GPConfig struct before). Was it the right thing to do to increase the version number?? * libgimp/gimpui.c (gimp_ui_init): use the same code as the app for initializing GdkRGB. Never explicitly activate Gdk's SHM usage (only switch it off). * app/main.c * libgimp/gimp.c: reverted the handling of all signals except SIGCHLD back to plain old signal() because those signals are fatal anyway and sigaction() as used by gimp_signal_*() made debugging (stacktrace) impossible. * plug-ins/AlienMap/AlienMap.c * plug-ins/AlienMap2/AlienMap2.c * plug-ins/FractalExplorer/Dialogs.c * plug-ins/bmp/bmp.c * plug-ins/borderaverage/borderaverage.c * plug-ins/dbbrowser/dbbrowser.c * plug-ins/faxg3/faxg3.c * plug-ins/fits/fits.c * plug-ins/flame/flame.c * plug-ins/fp/fp.c * plug-ins/fp/fp_gtk.c * plug-ins/gdyntext/Makefile.am * plug-ins/gdyntext/gdyntext_ui.c * plug-ins/gfig/gfig.c * plug-ins/gflare/gflare.c * plug-ins/gfli/gfli.c * plug-ins/gimpressionist/gimpressionist.c * plug-ins/helpbrowser/helpbrowser.c * plug-ins/ifscompose/ifscompose.c * plug-ins/imagemap/Makefile.am * plug-ins/imagemap/imap_main.c * plug-ins/maze/maze_face.c * plug-ins/mosaic/mosaic.c * plug-ins/pagecurl/pagecurl.c * plug-ins/print/print.c * plug-ins/rcm/rcm_dialog.c * plug-ins/script-fu/script-fu-console.c * plug-ins/script-fu/script-fu-scripts.c * plug-ins/script-fu/script-fu-server.c * plug-ins/sel2path/Makefile.am * plug-ins/sel2path/sel2path.c * plug-ins/sgi/sgi.c * plug-ins/sinus/sinus.c * plug-ins/struc/struc.c * plug-ins/webbrowser/webbrowser.c * plug-ins/winsnap/winsnap.c * plug-ins/xjt/xjt.c: use gimp_ui_init(). * plug-ins/Lighting/lighting_ui.c * plug-ins/MapObject/mapobject_ui.c: only switch Gdk SHM usage off, never on. Don't use gimp_ui_init() here because of libgck. |
||
---|---|---|
.. | ||
.cvsignore | ||
ifscompose.c | ||
ifscompose.h | ||
ifscompose_storage.c | ||
ifscompose_utils.c | ||
Makefile.am | ||
README.ifscompose |
IfsCompose-0.6.1 ---------------- IfsCompose is a plug-in for the GIMP that allows the creation of Iterated Function System fractals by direct manipulation onscreen of the component transforms. Although v0.6.1 is fairly full featured, it is still lacking some essentials. Most importantly, it is not yet possible to save fractals in unrendered form for future modification. The rendering code could also use some more work. IFS Fractals ------------ You may be familiar with IFS's from the screen hack 'Flame'. They are also the basis of fractal image compression. For a brief introduction to IFS's see Foley and van Dam, et al,. _Computer Graphics, Principles and Practice_, 2nd Ed., (Addison Wesley, 1990). The standard references in the field are Michael Barnsley's books (though I haven't looked at them yet): M. Barnsley, _Fractals Everywhere_, Academic Press Inc., 1988. M. Barnsley and L. Hurd, _Fractal Image Compression_, Jones and Bartlett. Briefly, you take a point and repeatedly apply one of a set of transformations to it, choosing randomly between them, and plot the point at each step. An interesting result (the Collage Theorem) says that if you can find a set of transformations that break up an image into smaller copies of itself, then the resulting fractal exactly reproduces the original image. For example, here is a classic image of a leaf and the same image with the four component transforms colored distinctively. But the best way to appreciate this may to install this program and try it out. I've extended the basic concept as found in Foley and van Dam to include transformations in color space as well as in real space. Installation ------------ The included Makefile should work with minor modifications on most systems if you have installed Gimp normally. Put the resulting binary in ~/.gimp/plug-ins or the system-wide plug-ins directory. The included files gtkaspectframe.c/.h implement a modified frame widget that guarantees that the aspect ratio of the child widget remains constant when the parent is resized. It's sort of specialized, but if you think it would be useful for other purposes, let me know and I'll lobby for its inclusion in the standard gtk. Use --- The interface is somewhat complex and it may take you a little while to get the hang of it. (There are 19 parameters for each transformation in your fractal, after all). The best way to learn is probably to start by making small changes, and seeing what they do. Click on the transformations (represented by polygons) in the design window to manipulate them interactively. Button-1: rotate/scale Button-2: distort Button-3: move If you hold down shift while clicking, you can select multiple polygons to apply the transformation to. Try not to click too near the center of a polygon, as this will amplify your actions. Note that if you render onto an image with an alpha channel, the background will be transparent (very useful for compositing several fractals), otherwise the background will be the current background. There is a tutorial and some example images at: http://www.msc.cornell.edu/~otaylor/plug-ins/ifscompose.html Have fun! Owen Taylor owt1@cornell.edu