On Tue, May 18, 2010 at 00:38, Joern Konopka
<cldx3000@xxxxxxxxxxxxxx> wrote:
All he meant was that if an Application utilizes a GTKNotebook Widget for Tabs that could as well be interpreted as top-level Windows, those Applications should utilize a new type of Widget to expose the toplevel treatment of the Tabs to the system to distinguish it from Applications that use the GTKNotebook Widget for content that cannot stand on its own two feet, for example the Icons Tab in the Appearance Settings. The look and feel of the Tabs should remain the same, the true advantages are laid out on the Backend and will make it easier to adopt special treatments for Tabs where those are demanded.
aaahh.. refreshing. That helped like a glass of lemonade ;)
thanks
It made me think about how Tabs only got invented so people won`t overfill their Taskbar and didn't have to run 10 instances of a Browser at once. Still, a Website remains a Toplevel Document and it should be emphasized as such. Now ever since Dylan mentioned a GTKWidget that separates such Tabs from Content-specific Tabs it just struck me, why can't i select a Tab from AltTab if its in no way related to any other Document i have open. And since i really didn't have anything better to do and im really not the guy with words i made a Mockup for your enjoyment. Any feedback is much appreciated.
Your mockup looks cool.. does it suggest that the initial invocation of the window switcher doesn't take it to the previous window yet, instead focuses the current window to cycle the tabs in it?