[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-devel
Subject:    Re: [RFC] KDev4 Ui
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2007-11-14 19:43:53
Message-ID: 20071114194353.GA17837 () morpheus ! apaku ! dnsalias ! org
[Download RAW message or body]

On 14.11.07 20:38:35, Jens Dagerbo wrote:
> On Wednesday 14 November 2007 19.40.21 Andreas Pakulat wrote:
> > Here's what I'm talking about: 
> >
> > a) file-list, a simple listing of files, eventually sorted in the
> > least-recently-visited order
> > b) edit-history, this includes any positions I have edited (not just
> > viewed).
> >
> > Afaik thats what we have in KDev3 as well. 
> 
> Not quite, KDev3 history adds an entry every time you call 
> KDevPartController::editDocument(), so if you use any language bases 
> navigation feature to jump between methods in the same file, these movements 
> will be recorded and "backable".

Aaah, ok.

> It's easy to remember and recall the point of the _last_ edit, and KDev3 does 
> this. But how would you define the point of the second-to-last edit? Where is 
> this? Probably not the second-to-last character you typed. Perhaps the last 
> edit point that isn't on the same line as the last edit?

No, using the function scope would be a starting point, additionally one
could use a 20 second timeout additionally, so you'd get a new edit
point when not doing a change for 20 seconds. 

Or maybe thats really too complex. Then we're back to file-list and
navigation-history. For the latter I'd still want the list as I
proposed.

> > All I wanted to do is give the latter one a proper UI, because IMHO
> > without UI its not usable - you don't see where a "back" or
> > "forward" takes you.
> 
> In KDev3 you can press-and-hold the toolbar button to see where you will end 
> up, but I never found that too useful myself. You typically "remember" 
> where 'back' will take you. Typical use would be something like: you 
> click 'QObject' in your code to have a look at qobject.h, once satisfied with 
> what you learned you hit 'back' to continue working. That's code navigation 
> history. And KDev3 supported this quite nicely. Calling it "not usable" is a 
> wild exaggeration.

Sorry, but for me its unusable because I don't want to go back only
once, but possibly many times. And using the toolbar is not an option as
I want that to be fast, having to go to my trackball and than waiting
another 2 seconds for the popup to show. I just want the keyboard
shortcut to show the last couple of places (or the "next") I've been to.

Andreas

-- 
Today is the first day of the rest of the mess.

_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]