History Navigation Proposal by Alexander

[kitts]

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