|
From: | Dmitry Gutov |
Subject: | Re: Unified project interface |
Date: | Mon, 27 Jul 2015 04:49:04 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0 |
On 07/27/2015 02:56 AM, John Yates wrote:
If there were no cost to keeping the cache current (equivalent to stating that a naive user never would _never_ need to learn of that cache) would you still advocate such a UI?
I think the word "cache" itself implies a storage that can get stale.
Bottom line: start by getting the model of state and the UI right. After that if the performance in corner cases needs help then give advanced users tools to tune the system. But please do not foist a user-maintained cache on casual users.
Right. Even if there's a cache mechanism, I'd very much like to see its invalidation by automatic means (via file-notify, or similar), at least by default.
Anyway, I'd prefer to implement as many operations as feasible without needing that cache. If the search through the project tree spends an order of magnitude more time searching than listing the files, there's not point in caching the latter.
[Prev in Thread] | Current Thread | [Next in Thread] |