Experiment: Browser-like Tabs

David Nolden zwabel at googlemail.com
Mon May 31 12:55:44 UTC 2010


2010/5/31 Niko Sams <niko.sams at gmail.com>:
> On Sun, May 30, 2010 at 22:19, David Nolden <zwabel at googlemail.com> wrote:
>> This seems only useful when browsing, not when working,
> True.
>
>> 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.
> I don't know if such an automatism is a good idea, too much magic that isn't
> clear to the user.

Maybe, the best level of automatism is something one could evaluate
later. The important point is that both kinds of tabs should be usable
at the same time, as both have use-cases that are not covered by the
other tabs well. Also it would suck if we had one more _option_
regarding the UI behavior.




More information about the KDevelop-devel mailing list