History Navigation Proposal by Alexander

Hi,

on behalf of Alexander I present his proposals for history
navigation in
Kdevelop4:

The Task
-------------
Let's imagine we have KDevelop with two split views. In each
view user opened several files. Current state of the screen
is: 
---------------------------
|  file3.cpp |  file4.cpp |
|            |            |
|            |            |
---------------------------

Files previously opened in views are: 
  left view:    | right view:
  1. file1.cpp  | 2. file2.cpp
  3. file3.cpp  | 4. file4.cpp

Numbers near the filenames indicate the order in which user
opened the files. 
This means the user: 
 opened file1.cpp 
 split the screen and opened file2.cpp 
 got back to the first view and opened file3.cpp 
 switched to the last view and opened file4.cpp 
Currently focus is in file4.cpp editor. 
Also let's assume Alt-Up/Down keys traverse the history
Back/Forward 

Proposals
----------------
v.1 In-View History Navigation 
   Back: show file2.cpp 
   Forward: show file4.cpp 
v.2 Global History Navigation With Switching 
   Back: switch to left view + focus file3.cpp 
   Back: switch to right view + show file2.cpp 
   Back: switch to left view + show file1.cpp 
   Forward: switch to right view + focus file2.cpp 
   Forward: switch to left view + show file3.cpp 
   Forward: switch to right view + show file4.cpp 
v.3 Global In-View History Navigation 
   Back: show file3.cpp 
   Back: show file2.cpp 
   Back: show file1.cpp 
   Forward: show file2.cpp 
   Forward: show file3.cpp 
   Forward: show file4.cpp

Please comment.

Andreas

-- 
If you stand on your head, you will get footprints in your
hair.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 10.06.07 16:23:22, Andreas Pakulat wrote:
> Proposals
> ----------------
> v.1 In-View History Navigation 
>    Back: show file2.cpp 
>    Forward: show file4.cpp 

This one is really simple, however I need 2 different key
combos to go
to file1.cpp. So I don't like that that much.

> v.2 Global History Navigation With Switching 
>    Back: switch to left view + focus file3.cpp 
>    Back: switch to right view + show file2.cpp 
>    Back: switch to left view + show file1.cpp 
>    Forward: switch to right view + focus file2.cpp 
>    Forward: switch to left view + show file3.cpp 
>    Forward: switch to right view + show file4.cpp 

Too complicated and probably going to be a usability
nightmare due to
the focus switching. There are no focus indicators at the
moment, except
the blinking cursor which is hard to see already for people
with 100%
sight.

> v.3 Global In-View History Navigation 
>    Back: show file3.cpp 
>    Back: show file2.cpp 
>    Back: show file1.cpp 
>    Forward: show file2.cpp 
>    Forward: show file3.cpp 
>    Forward: show file4.cpp

This is what kate does and IMHO is a good compromise between
simplicity
and not having to hit multiple combo's in the right order to
get where
one wants.

So, my vote is for v.3.

Andreas

-- 
You are sick, twisted and perverted.  I like that in a
person.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Sunday 10 Jun 2007 7:53:22 pm Andreas Pakulat wrote:
> on behalf of Alexander I present his proposals for
history navigation in
> Kdevelop4:
>
> The Task
> -------------
> Let's imagine we have KDevelop with two split views. In
each view user
> opened several files. Current state of the screen is:
> ---------------------------
>
> |  file3.cpp |  file4.cpp |
>
> ---------------------------
>
> Files previously opened in views are:
>   left view:    | right view:
>   1. file1.cpp  | 2. file2.cpp
>   3. file3.cpp  | 4. file4.cpp
>
> Numbers near the filenames indicate the order in which
user opened the
> files. This means the user:
>  opened file1.cpp
>  split the screen and opened file2.cpp
>  got back to the first view and opened file3.cpp
>  switched to the last view and opened file4.cpp
> Currently focus is in file4.cpp editor.
> Also let's assume Alt-Up/Down keys traverse the history
Back/Forward
>
> Proposals
> ----------------
> v.1 In-View History Navigation
>    Back: show file2.cpp
>    Forward: show file4.cpp
> v.2 Global History Navigation With Switching
>    Back: switch to left view + focus file3.cpp
>    Back: switch to right view + show file2.cpp
>    Back: switch to left view + show file1.cpp
>    Forward: switch to right view + focus file2.cpp
>    Forward: switch to left view + show file3.cpp
>    Forward: switch to right view + show file4.cpp
> v.3 Global In-View History Navigation
>    Back: show file3.cpp
>    Back: show file2.cpp
>    Back: show file1.cpp
>    Forward: show file2.cpp
>    Forward: show file3.cpp
>    Forward: show file4.cpp
>
> Please comment.

