http://www.gimpusers.com/news/00360-gim ... nt-release

Windows release should follow soon.

Bummer

Ahh I am happy with my Partha Version

I'm just gonna stay with that

Thanks for the info Rod, gonna spread the Windows Realease when it comes

I'm not real good at installing .tar files yet. If it doesn't come through the software manager or update manager I can never seem to get it right.

Are these Tar Balls kinda like what you get from a Rar Download of something in Windows?

Too bad i can't login on gimpusers, their recover password thingy seems broken, they go on on sending recovery links to my mail that lead only to not existing pages

As far from Windows i don't see reason to wait that release, Partha build has 2 big advantages, include python (and make work python on 2.7 seems more complex then with 2.6) and is also portable
Well is portable only at 64 bit but Partha was planning to do the same for 32 bit, maybe this weekend

PC there are some extras with this package here are the release notes from the site.
Quite a few new things - very nice
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 layers
* Clean up the transform tool a lot, and refactor away old junk
* Tool and tool event cleanup: enforce tool activate/halt invariants,
consistently shutdown all tools in control(HALT), and many other
tool fixes
* Remove GimpToolPresets object, this functionality got merged into
the new GimpToolPreset system
* Rename GimpFilteredContainer to GimpTaggedContainer and add a new
GimpFilteredContainer parent class which is a generic filter
* Remove the concept of an “offset” from TileManager and instead
pass around the offsets explicitly when needed, like when
transforming
* Move GimpBezier desc from vectors/ to core/ and add API to create
one from sorted BoundSegs
* Change GimpBrush boundary API to return a GimpBezierDesc
* Add GimpBrushCache object and use it to cache a brush’s transformed
pixels and its outline, remove the caching code from GimpBrushCore
* Add GimpBezierDesc based API to GimpScanConvert and use it

GEGL:

* Add operations and gegl infrastructure for the cage tool

Libgimp:

* Introduce an “item” type in the PDB and libgimp and deprecate
lots of old API in favor of item API
* Add procedures to create, traverse and manipulate layer trees
* Add more state to the context API, and deprecate functions with
too many parameters in favor of simpler ones that use context states,
particularly the entire transform and selection API
* Move GimpUnitStore and GimpUnitComboBox to libgimpwidgets, and
use them in GimpSizeEntry, deprecate GimpUnitMenu.
* Deprecate gimp_min_colors() and gimp_install_cmap()
* Add API that enables GimpRuler to track motion events by itself
* Add new selection API and deprecate all old selection functions
* Move around and rename all parasite functions, deprecate the old ones
* Add a generated PDB file in the “gimp” namespace and get rid
of “gimpmisc”
* Add unit conversion functions to libgimpbase
* Add function to reset a plug-in’s context to default values

Plug-ins:

* Make script-fu server IPv6 aware
* Follow libgimp deprecations in plug-ins and scripts
* Add PDF export plugin
* Lots of cairo porting here too
* UTF-8 fixes in script-fu
* Set the progress to 1.0 when done
* Merge a lot of upstream fixes into script-fu’s Tinyscheme
* Add “New Layer” option to MapObject
* Support loading of 16-bit raw PPM files
* Add web-page, a new plug-in which renders images of web pages
* Fix some more plug-ins to not warn if applied on an empty region

Data:

* Remove “Untitled” from palette names entries

Developer documentation:

* Move libgimp documentation from templates to inline comments
* Generate standard deprecated sections

Source and build system:

* Add more code documentation
* Add more unit tests and refactor existing ones to use global
test utility functions
* Add a manifest to executables (app and plug-ins, Win32)
* Depend on GLib 2.28, GTK+ 2.24, Cairo 1.10
* Make WebKit available to all plug-ins, not just the help browser
* Run UI tests on Xvfb if available
* Check for GdkPixbuf separately because it’s now a separate library
* Allow tests to use uninstalled plug-ins from the build dir
* Remove, comment out, or build for GIMP_UNSTABLE some stuff that
should not be in a stable release

General:

