Experiment: Browser-like Tabs

[David Nolden]

This seems only useful when browsing, not when working, so it would be best
if we had two kinds of tabs: Working-tabs and browsing-tabs, where
browsing-tabs have your behavior, while working-tabs have the current
behavior. It should be easily possible to spawn a working-tab from a
browsing-tab, browsing-tabs should be uniquely marked (maybe a special
border and read-only), and we could even automatically spawn a browsing-tab
when the user uses navigation-shortcuts, and a working-tab when the user
tries to edit within a browsing-tab.

Greetings, David

Am 30.05.2010 20:32 schrieb "Niko Sams" <niko.sams at gmail.com>:

Hi,

When working with kdevelop I have always the problem that after some
time I loose the
overview over the opened files.
A possible solution to this might be to make the Tabs behave like we
know it from
web browsers:
(1) a normal click on a link navigates to the new url in the current tab
(2) entering a new url navigates to that url in the current tab
(3) opening a new tab is an explicit user action
(4) holding a shortcut (ctrl) an clicking a link opens a new tab and
navigates there to the the link url
(5) there can be two tabs with the same url opened

I implemented 1, 2, 3 and 5 in an experimental branch:
browser-like-tabs branch of:
http://gitorious.org/~nsams/kdevelop/nsams-kdevplatform
http://gitorious.org/~nsams/kdevelop/nsams-kdevelop
(use Window -> New Tab to create a new tab)

What do you think about it?

Niko

--
KDevelop-devel mailing list
KDevelop-devel at kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20100530/cb7a1e5d/attachment.html>