Personally i would prefer V2. It is what would be most
useful when using the 
history to move back and forth between 2 files when i need
one for reference 
while coding the other. I know just plain split view can
help in this case 
but depending on the resolution and use case, splitting
could severely limit 
the view area of each file.
-- 
Cheers!
kitts

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 10.06.07 20:21:29, kitts wrote:
> On Sunday 10 Jun 2007 7:53:22 pm Andreas Pakulat
wrote:
> > Proposals
> > ----------------
> > v.1 In-View History Navigation
> >    Back: show file2.cpp
> >    Forward: show file4.cpp
> > v.2 Global History Navigation With Switching
> >    Back: switch to left view + focus file3.cpp
> >    Back: switch to right view + show file2.cpp
> >    Back: switch to left view + show file1.cpp
> >    Forward: switch to right view + focus
file2.cpp
> >    Forward: switch to left view + show file3.cpp
> >    Forward: switch to right view + show file4.cpp
> > v.3 Global In-View History Navigation
> >    Back: show file3.cpp
> >    Back: show file2.cpp
> >    Back: show file1.cpp
> >    Forward: show file2.cpp
> >    Forward: show file3.cpp
> >    Forward: show file4.cpp
> >
> > Please comment.
> 
> Personally i would prefer V2. It is what would be most
useful when using the 
> history to move back and forth between 2 files when i
need one for reference 
> while coding the other. I know just plain split view
can help in this case 
> but depending on the resolution and use case, splitting
could severely limit 
> the view area of each file.

If you use only 1 view all 3 ways are the same.

Andreas

-- 
This life is yours.  Some of it was given to you; the rest,
you made yourself.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Sunday 10 Jun 2007 8:42:28 pm Andreas Pakulat wrote:
> > Personally i would prefer V2. It is what would be
most useful when using
> > the history to move back and forth between 2 files
when i need one for
> > reference while coding the other. I know just
plain split view can help
> > in this case but depending on the resolution and
use case, splitting
> > could severely limit the view area of each file.
>
> If you use only 1 view all 3 ways are the same.

Sorry, i think i am a little confused. Does a split cause
even the tab bar to 
split? Last i remember, the split occurred within a tab.
-- 
Cheers!
kitts

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Jun 10, 2007, at 9:23 AM, Andreas Pakulat wrote:

> Hi,
>
> on behalf of Alexander I present his proposals for
history  
> navigation in
> Kdevelop4:
>
> The Task
> -------------
> Let's imagine we have KDevelop with two split views. In
each view  
> user opened several files. Current state of the screen
is:
> ---------------------------
> |  file3.cpp |  file4.cpp |
> |            |            |
> |            |            |
> ---------------------------
>
> Files previously opened in views are:
>   left view:    | right view:
>   1. file1.cpp  | 2. file2.cpp
>   3. file3.cpp  | 4. file4.cpp
>
> Numbers near the filenames indicate the order in which
user opened  
> the files.
> This means the user:
>  opened file1.cpp
>  split the screen and opened file2.cpp
>  got back to the first view and opened file3.cpp
>  switched to the last view and opened file4.cpp
> Currently focus is in file4.cpp editor.
> Also let's assume Alt-Up/Down keys traverse the history
Back/Forward
>
> Proposals
> ----------------
> v.1 In-View History Navigation
>    Back: show file2.cpp
>    Forward: show file4.cpp
> v.2 Global History Navigation With Switching
>    Back: switch to left view + focus file3.cpp
>    Back: switch to right view + show file2.cpp
>    Back: switch to left view + show file1.cpp
>    Forward: switch to right view + focus file2.cpp
>    Forward: switch to left view + show file3.cpp
>    Forward: switch to right view + show file4.cpp
> v.3 Global In-View History Navigation
>    Back: show file3.cpp
>    Back: show file2.cpp
>    Back: show file1.cpp
>    Forward: show file2.cpp
>    Forward: show file3.cpp
>    Forward: show file4.cpp
>
> Please comment.
>
> Andreas
>

