[Gimp-developer] ANNOUNCE: GIMP 2.7.1 released
Hi, We are pleased to announce the availability of a new development version that brings us closer to GIMP 2.8. This version is packed with important new features and improvements. For a complete list of changes since 2.7.1 please see the Changes section below. Also see the release notes of the 2.7 series at http://www.gimp.org/release-notes/gimp-2.7.html Please note that the whole 2.7.x series of versions is considered unstable and is not recommended for use in production even though it might just work for you. Our intention is to make development versions available for passionate users who can provide useful feedback to help us fix bugs and streamline implementation of some of the new features. The upcoming v2.8 also introduces a huge amount of API deprecations and additions that have the potential to break existing 3rd party scripts and plug-ins. Please file bugs for all plug-ins and scripts that do work in v2.6, but don't work in 2.7.2. A migration guide for developers will be provided when v2.8 is out. There is still a lot of work to do on v2.8. Please refer to http://tasktaste.com/projects/Enselic/gimp-2-8 to find out what the current estimate of the v2.8 release is, and what bugs you can help us fixing to make the new stable version happen sooner. Happy GIMPing, --Mitch Download GIMP 2.7.2 is available from: ftp://ftp.gimp.org/pub/gimp/v2.7/ and from the mirrors listed at: http://www.gimp.org/downloads/#mirrors The checksum of the tarball is: 6996138ab70b0bfebfe9f563284e5f78 gimp-2.7.2.tar.bz2 Changes in GIMP 2.7.2 = UI: - A lot of undeprecations due to GTK+ 2.22 and 2.24 - Lots and lots of cairo porting, calls to gdk_draw_* are gone - Merge the cage transform tool from GSoC - Remove the old bitmap cursors completely and always use RGBA cursors also for compat cursors for old X servers - Add new GimpCanvasItem infrastructure with subclasses for everything that needs to be drawn on the canvas and port all tools to canvas items, this is a huge change that touches all tools and almost all display code, and which finally gets rid of XOR drawing altogether - Switch from purely idle-rendering the display to something that ensures a minimum framerate, so we don't fail to update under heavy load - Make the text tool handle RTL mode better - Change GimpColorMapEditor to use the newly added proxy GimpPalette - Replace the brush scale control in tool options by a brush size one that works in pixels, and does the right thing when the brush changes - Add new widget GimpSpinScale which is a scale with number entry, and use it in all tool options - Make the brush, pattern etc. selectors in tool options more compact and allow to directly jump to the editor dialogs - Make handle sizes in tools consistent - Add an on-canvas progress and use it for tool progress instead of the statusbar - Add a new GimpToolPalette class with lots of code that was in GimpToolBox - Allow to properly drop into and after a layer group - Refactor and clean up the dynamics editor widget, and add colors for the curves - Add support for F2 to rename items in lists - Clean up GimpDeviceStatus internally and visually - Allow to set GimpToolPreset's icon using the new GimpIconPicker widget - Make the text tool's style overlay show default values from the text object if there is no style active at the cursor position/selection - Show the the text size's unit in the text style overlay - Make tool dialogs transient to the image window again - Consistently add a gimp- prefix to all window roles - Make the preset buttons in tool options work on the global tool presets instead of the removed per-tool preset lists - Add GimpControllerMouse, which allows to bind extra mouse buttons to arbitrary actions Core: - Add uniform API to turn any GimpItem's outline into a selection - Add support for color tags in text layers - Remove the selection_control() stuff from GimpImage and with it maybe last piece of UI code still not properly separated - Add more validation code for XCF loading - Add accessors to GimpPalette and use them globally - Keep a proxy GimpPalette around for the image's colormap - Don't scale SVGs when pasting or importing them - A lot of changes to the input device handling code, partly merged from the gtk3-port branch, add GimpDeviceManager class - Add smoothing of paint strokes - Fix display filters to work on a cairo surface - Fix and enhance GimpImage's URI/filename handling API - Unset removed flag on items when they get added back to the image from the undo stack - Change item creation to properly use GObject properties and remove item_configure() and drawable_configure() - Refactor tool event handling and move lots of stuff into utility functions - Clean up GimpViewRenderer API - Implement transforms on group
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1 released
On 04/15/2011 08:17 PM, Michael Natterer wrote: ... Argh, it's 2.7.2 of course... ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
On 2010-07-03 16:29, Jernej Simončič wrote: On Saturday, July 3, 2010, 22:01:50, photocomix wrote: snipsnip One other thing I noticed about the installer is that it does not AFAICT allow user to chose where to install but forces to: C:\Program Files\GIMP 2.7\ (on WinXP SP3). Was this to test some other part of the Win32/Win64 and/or Win7 business or just oversight? Regards ... Alec ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
On Sunday, July 4, 2010, 11:27:35, Alec Burgess wrote: One other thing I noticed about the installer is that it does not AFAICT allow user to chose where to install but forces to: C:\Program Files\GIMP 2.7\ (on WinXP SP3). Was this to test some other part of the Win32/Win64 and/or Win7 business or just oversight? The installer actually defaults to Program Files\GIMP 2, but you can change that if you choose Custom install. -- Jernej Simončič http://eternallybored.org/ Anything that begins well ends badly. Anything that begins badly ends worse. -- Universal Law ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
On 2010-07-04 05:36, Jernej Simončič wrote: On Sunday, July 4, 2010, 11:27:35, Alec Burgess wrote: One other thing I noticed about the installer is that it does not AFAICT allow user to chose where to install but forces to: C:\Program Files\GIMP 2.7\ (on WinXP SP3). Was this to test some other part of the Win32/Win64 and/or Win7 business or just oversight? The installer actually defaults to Program Files\GIMP 2, but you can change that if you choose Custom install. Sorry ... my bad ... on first install I missed the [Custom] button - I think because I was perplexed by the forced uninstall and clicked w/o thinking. After uninstall and reinstall everything is where I wanted it. Regards ... Alec ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
Sorry ... my bad ... on first install I missed the [Custom] button - I think because I was perplexed by the forced uninstall and clicked w/o thinking. After uninstall and reinstall everything is where I wanted it. Regards ... Alec Maybe move the UNISTALL step after CUSTOM and add in CUSTOM a option to skip the Unistall will help a bit even if i would prefer see at the Unistall step a visible checkbox allowing to skip that PS soorry for the missed Re in the subject title...seems a little bug at gimpusers.com when using the forums...should be manually added as now -- photocomix (via www.gimpusers.com) ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] ANNOUNCE: GIMP 2.7.1
For not clear reasons the Windows installer of 2.7.1 force unistall of previous version of gimp Apparently no way to skip unistall, or to cancell unistall/install process The point is i can't see any reason to force unistall, the 2 version create 2 different gimp folder in the user directory...and for the rest seems run well alongside about the question on ufraw and thor reply But be aware then that telling about it might inspire random, more clueless, other people to repeat the trick without really knowing what they are doing. --tml reply is correct but replacing intl.dll with libintl-8.doesn't not create problem only with ufraw But with most, almost all extra plugins without intl.dll they all (except Gmic, including Gap-2.6) abort at loding time with error messages Only solution i could find is adding back intl.dll, (not renaming libintl-8, just add bact intl.dll ) Do you think may be a better solution? Advice all plugin writers to remap all the calls to intl to libintl may be pratical in long term to port plugins to gimp 2.8 but will not solve any of present problem As far i could test add back that intl.dll has no practical adverse side effects -- photocomix (via www.gimpusers.com) ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
On Saturday, July 3, 2010, 18:13:04, photocomix wrote: For not clear reasons the Windows installer of 2.7.1 force unistall of previous version of gimp That is correct. Apparently no way to skip unistall, or to cancell unistall/install process Apparently somebody is claiming things without even trying the installer. The point is i can't see any reason to force unistall, The point is that the new installer combines 32 and 64-bit GIMP in a common installer, and once it becomes stable, many people will be upgrading from 32-bit GIMP 2.6 - it would make no sense for these people to keep both GIMP 2.6 and 2.8 at the same time, so the new installer removes the old version first. Since this functionality needs to be tested before it's deployed in the stable installer, it's forced in the unstable one (the uninstall will be optional, but I haven't implemented that yet). -- Jernej Simončič http://eternallybored.org/ The more campaigning, the better. -- O'Brien's First Law of Politics ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] ANNOUNCE: GIMP 2.7.1
Apparently no way to skip unistall, or to cancell unistall/install process Apparently somebody is claiming things without even trying the installer. Sergey i tried the installer and i could not see how cancel or skip unistalling AT THE POINT OF UNISTALLING Judging from messages i see here The point is i can't see any reason to force unistall, The point is that the new installer combines 32 and 64-bit GIMP in a common installer, and once it becomes stable, many people will be upgrading from 32-bit GIMP 2.6 - I didn't saw any option in the 2.7.1 installer for chose 32 or 64 bit even if my computer support 64 bit i suppose installed, without asking the 32 bit version since all my extra plugin, that were usually not compiled to work at 64 bit, seem working fine .. many people will be upgrading from 32-bit GIMP 2.6 - it would make no sense for these people to keep both GIMP 2.6 and 2.8 at the same time, so the new installer removes the old version first. Since this functionality needs to be tested before it's deployed in the stable installer, it's forced in the unstable one (the uninstall will be optional, but I haven't implemented that yet). Sure? most (if not all) of third party plugin are not compiled for 64 bit but only for 32 so many may prefer run a 32 bit gimp even if a 64 bit version could be available Or simple they may wish to run a stable version for work...and a beta for the fun to test new features... -- photocomix (via www.gimpusers.com) ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
On Saturday, July 3, 2010, 22:01:50, photocomix wrote: Sergey i tried the installer and i could not see how cancel or skip unistalling AT THE POINT OF UNISTALLING Judging from messages i see here Once the uninstaller is running, there's no way to cancel it - it wouldn't make any sense anyway, since some files are already deleted at that time, and there's no way to bring them back. This is why the installer displays a warning before it starts. However, since you are apparently the third person who ignored that dialog, I guess I'll have to bring the checkbox back. Sure? most (if not all) of third party plugin are not compiled for 64 bit but only for 32 so many may prefer run a 32 bit gimp even if a 64 bit version could be available By default, the 64-bit version installs everything needed to run 32-bit plug-ins as well (in fact, the 64-bit version always uses 32-bit TWAIN plug-in, since the 64-bit one doesn't work). BTW, please fix your e-mail program so that it doesn't strip Re: from subject. -- Jernej Simončič http://eternallybored.org/ Information which is true meets a great many different tests very well. -- Berkeley's Fourth Law ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
Tor, and what solution can you advice? Now I can see two alternatives - to rename libraries and have UFRaw working, and do not rename libraries and do not use UFRaw. Tor Lillqvist wrote: after renaming some libraries (libintl-8 to intl, libpng14-14 to libpng12-0) everything went Ok Renaming DLLs is never a good idea. There might be a good reason why the name was changed - namely because the API and/or ABI has changed. --tml With respect, Alexander Rabtchevich ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
Tor, and what solution can you advice? File bugs with the respective maintainers to fix the problem? But yeah, that might take a while of course. So sure, if you know what you are doing, and you verify that it works, feel free to rename DLLs. But be aware then that telling about it might inspire random, more clueless, other people to repeat the trick without really knowing what they are doing. --tml ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] ANNOUNCE: GIMP 2.7.1
It is about time... We are pleased to announce the release of GIMP 2.7.1, a development snapshot on the way to the next stable version GIMP 2.8. You will need the latest stable releases of a couple of libraries in order to install GIMP 2.7.1; the following requirements have been updated: GLib 2.24.0, GTK+ 2.20.0, BABL 0.1.2, and GEGL 0.1.2. GIMP 2.7.1 brings a whole lot of new features and improvements, see the release notes at http://gimp.org/release-notes/gimp-2.7.html for details. A brief but more comprehensive list of changes is available at http://git.gnome.org/cgit/gimp/tree/NEWS and below. Happy GIMPing! --Mitch Download GIMP 2.7.1 is available from: ftp://ftp.gimp.org/pub/gimp/v2.7/ and from the mirrors listed at: http://www.gimp.org/downloads/#mirrors The checksum of the tarball is: 4932a0a1645ecd5b23ea6155ddda013d gimp-2.7.1.tar.bz2 Contribute == Wondering why it took so long from GIMP 2.7.0 to 2.7.1? The default answer to that question, when asked on the mailing list or on IRC, will often be because you didn't help us. We are always short of resources, and everybody is invited to join development. There are a lot of areas where you can help, even if you are not a programmer: http://www.gimp.org/develop/ Changes in GIMP 2.7.1 = UI: - Add lock content button to the layers, channels and paths dialogs, make the lock buttons more compact - Refuse to edit locked items - Add support for layer groups - Improve internals and GUI of the save/export functionality - Move the shortcut dialog's clear button into the entry - Clean up UI code by introducing GimpDockWindow and GimpImageWindow classes - Support multi-column dock windows - Get rid of docking bars, use highlights in existing widget hierarchy instead - Remove toolbox-window-hint gimprc setting and use dock-window-hint for both toolbox and docks instead - Move GimpDock::default-height style property to GimpDockWindow - Polish save+export path-part precedence rules - Merge the GSoC 2009 Advanced GUI for Brush Dynamics project - Default to non-fixed-aspect in Canvas Size dialog - Add a still incomplete Single-window mode - Have an Export button, not Save, in export dialogs - Improve Free Select Tool handle highlightning - Support changing user interface language from preferences - Update ps-menurc with PS CS4 keyboard shortcuts - Reduce spacing around canvas and use it for the canvas itself - Put name of active dockables in dock window titles - Don't have Toolbox in list of Recently Closed Docks, handle that directly in the Windows menu - Support selecting and tagging multiple objects in resource lists - Improve on-canvas text editing and text attribute setting - Add GimpContainerTreeStore and use it in all GtkTreeStore based views - Add a new default automatic tab style that makes sure dockable tabs always show as much detail as possible - Remove the dockable title bar and add the menu arrow button next to the notebook tabs - Add an icon for the desaturate tool - Add 'Rule of fifths' crop guide overlay - Make Alt+Click on layers not affect active layer Core: - Make all GimpItems lockable so their contents can't be changed - Make more sense when naming imported layers - Make group layers work except for layer masks and save them in the XCF - Change GimpProjectable::update to GimpProjectable:invalidate - Make sure we don't mix font backends (and crash) by explicitely asking for FT/Fontconfig backends - Move members of GimpObject to a private struct - gimp_object_get_name() takes a gconstpointer now, remove casts from all callers - Let drawables connect to their floating selection's update signal instead of letting the image do this job - Fix brush rotation artifacts at even 90 degree rotation - Don't leak shared tile memory on Solaris - Add a PDB procedure to access a text layer's markup - Remove legacy cruft from pdbgen and make sure number ranges are correct - Move all image creation functions to a common file - Add translation context to all undo descriptions GEGL: - Make sure all nodes are added to their resp. graphs - Use GEGL for layer scaling if use-gegl is TRUE Plug-ins: - Updated script-fu's scheme to latest upstream fixes - Don't store image-specific print settings globally - Add fundamental OpenRaster (.ora) import and export support - Add RGB565 support to the csource plug-in Data: - Add texture/grunge brushes made by Johannes Engelhardt Developer documentation: - Explain GimpContext - Add SVG graphic with GIMP application core module dependencies - Add a schedule for 2.8 development Source and build system: - Add more code documentation - Clean up subsystem linking dependencies in app/ - Add unit testing framework in app/tests/ and some basic tests, including basic UI tests and XCF tests - Tentatively introduce usage of using Glade + GtkBuilder - Depend on
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
In the new release notes of http://www.gimp.org/release-notes/gimp-2.7.htmlthe keyboard shortcut for shrink wrap is still noted Ctrl+R, although it is now Ctrl+J. Same problem for Fit in Window. Incidentally, does this latter command appear in some menu? Same question for Alt+click in a layer thumbnail: what is the name of the command, and does it appear in some menu? Olivier Lecarme ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
Hello Thank for the hard work. I haven't tried yet linux version, but Windows one does not show anything in a pop-up window for plugin previews (the window is grey). And UFRaw stopped working complaining entry point for the procedure BZ2_bzRead is not found. With respect, Alexander Rabtchevich ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
Von: Alexander Rabtchevich alexander.v.rabtchev...@iaph.bas-net.by I haven't tried yet linux version, but Windows one does not show anything in a pop-up window for plugin previews (the window is grey). Can't reproduce. And UFRaw stopped working complaining entry point for the procedure BZ2_bzRead is not found. Different version of the bz2 library, I guess. Regards, Michael -- GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl. Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
Michael Schumacher wrote: Von: Alexander Rabtchevichalexander.v.rabtchev...@iaph.bas-net.by I haven't tried yet linux version, but Windows one does not show anything in a pop-up window for plugin previews (the window is grey). Can't reproduce. Look at the navigation window. It is grey regardless GEGL preview is enabled or not. And UFRaw stopped working complaining entry point for the procedure BZ2_bzRead is not found. Different version of the bz2 library, I guess. The above message is shown when gimp plugin is used. Entry point for the procedure g_assertion_message_expr is not found in the library lbglib-2.0-0.dll is shown when a standalone UFRaw version is launched - it uses its own bzip2.dll. Is there a way to overcome that? With respect, Alexander Rabtchevich attachment: window.jpg___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
The problem with UFRaw was caused by the deinstallation of 2.6 version made by 2.7.1. After renaming some libraries (libintl-8 to intl, libpng14-14 to libpng12-0) everything went Ok except bzip2 library - UFRawonly wants the old one. With respect, Alexander Rabtchevich ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] ANNOUNCE: GIMP 2.7.1
after renaming some libraries (libintl-8 to intl, libpng14-14 to libpng12-0) everything went Ok Renaming DLLs is never a good idea. There might be a good reason why the name was changed - namely because the API and/or ABI has changed. --tml ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
