[RFC] KDev4 Ui

Andreas Pakulat apaku at gmx.de
Wed Nov 14 18:40:21 UTC 2007

On 14.11.07 19:39:50, Jens Dagerbo wrote:
> On Wednesday 14 November 2007 18.50.50 Andreas Pakulat wrote:
> > On 14.11.07 16:00:52, Jens Dagerbo wrote:
> > > Why isn't the current Document List (or whatever it's called) enough?
> >
> > Well, if it automatically re-arranges itself according to my navigation,
> > it might work well enough. That means when I go from foo to bar, it
> > should be 1 keyboard-shortcut to go back to bar and the document list
> > should show that. Same thing for mouse-movement, 1 move + 1 click at
> > most to go back 1 edit position.
> I'm not convinced code navigation history (places visited via language support 
> features) and file navigation history (files visited via file switching or 
> opening) mixes well.

Hmm, do we talk about the same thing? 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

Afaik thats what we have in KDev3 as well. 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.

I don't necessarily need code-navigation-history, I think plain
file-history is fine for that. But edit-history would have quite some
benefits when working on larger files (like the svn plugin class).

> Eclipse/JDT (dunno about CDT) has both. But it keeps them seperately. You can 
> either chose to go back/forward between code navigation points or use a 
> keyboard shortcut to revisit files in a stack-like fashion (There was a nice 
> patch to KDevelop3 that did this, but, instructively, it was implemented with 
> a parallel history)

Hmm, seems I haven't dived into Eclipse enough yet. I almost always just
switch between files there.

> > > It actually scales and can additionally house many more actions than a
> > > dropdown list. (VCS actions, file actions, etc)
> >
> > Sorry, I think you lost me here, what do VCS actions do in a document
> > list. And what exact VCS actions do you mean?
> Well.. the document list is a list of files, and simple VCS actions 
> (checkin/checkout/diff/annotate, etc..)  are file-centric actions.

Oh, that. Yeah, of course that will happen :)


Be careful!  UGLY strikes 9 out of 10!

More information about the KDevelop-devel mailing list