KDE/kdevplatform/shell

Andreas Pakulat apaku at gmx.de
Fri Nov 7 19:26:10 UTC 2008


On 07.11.08 18:33:51, Alexander Neundorf wrote:
> On Thursday 06 November 2008, Andreas Pakulat wrote:
> > On 06.11.08 21:06:11, David Nolden wrote:
> ...
> > Whats the problem with the documents list or the first 8 files in
> > quickopen? I understand that you want to keep an overview of what you're
> > working on right now, but 8 tabs already fail to work for me on my laptop.
> > I already have 2 of them not visible, even more if the filenames are a bit
> > longer.
> 
> I agree.
> Usually I don't close files, so usually I have many open files, more than 50. 
> Why should I actually close them ? The open-files is for me more like a 
> history of files which I used recently and may use again soon. If I save the 
> files I'm working on from time to time it should be enough. I actually also 
> don't really care if they are indeed open and loaded or not.
> Would it make sense to have a maximum number of files remembered as open ? 
> E.g. if I exit with 60 open files only the 50 most recently used files are 
> opened again ?
> Maybe indeed this is just more like a history function, and when starting 
> kdevelop only one file has actually to be opened and all others are loaded on 
> demand (easier if there are no tabs ;-) ).

Well, loading on demand means switching to another file might be pretty
slow. OTOH if you happen to have 50 files that need to be opened during
startup, startup slows down. So what we probably actually should have is
asynchronous opening of files, though I guess we can't simply put
kate::document into a thread :( And IIRC using timers+eventloop still means
a slightly lagging Ui while actually loading the document into memory -
especially for larger documents. 

> > > So we first need to develop a good replacement,
> >
> > Yeah, like a list of files you have open right now. This is called
> > Documents view and already works :)
> 
> Yes, that's what I use all the time.
> Only issue is the sorting of that view - 
> alphabetically: you can find everything, but everything needs a bit of time,
> most recently used first: you can find the files youre working on all the time 
> really fast, but the order of the others feels basically random, so for them 
> it takes very long (think 70 files or so).
> (maybe some combination of both ? 10 most recently used files at the top 
> followed by *all* open files alphabetically sorted)

That might indeed be a good idea. But I guess you didn't yet look at
kdevelop4, right? Because that one actually orders by filetype and then
alphabetically :)

Andreas

-- 
Live in a world of your own, but always welcome visitors.




More information about the KDevelop-devel mailing list