KDE/kdevplatform/shell
Andreas Pakulat
apaku at gmx.de
Sun Nov 9 19:29:26 UTC 2008
On 08.11.08 23:59:07, Alexander Dymo wrote:
> On Saturday 08 November 2008 17:41:17 Niko Sams wrote:
> > What about dropping this "open files" idea completely? We have quickopen,
> > we have a Context-Browser "back" action and we could probably have a
> > recently opened
> > files list. There could also be favorite files list - so you can mark
> > the files your are working on.
> >
> > Internally the latest files can still left open (faster).
> > Files with unsaved changes also must stay opened.
>
> I also support this idea and here's why:
>
> In KDevelop we support several usecases for "opened" files which we can
> continue to support without a concept of "opened" file.
>
> 1) files from project which you work on
> -> present solution: "quick open opened files" (+tabs)
> -> possible solution: just regular "quick open file"
I thought the separate action has already been removed because the normal
quick-open-file list already contains a special icon for already-opened
files (and lists them at the top).
> ==================
>
> On tabs:
> Let's stop thinking about tabs and its problems for now, but think instead
> about usecases.
>
> My usecase for tabs is following:
...
> ==================
> Please share your usecase for tabs and let's think if we can cover all of
> these without tabbed interface.
<None>
Sorry, I have absolutely 0 use for tabs currently. Ever since Jens brought
me to try kdev3 without tabs I don't need really need them anymore :)
Oh, or maybe one thing: To actually see where I'm switching to when using
<file-forward-navigation>/<file-backward-navigation> shortcuts, so I can
quickly hit them thrice to go three files forward/backward. Or with a very
long list of files, even use the keyboard-repeating.
So for me Alex option 2) would work perfectly as well (and would mean I'd
really have no use for tabs).
Andreas
--
You will be run over by a beer truck.
More information about the KDevelop-devel
mailing list