Re: Re: [nbdev] Too many editor tabs?

> Date: Tue, 21 Mar 2006 00:45:37 +0100
> From: Marian Petras <[email protected]>
> To: [email protected]
> Subject: Re: [nbui] Re: [nbdev] Too many editor tabs?
> 
> Ivan Soleimanipour wrote:
> >> 1) There is not a special mode (frame) but a special "navigation tab" 
> >> for files opened just for browsing/navigation. The navigation tab is 
> >> opened when a navigation action (Ctrl+click, debugger action, etc.) 
> >> leads to a file not currently opened in the current tabs.
> > 
> > That's a problem.
> > If I want to open file X, I have to magically divine whether it's
> > in the "current tabs" or in the navigation tab.
> > We want 1 "cache" for user to look into not two
> 
> I agree that "we want 1 cache" - theoretically. But as there are 
> multiple and mixed(!) use cases of navigation/editing/opening files, I 
> still consider my suggested solution the best I can think of at the moment.

If you have two caches where it's unpredictable where things are
the point of having a cache becomes absolutely useless.

And even then I maintain that as soon as the number of explicitly
opened files exceeds 3 or 4 the horizontal tabs fail to act as a cache.
With a menu you click and very quickly scan down and pattern match.
with the tabs you have the click check, click check  ... and where
the new tab and name appears shifts in you field of view ...

> 
> 
> > Tab's in my view are "implementation artifacts" they are associated
> > with buffers/models. Why do we need them? An editor view should provide
> > easy access to files.
> 
> Again, this is too theoretical for me and it does not lead me to 
> anything more usable.

OK, here's concrete:
1) throw away tabs.
2) have an LRU (not alphabetical) list in a menu pulldown.
3) make it much easier (using filename completion) to open a file 
   not on the lru list.