Earlier quoted context omitted.
I'm not convinced. The UI in early Blender was as arcane as any I have ever seen, worse than GIMP's by a mile. Contemporary commercial 3D software did not have the same quantity or quality of weirdness. (Remember SoftImage?) The commercial version of Blender failed in the marketplace, and after it was open sourced, it was not taken seriously again for quite a few years. Blender's dogfooding efforts were a powerful fo…
> The UI in early Blender was as arcane as any I have ever seen, worse than GIMP's by a mile. That's just not true at all. GIMP's UI has no redeeming workflow . Even if you master it, you must still constantly navigate it's clunky menu of features. Blender 2.x had an intentional UX flow. When you mastered it - which really wasn't nearly as difficult as whatever work you were doing with it - you could be very producti…
Is this radical redesign of GIMP possible now?
171–180 of 306 posts
Re: Is this radical redesign of GIMP possible now?
#172Earlier quoted context omitted.
macOS has had the ability to search menus for what seems like a decade. It should be a feature of the toolkit, not something apps need to implement themselves. This doesn’t extend to other UI elements (like System Prefs/Settings), but I agree that it should (and again, should be a toolkit feature).
> macOS has had the ability to search menus for what seems like a decade. Wow, TIL. Talk about a hidden feature. So it turns out it's under the "Help" menu, and it just says "Search". I had always assumed that this searched help topics, not menus. But it's also pretty miminal, seemingly without support for synonyms or features inside of dialog boxes -- e.g. if you type "pref" it won't find "Settings". It also doesn't…
Raycast for example. It still wont find synonyms, but it works well enough that I frequently use it in Affinity and similar apps.
Re: Is this radical redesign of GIMP possible now?
#173Earlier quoted context omitted.
The fundamental difference between Blender and Gimp is that Blender started life as a commercial product, designed by 3D professionals for other pros. Yes, the interface was different and the learning curve hardcore, but it had an internal logic that enabled fast workflows when you’d mastered it. Gimp was designed by open source hackers with no input from professional designers, or seemingly even any interest in thei…
I'm not convinced. The UI in early Blender was as arcane as any I have ever seen, worse than GIMP's by a mile. Contemporary commercial 3D software did not have the same quantity or quality of weirdness. (Remember SoftImage?) The commercial version of Blender failed in the marketplace, and after it was open sourced, it was not taken seriously again for quite a few years. Blender's dogfooding efforts were a powerful fo…
I loved Softimage's look ! Flat and minimalist zen design way before ! Then I got the credits for that course and moved on to different pastures.
Re: Is this radical redesign of GIMP possible now?
#174Earlier quoted context omitted.
It would not shock me to learn that GIMP has been a multi decade study to find out how bad a UX has to be before the FOSS community starts to care.
GIMP has one of the best user interfaces of all community driven open source software. I frankly can't think of any that are better, now that Firefox followed Chrome in hiding all its most important features.
Re: Is this radical redesign of GIMP possible now?
#175Earlier quoted context omitted.
macOS has had the ability to search menus for what seems like a decade. It should be a feature of the toolkit, not something apps need to implement themselves. This doesn’t extend to other UI elements (like System Prefs/Settings), but I agree that it should (and again, should be a toolkit feature).
> macOS has had the ability to search menus for what seems like a decade. Wow, TIL. Talk about a hidden feature. So it turns out it's under the "Help" menu, and it just says "Search". I had always assumed that this searched help topics, not menus. But it's also pretty miminal, seemingly without support for synonyms or features inside of dialog boxes -- e.g. if you type "pref" it won't find "Settings". It also doesn't…
I find the OSX search feature close to useless as a "help" feature because of this.
I came to the realization that it's more like a power user shortcut tool than something to help new users. If you know exactly what you're looking for and exactly what the application calls it then you can skip navigating through nested menus.
Re: Is this radical redesign of GIMP possible now?
#176Universal search in UI is cool, and I’m all for it, but it shouldn’t be the only/primary way of accessing tools as tool discoverability is very low. The author tries to deal with this by putting the a menu next to a search bar and putting hints in the bottom menu (which I don’t think would really work here, as raster tools are less selection-specific than 3D tools). Search fixes the speed-of-access issue, but doesn’t…
Universal UI search is great, and at this point it should be present in all but the simplest applications. I first saw it introduced in Google Docs, and it's precisely for things you suspect exist, but it's not even remotely clear which menu, submenu, or dialog it's in. (Apple OS Settings is another great example of it.) E.g., you want to apply a hanging indent in Docs? Just type "hanging" into the menu search, and i…
They changed it recently. Now it’s a nice prominent rounded search box in the upper-left corner.
Re: Is this radical redesign of GIMP possible now?
#177Re: Is this radical redesign of GIMP possible now?
#178Re: Is this radical redesign of GIMP possible now?
#179Gimp isn't more complex than Photoshop. We don't need it to reinvent drawing applications.
Re: Is this radical redesign of GIMP possible now?
#180All these programs like GIMP, Blender, Dune, should split into two. There should be a library that has the functionality and data structures to manipulate data. The UI should be a separate project with different people. There could be multiple GUI's for the same project or same GUI framework for multiple projects.
In theory, Oz was UI toolkit agnostic but, as anyone who's ever done UI work will understand, it rapidly became wedded to the toolkit we used (a heavily customized version of Tk). This made the eventual switching to Qt very, very difficult. So difficult it nearly destroyed the artists' faith in the R&D group. (Extremely late delivery, buggy, and coming at the manpower cost of not doing any improvements on the tool itself for a year and a half.)