Slashdot Mirror
GIMP 2.8 Will Sport a Redesigned UI
ceswiedler writes "Ars Technica's Ryan Paul previews the upcoming release of the GIMP. It will include a single-window mode where the user can dock toolbar windows and switch between images via tabs. There are other improvements as well, including docking support in multi-window mode and improvements to the text tool." To get this early preview, Paul compiled version 2.7.1 from the active development branch, along with its dependencies.
Will GIMP finally get support for masks?
I'm glad they're doing this.
It makes it much easier to work on the images, instead of having to "mishap-click" on every single window, and having to click on the related window in order to get back into the image editor again. WAAAAY overdue, but finally here - good job guys!
What this world is coming to - is for you and me to decide.
Why not floating windows inside the main window?
Oh I know why: because the GTK designers don't like floating windows inside a window for whatever strange reason.
But great improvement nonetheless, kudos!
I used to prefer GIMP to Photoshop back in the day because I could work so much more quickly with many, many open files and windows using GIMP thanks to the "lots of little windows" approach. It made fine-grained window management easy using a capable window manager and focus-follows-mouse.
I always found the Photoshop interface clumsy in comparison, but now with every release GIMP gets closer to it.
STOP . AMERICA . NOW
But some of the screenshots look Photoshopped.
Set your phasers on "funky"!
Are they still committed to breaking one of Gimp's best features: "Intelligent Save" ? (Inferring file type based on extension)
Splitting "File > Export" and "File > Save" is counter-intuitive; it's not DWIMish, and I guarantee more people will be frustrated that the Save dialog box is "broken" when they try to save a JPG and end up with an XCF file instead. "File > Export" reeks of being Designed By Developers, rather than actually taking user behavior into account.
(And stealing the keystroke for "Fit In Window" is just adding insult to injury...)
Like a lot of novice users I gave GIMP a shot. Loved the plugin system and spent many an hour trying to get older plugins working and tweaking other plugins to do some neat effects. But in the end the UI made it difficult and confusing to use. For YEARS the internal arguments over the UI made it seem unlikely something like single window mode would reach maturity (and become usable on Windows). Kudos to the developers. I'll give it another shot.
"God fights on the side with the best artillery." - Napoleon, Marshal of France - speaking truth to power
So, "Gimp 7 was your idea." ;)
Multi-window is nice if you've got a ginormous wide-screen or multiple monitors. Multi-window on a smaller screen, or god forbid a laptop, is a real pain unless you live in it day-in day-out. Kudos for letting users choose the right tool for the job.
GIMP is always compared to photoshop. There are some key features missing in GIMP that do not allow serious artists to move to it from Photoshop. Three of these are adjustment layers (which GEGL is suppose to eventually bring about, but it's been a long wait), proper 16 and 32 bit image editing and LAB and CYMK modes. (GIMP only does RGB). I'm greatful for GIMP and thankful for the developer's efforts but I'd rather they focus on these things than dicking around with windowing. The truth is once you get use to it, GIMP's windowing isn't THAT bad.
These posts express my own personal views, not those of my employer
Me, I don't care much about the UI - I'll get used to whatever way it goes. The significant change, to me, is left at the very end of the article: GEGL and proper high-bit-depth color support it brings.
Yes, this is *that* post. Just trying to keep it fresh in your mind. I use the GNU Image Manipulation Program all the time, and internally, I call it GIMP, and amongst friends in the know, I call it GIMP, but amongst people who are new to FOSS, I usually make an effort to use the full name. Every once in a while, I forget, and most people associate GIMP or "The GIMP" with Pulp Fiction these days, or worse, they've never seen Pulp Fiction because they would be offended by it, but they still know "The GIMP" through cultural allusions to that character, and thus are offended by any reference to GIMP.
Hell, I'd even take GIMPY (the GNU Image Manipulation Program for You), since that evokes a different, albeit still negative, emotional response.
The best suggestion I've heard is just drop GNU or make GNU separate from the acronym: IMP, GNU IMP.
Hell, I'd even take GIMPY (the GNU Image Manipulation Program for You), since that evokes a different, albeit still negative, emotional response.
I wonder how the citizens of Gympie would feel about that assertion!
Anyway, I'd rather that time were spent so that Gimp worked in linear colour space (~ 16 bits per channel) rather than botching all the operations in 8bit/channel sRGB. As it currently stands, filtering operations etc are wrong.
For example (at least in 2.6) it still thinks that the average of sRGB black and white is 0x808080, which is far too dark. It should be something more like (doing a back of the envelope calculation) 0xBABABABA.
And the reasons for this are political, with a side of history. The GIMP developers invented GTK+, and now they're tied to it.
Know what? GTK+ is great under X11. It looks and behaves like crap under everything else, regardless of what theme you select. Basic UI principles say that your applications should be consistent with the OS, and that means using standard widgets (menu bars, icons, buttons, file open dialogs, and other things that match the look and feel of your OS). When GIMP was first released there WERE no standard widgets for Linux, so the devs hacked some together and released them as a separate library. A couple other devs saw the work that had been done, and figured that GTK could be used to save work on their own projects, and before long a ton of apps and window managers used it. Some of those app developers wanted to port their apps to Windows and Mac OS, and so GTK+ was ported as well. But because GTK+ manually renders all the buttons and widgets and so on, the ports look out of place. Strike that. They look godawful. Really this isn't GTK's fault, it's just not the right tool for the job. It's not just that they look bad, but users have to learn things like how to interact with a new file manager. It's unprofessional, it robs the user of time and effort, and it makes ported open source software seem inferior to native apps.
Recognizing the inherent problem, several other developers made toolkits so that apps would look normal again. A wxWidgets program compiled for Linux uses GTK+ to draw the dialogs and menus, but calls the native widget functions under Windows. The result is a program that looks like it was designed specifically for each OS on which it runs. Take a look at screenshots of Audacity for a great example.
They could design the UI in wxWidgets or Qt to make it actually look decent under every OS, but they won't-- and really at this point they can't, because the former would be seen as pandering, and the latter would be seen as abandoning GTK+. But to everyone outside the community, it looks like the GIMP devs are rallying to prove the superiority of GTK+ using the flagship Linux graphics app, at the expense of the open source movement. It only pisses off those of us who are trying to ease migrations to a free OS by gradually replacing existing non-free apps with free alternatives like OpenOffice. OO is a drop in replacement for MS Office in many cases, and behaves almost exactly like a native app under Windows. On the other hand, Inkscape is a great program with a decent UI, but I can't wholeheartedly recommend it as an Illustrator replacement to Windows users because it doesn't look or act like what they're used to. And if I can't get my mother weaned off the crippled photo editor that came bundled with her camera, I'm never going to get her to switch completely.
Face it, folks, GTK+ is cross platform only by the loosest possible interpretation. I realize a lot of time and effort has gone into the 2.7/2.8 "redesign", but these UI changes to GIMP are too little, too late. At this point the only thing which is really going to save The GIMP on other platforms is a complete UI redesign using something other than GTK+. If GEGL is ever finished this shouldn't be too hard. Conveniently this would also allow us to change the cringe-inducing name as well. The result would be a Photoshop replacement that would look like it wasn't cobbled together by two bearded guys in a basement.
It's not the user's job to change themes. It's the toolkit's job to detect when a theme is overpadded for a given application and automatically correct for it.
Sorry, but as much as I want applications to automatically do stuff on this one I have to disagree.
The application ought to honor the styles set by the Windows manager, and not run off and do its own thing. How is the application suppose to know that the user did not want it overpadded? Or do you really want every single application to have all kinds of little settings to modify the display and break the central theming provided by the Windows Manager?
Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
Just looked at it. Indeed, it seems that the windows version is build for a min height of 800px. Anything less and buttons start to disappear.
But if you change the icon size (interface preferences, nothing fancy. Does require a restart, which it doesn't mention) then it will fit as far as I can see.