Re: [Nautilus-list] throbber out-of-process
- From: Darin Adler <darin bentspoon com>
- To: Havoc Pennington <hp redhat com>
- Cc: nautilus-list eazel com
- Subject: Re: [Nautilus-list] throbber out-of-process
- Date: Thu, 2 Aug 2001 16:33:58 -0700
On Thursday, August 2, 2001, at 03:39 PM, Havoc Pennington wrote:
The rationale I've heard for having the throbber out-of-process is so
that it keeps throbbing when Nautilus is locked up.
However, isn't the point of a throbber to show that Nautilus is doing
work? So if it's stuck then the throbber _should_ lock up, right? And
Nautilus doesn't get stuck nearly as much as it used to.
Just wondering if we can in-process this and trim a bit of excess
overhead.
We had an in-process throbber. It wasn't throbbing enough to the point
that people thought that Nautilus was completely broken.
So Andy made the out of process throbber. I said at the time that I would
have preferred to fix the places where Nautilus locks up. Nautilus was
designed so that it should basically never lock up. It should always be
another thread that blocks, not the main one.
I'm not sure where you get the idea that Nautilus doesn't get stuck as
much as it used to. Do the recent changes really make Nautilus get stuck
so much less? I think there are all sorts of things that make Nautilus
lock up more than it should.
So I'd love to have the throbber in process again, if it doesn't make
Nautilus immediately worse.
I believe that on balance throbber currently makes the experience better,
even if it's somehow slightly dishonest to keep it throbber when Nautilus
is locked up.
-- Darin
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]