* Improve safety on Win32 by calling SetDllDirectory() and
SetProcessDEPPolicy()
* Switch from GtkObject::destroy() to GObject::dispose() all over
the place
* Various changes that make maintaining the gtk3-port branch easier,
such as s/GtkAnchorType/GimpHandleAnchor/ and s/GtkObject/GtkAdjustment/
* Don’t use gtk_container_add() for adding to GtkBoxes
* Inherit from GtkBox directly, not from GtkHBox/GtkVBox
* Add namespace to the ink blob types and functions
* Remove all useless calls to gtk_range_set_update_policy()
* Use GObject::constructed() instead of GObject::constructor() all
over the place
* Move more members to private and add accessors for them
* Stop using GdkNativeWindow, use guint32 instead
* Plug memory leaks
* Remove ps-menurc, we are not a PS clone
* Use the new g_[s]list_free_full() instead of foreach() and free()
* Don’t use newly deprecated GTK+ API
* Use the new GDK_KEY_foo key names
* Lots of bug fixes and cleanup
* Lots of translation updates

Damn you beat me to it

Weird i wrote a message but went MIA (or i forgot to click "Submit" ?)

Anyway Rod that are the changes respect the last stable version, changes respect to the build with Partha are much less...now i don't know exactly which but that build was based on a very recent code,and in less then 2 weeks are not probable major changes

(maybe more then add they just removed some too incomplete feature )

OMG!

I installed one dev compilation, just to try out the Cage Transform which is reeeaallly nice thing.

But the Cairo UI is something much more! It's sooooo addictive! I just can't stop playing with vectors, selections, and generally the whole interface works somehow better!

Yesss! Happy, happy!

Hi PC,

This is indeed great news that the devs have released 2.7.2.

You are correct, I use the nightly-builds. So, yes, the gimp-2.7.2 I have provided on my website is about 2 weeks old. The current version (as of April 4) requires gtk+-2.24.3 or higher and no windows build of gtk+-2.24.3 or higher exist (32 or 64). My next build will hopefully soon incorporate gtk+-2.24.4. However, this is short-lived since the next move for gimp is to get gtk+-3.0 or higher.

Thanks,
Partha

So are you saying that GTK might not make your GIMP Work with Themes?

should be no problems for themes

This is exactly why Windows should incorporate system wide libraries that update instantly on connection to the internet.Ahh but i can still dream.

Thanks PC, and Partha for the information.
We should also remember that because this is a developer release, bugs can be submitted.

Sorry Willy, nothing to do with the themes. I was talking about gtk+ which underlies gimp.

I haven't installed this yet, just haven't had time for it, but I will get around to it in the next few days hopefully.

Can someone post screen shorts of the new release to show the different from Parths' compiled windows version?

And also, is the forthcoming windows of the development release gonna be a compiled or just code?

i don't think that the difference are very visible (except for Partha's bigger preview windows for some old plugins as map object and gimpressionist )
that for partha include support for python and , for the last 64 bit version , is portable,

the other more "official"as far i know is not yet compiled for windows, so it is difficolt to compare



there is only a code for gimp there is no a Windows version, the developers don't provide binary, the compiled versions are always from other sources as from the mantainer of the Officially UNofficial windows build on http://sourceforge.net/projects/gimp-win/files/
,or from the various linux distro repository.

so last version is always only code and they may be compiled for all OS, doesn't exist anything speciphic for windows, not from developers side

The new development release is also supposed to contain the new web page plug-in.
Though i just updated Parthas version i do not see the new plug-in so i wonder if he is compiling the same src files?
Windows versions will be released as installs or setup files josephbupe.

PC i found out why my Gimp patterns and gradients and brushes were doing invisible acts - the themes in GTK were the problem.I stopped using them in 2.7.2 and no more problems.

Partha version come from a nightly build from 2 weeks before, and to release the official snapshot of gimp 2,7,2 the developer did some additional cleaning

I believe Partha is recompiling now the same version for 32 and 64 bit (and in case will include Python and mantain portability ) but i cannot predict the time needed

Neither i am sure if will be that or a even more resent nightly build to be compiled

PS
@ROD
yes themes may do weirds things
i was thinking to integrate a theme switcher but the problem is that is hard test Themes for compatibility, you never know what kind of problem they may create and how to replicate .at least till you don't stumble upon

even the MS windows theme is (was ? ) creating problems on some occasion, and in the stable builds