mirror of
https://gitlab.gnome.org/GNOME/gimp
synced 2024-10-21 03:52:33 +00:00
b10adabb5e
2005-09-09 Michael Natterer <mitch@gimp.org> Added parent window API to the GimpProgress interface and to the libgimp progress stuff. Might look strange, but does the right thing in almost all cases (image window, file dialog, script-fu dialog etc). Fixes bug #62988. * app/core/gimpprogress.[ch]: added GimpProgress::get_window() which should return a toplevel window ID if the progress is in a window that wants to be the transient parent of plug-in dialogs. * app/widgets/gimpwidgets-utils.[ch] (gimp_window_get_native): new function which returns the window handle of a GtkWindow's GdkWindow. * app/widgets/gimpfiledialog.c: implement ::get_window(). * app/display/gimpdisplay.[ch]: ditto. Removed window handle API. * app/gui/gui-vtable.c: changed accordingly. * libgimpbase/gimpbaseenums.[ch] (enum GimpProgressCommand): added GIMP_PROGRESS_COMMAND_GET_WINDOW. * app/plug-in/plug-in-progress.[ch] (plug_in_progress_get_window): new function. Also renamed some functions to match the GimpProgress interface, and not the legacy PDB procedure names. * tools/pdbgen/pdb/progress.pdb * app/core/gimppdbprogress.c: implement get_window() on both sides of the wire, keeping backward compatibility (hopefully). * libgimp/gimpprogress.[ch]: deprecated gimp_progress_install() and added gimp_progress_install_vtable() which takes a vtable with padding to be extensible. Added get_window() vtable entry and dispatch it accordingly. Also added pulse() which was implemented in a hackish way before. Everything is of course backward compatible. * libgimp/gimpprogressbar.c: inmplement the get_window() stuff so a plug-in dialog containing a progress can be the transient parent of another dialog in another plug-in. * libgimp/gimpui.[ch] (gimp_ui_get_progress_window): new function which returns a foreign GdkWindow of this plug-ins progress window. Renamed gimp_window_set_transient_for_default_display() to gimp_window_set_transient() and make it use the progress' window handle instead of the display's (which is the right thing to do in almost all cases). * libgimp/gimp.def * libgimp/gimpui.def: add the new functions. * tools/pdbgen/enums.pl * app/pdb/internal_procs.c * app/pdb/progress_cmds.c * libgimp/gimpprogress_pdb.[ch]: regenerated. * libgimp/gimpexport.c * plug-ins/*/*.c: follow API change. |
||
|---|---|---|
| app | ||
| cursors | ||
| data | ||
| desktop | ||
| devel-docs | ||
| docs | ||
| etc | ||
| libgimp | ||
| libgimpbase | ||
| libgimpcolor | ||
| libgimpconfig | ||
| libgimpmath | ||
| libgimpmodule | ||
| libgimpthumb | ||
| libgimpwidgets | ||
| m4macros | ||
| menus | ||
| modules | ||
| plug-ins | ||
| po | ||
| po-libgimp | ||
| po-plug-ins | ||
| po-script-fu | ||
| po-tips | ||
| regexrepl | ||
| themes | ||
| tools | ||
| .cvsignore | ||
| acinclude.m4 | ||
| AUTHORS | ||
| authors.dtd | ||
| authors.xml | ||
| authors.xsl | ||
| autogen.sh | ||
| ChangeLog | ||
| ChangeLog.pre-1-0 | ||
| ChangeLog.pre-1-2 | ||
| ChangeLog.pre-2-0 | ||
| ChangeLog.pre-2-2 | ||
| config.h.in | ||
| config.h.win32 | ||
| configure.in | ||
| COPYING | ||
| gimp-zip.in | ||
| gimp.pc.in | ||
| gimpdefs.msc | ||
| gimpthumb.pc.in | ||
| gimptool-2.0.in | ||
| gimptool-win32.c.in | ||
| gimpui.pc.in | ||
| HACKING | ||
| INSTALL | ||
| LICENSE | ||
| Makefile.am | ||
| makefile.msc | ||
| NEWS | ||
| NEWS.pre-2-0 | ||
| NEWS.pre-2-2 | ||
| README | ||
| README.i18n | ||
| README.win32 | ||
The GNU Image Manipulation Program Version 2.3 ---------------------------------------------- This is an unstable development version of GIMP. Please realize that this is in no way a final product. A lot of new features are incomplete and some things may even be completely broken. If you need to get work done, please use the stable version, GIMP 2.2. GIMP 2.3 replaces earlier GIMP 2.x versions. It is advised that you uninstall them before installing GIMP 2.3. If you want to keep your older GIMP 2.x installation in parallel to GIMP 2.3, you have to choose a separate prefix which is not in your default library search path. Otherwise your GIMP 2.2 or GIMP 2.0 installation will start to use the new libraries. You have been warned. If you think you found a bug in this version, please make sure that it hasn't been reported earlier and that it is not just new stuff that is still being worked on and obviously not quite finished yet. If you want to hack on The GIMP, please read the file HACKING. For detailed 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/downloads/ 2. Mailing Lists ================ We have several mailing lists dedicated to GIMP user and development discussion. There is more info at https://lists.xcf.berkeley.edu/mailman/listinfo/<listname> with <listname> replaced by "gimp-announce", "gimp-user", "gimp-win-users" 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. There is also a mailing list, "gimpwin-users", dedicated to users of the Win32 port. To subscribe, send an empty message to gimpwin-users-subscribe@egroups.com You can also use the web interface at http://www.egroups.com/group/gimpwin-users/. Note that as this mailing list is 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 GIMPNet (a private free software oriented network) there is #gimp. Many of the developers hang out there. Some of the GIMPNet servers are: irc.gimp.org:6667 irc.us.gimp.org:6667 irc.eu.gimp.org:6667 4. Customizing ============== The look of GIMP's interface can be customized like any other GTK app by editing the ~/.gtkrc-2.0 file or by using "themes" (ready-made customizations). For downloadable themes and further details, see http://gtk.themes.org. Additionally, GIMP reads ~/.gimp-2.2/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-2.2/menurc. You can also manually change the keybindings to any of your choice by editing ~/.gimp-2.2/menurc. Have fun, Spencer Kimball Peter Mattis Federico Mena Manish Singh Sven Neumann Michael Natterer Dave Neary