On Fri, Jul 01, 2005 at 07:30:45AM -0400, michael chang wrote:
> On 6/30/05, Carol Spears <[EMAIL PROTECTED]> wrote:
> That said, The GIMP technically *shouldn't* load *all* of it's brushes
> on startup, should it?  (At least not when a user has this many
> brushes and patterns.)  Like there should be a threshold, e.g. The
> GIMP will only load 32-128 brushes/patterns (this is a combined
> number, and should be configurable, and based on memory requirements)
> concurrently in memory on startup, and the rest will be left stored on
> disk and read as necessary.
> Then again, this sounds like Windows XP's prefetching method of
> "speeding up the launch of applications" -- which is nice if you start
> the same thing every day, but if you have 200 applications and you
> maybe use each one 3 times a month, the computer might end up trying
> to prefech (e.g. 5 files per application) 1000 files on startup,
> causing it to "freeze" on startup for a minute before you can use it.
> There's no way to win.
> Has someone mentioned this "bug" to GIMP-devel?  Maybe we can put it
> on a TODO list [consider changing pattern/brush management system(s)
> in The GIMP].  Or someone can submit a patch?  *shrugs*
they have been discussing this and there is probably already a bug about

demanding it and/or complaining about it on the user list is probably
the worst approach to affecting a change in how volunteer software gets
fixed or making an enhancement request.

the analogy was funny tho'

recently i would go to see one friend and watch as the phones were used
and soon others would show up.  it was always fun.  other times, i knew
that people were scheduled to be there, allowing me to attend or avoid.

then at restaurants you have your all-you-can-eat buffet or your menu
style dining.

it all goes into "whatever".

as far as gimp is concerned, my suggestion will work.  more than likely
bug reports (enhancement requests) have been made and i have seen it
discussed on the irc.

nuno was looking for an argument though.


Gimp-user mailing list

Reply via email to