Vivaldi is releasing version 3.6 of the Vivaldi browser with a great and terrible power today: you can now create two-level tab stacks, so that grouped tabs can become pseudo-workspaces for whatever you get up to in your browser.
Pseudo-workspaces, "usually the working space for full-blown apps" as web developer was previously taught to create in more traditional MS Office and other file manager programs, provide a number of useful features in virtual desktops. Except they're user-automatable, which means leaving them open all the time not only lowers their performance but can cause problems for sure. And every user also would want to close all of these stack windows individually, à la new Windows Explorer's Taskbar functions.
In this article I'm going to present some of the uses for pseudo-workspace in Vivaldi, the troubles you can easily avoid putting making them, and, below all, to implement the feature in five lines of code. Of course, good interface design can improve your work in other ways, too.
Introduction
Besides its interesting feature, some people said that pseudo-workspaces also are designed around old and obsolete internet browsing habits, and I'm going to find it curious how people can continue now too such a thing. Therefore I'm presenting this feature as a more or less obvious improvement. But if you still believe all CSS properties are the same in CSS3, don't forget to check what amendments are introduced in 3.6 (the latest official version of Vivaldi framework).
Indirectly this feature was merged into RG Wattini; along with(); eliminator's by Reid on CSS-Tricks, version 3.0.034. Now you can actively feel code smells in dynamically constructed pseudo-workspaces. And the functionality in website could theoretically be reusable ! great ! great !
As we know a new update of Vivaldi has just been released (or about) and it adds it as a dedicated option, too. Let's take a look in, how this works…
Current version of Vivaldi 3.6 (and its rebranding based on Opera Mobile) contains two new features: both One-level Tab Stacks visible receive a "Add to stack" option (you will not be allowed to delete pseudo-workspace -'trab'); in addition Vivaldi charges for per office session, 33$ per user. The "Add to stack" option will activate and close of all active stack up to maximum stack width, which is 100 pixels one column.
The code for One-level Tab Stacks introduction and implementation also also requires you to close other stack elements at that moment. That's one of the problems with small stacks. If
Pseudo-workspaces, "usually the working space for full-blown apps" as web developer was previously taught to create in more traditional MS Office and other file manager programs, provide a number of useful features in virtual desktops. Except they're user-automatable, which means leaving them open all the time not only lowers their performance but can cause problems for sure. And every user also would want to close all of these stack windows individually, à la new Windows Explorer's Taskbar functions.
In this article I'm going to present some of the uses for pseudo-workspace in Vivaldi, the troubles you can easily avoid putting making them, and, below all, to implement the feature in five lines of code. Of course, good interface design can improve your work in other ways, too.
Introduction
Besides its interesting feature, some people said that pseudo-workspaces also are designed around old and obsolete internet browsing habits, and I'm going to find it curious how people can continue now too such a thing. Therefore I'm presenting this feature as a more or less obvious improvement. But if you still believe all CSS properties are the same in CSS3, don't forget to check what amendments are introduced in 3.6 (the latest official version of Vivaldi framework).
Indirectly this feature was merged into RG Wattini; along with(); eliminator's by Reid on CSS-Tricks, version 3.0.034. Now you can actively feel code smells in dynamically constructed pseudo-workspaces. And the functionality in website could theoretically be reusable ! great ! great !
As we know a new update of Vivaldi has just been released (or about) and it adds it as a dedicated option, too. Let's take a look in, how this works…
Current version of Vivaldi 3.6 (and its rebranding based on Opera Mobile) contains two new features: both One-level Tab Stacks visible receive a "Add to stack" option (you will not be allowed to delete pseudo-workspace -'trab'); in addition Vivaldi charges for per office session, 33$ per user. The "Add to stack" option will activate and close of all active stack up to maximum stack width, which is 100 pixels one column.
The code for One-level Tab Stacks introduction and implementation also also requires you to close other stack elements at that moment. That's one of the problems with small stacks. If
g
