|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
On Fri, Dec 9, 2011 at 2:38 AM, Ofnuts <ofnuts@xxxxxxxxxxx> wrote:Tagging tries to relieve that... There is a very recent patch in
> IMHO the problem is more with the current single-level display of brushes.
> Gimp will look in subfolders of the declared folders, but it should allow
> some hierarchical navigation as well. The current interface must have been
> designed when the designers thought that 100 brushes would be plenty.. They
> were right on one point: the resulting interface is very hard to use with
> more than 100 brushes.
master that adds subfolders into the tag cloud. but yeah, it wont cure
the loading slowness.
You wont get around lazy loading with that. Tool presets have brushes
> And once you have a hierarchical navigation, you only need to load the
> brushes from the current brush folder.
saved in it. What should happen if the preset's brush or gradient or
whatever isn't in the current set? What if a script refers to a brush
that isn't currently active? Nothing is ever as simple as it looks.
There is a lot of interdependency among various bits of gimp and
sometimes gimp-s aim for stability complicates matters as well. Gimp
has had brush scaling for ages now, and we still have gazillion round
brushes, no longer visible in UI but still present, because scripts
may make use of them.
gimp-developer-list mailing list
_______________________________________________ gimp-developer-list mailing list gimp-developer-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gimp-developer-list
[Home] [Video For Linux] [Photo] [Yosemite News] [Yosemite Photos] [Yosemite Book Store] [gtk] [GIMP for Windows] [KDE] [Scanner] [Memory] [GEGL] [Gimp's Home] [Gimp on Windows] [Steve's Art] [Webcams]