My vote is for v1. It's the simplest of the bunch and it's
probably  
best if we keep things simple.
--
Matt



_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Jun 10, 2007, at 9:44 AM, Andreas Pakulat wrote:

> On 10.06.07 16:23:22, Andreas Pakulat wrote:
>> Proposals
>> ----------------
>> v.1 In-View History Navigation
>>    Back: show file2.cpp
>>    Forward: show file4.cpp
>
> This one is really simple, however I need 2 different
key combos to go
> to file1.cpp. So I don't like that that much.

like one more key combination is going suddenly make your
brain  
explode? ;) Is the use of 2 different key combinations the
only  
reason you oppose this?

>> v.2 Global History Navigation With Switching
>>    Back: switch to left view + focus file3.cpp
>>    Back: switch to right view + show file2.cpp
>>    Back: switch to left view + show file1.cpp
>>    Forward: switch to right view + focus file2.cpp
>>    Forward: switch to left view + show file3.cpp
>>    Forward: switch to right view + show file4.cpp
>
> Too complicated and probably going to be a usability
nightmare due to
> the focus switching. There are no focus indicators at
the moment,  
> except
> the blinking cursor which is hard to see already for
people with 100%
> sight.
>

Agreed.

>> v.3 Global In-View History Navigation
>>    Back: show file3.cpp
>>    Back: show file2.cpp
>>    Back: show file1.cpp
>>    Forward: show file2.cpp
>>    Forward: show file3.cpp
>>    Forward: show file4.cpp
>
> This is what kate does and IMHO is a good compromise
between  
> simplicity
> and not having to hit multiple combo's in the right
order to get where
> one wants.
>
> So, my vote is for v.3.
>
> Andreas

And it's one of the reasons I don't use kate's split view.
If I were  
to use history, i'd want to have per view history, which is
what I  
get with v1, rather than all the files i've ever opened
history.
--
Matt



_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 10.06.07 20:51:42, kitts wrote:
> On Sunday 10 Jun 2007 8:42:28 pm Andreas Pakulat
wrote:
> > > Personally i would prefer V2. It is what
would be most useful when using
> > > the history to move back and forth between 2
files when i need one for
> > > reference while coding the other. I know just
plain split view can help
> > > in this case but depending on the resolution
and use case, splitting
> > > could severely limit the view area of each
file.
> >
> > If you use only 1 view all 3 ways are the same.
> 
> Sorry, i think i am a little confused. Does a split
cause even the tab bar to 
> split? Last i remember, the split occurred within a
tab.

This is for KDevelop4, not KDevelop3. And there's no tabbar
in
KDevelop4.

Andreas

-- 
You'll wish that you had done some of the hard things when
they were easier
to do.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 6/10/07, Matt Rogers <mattrkde.org> wrote:
> >> v.2 Global History Navigation With Switching
> >
> > Too complicated and probably going to be a
usability nightmare due to
> > the focus switching. There are no focus indicators
at the moment,
> > except
> > the blinking cursor which is hard to see already
for people with 100%
> > sight.
> Agreed.

Now imagine we have better indication of where the cursor
is. It's not
so hard to implement - just highlight the status/title bar
of the
current editor view. What would you think then?

> And it's one of the reasons I don't use kate's split
view. If I were
> to use history, i'd want to have per view history,
which is what I
> get with v1, rather than all the files i've ever opened
history.

The problem is that with v1 you have to keep the list of
opened files
in the view both in the UI and in your mind. That list is
usually tabs
in the UI and tabs... well.. don't scale ;)

IMHO if we are to avoid tabs, we need to avoid the
"list of opened
files in this view" too. Because once we remove tabs,
we remove the
last visible clue about opened files in the view.

File list will not help here much because it can list only
all opened
files, not the ones in the split view.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 6/10/07, kitts <kitts.mailinglistsgmail.com> wrote:
> Sorry, i think i am a little confused. Does a split
cause even the tab bar to
> split? Last i remember, the split occurred within a
tab.
In KDevelop3 - yes if you use SimpleIdeal mode's splitting
and not C++
header/source splitting.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel