SoylentNews is people
SoylentNews
from the why-not-beta-for-some-years-before-tossing-the-idea? dept.
For two periods last year, those using preview builds of Windows 10 could access to a feature called Sets: a tabbed interface that was eventually to allow tabs to be put in the titlebar of just about any window. These tabs would allow both multiple copies of the same application to be combined—a tabbed Explorer or Command Prompt, say—and multiple disparate windows to be grouped—combining, say, a browser window containing research with the Word window. However, both times the feature was enabled only for a few weeks, so Microsoft could gather data, before disabling it. Sets aren't in the Windows 10 May 2019 update.
The Shell-provided tab experience is no more, but adding tabs is high on our to do list.
— Rich Turner (@richturn_ms) April 20, 2019
It seems now that Sets are unlikely to ever materialize. Rich Turner, who oversees Microsoft's revamping of the Windows command-line infrastructure and the Windows Subsystem for Linux tweeted that the interface "is no more." Having everything tabbed everywhere isn't going to happen. Adding tabs specifically for command-line windows is, however, "high on [Microsoft's] to do list."
(Score: 3, Insightful) by DannyB on Wednesday April 24 2019, @07:18PM (3 children)
So what would a Microsoft implementation of a tabbed interface look like? Even if only for a command line window with tabs.
* tabs within tabs. Under one tab, there may be sub-tabs. And sub-sub tabs. Until you drill down to an actual command line.
* limits on number of tabs set by the license or activation code of the Windows OS. Users who get more benefit from tabs should have to pay for it.
* tabs should be highly permission restricted. Even command line access should have additional hoops to jump through. Command line users must have special role memberships, and other settings that are scattered among different parts of windows configuration dialog maze.
* tabs should require a complex configuration in order to setup properly. A configuration file that is XML with elements that contain YAML, with entries that contain JSON.
* if any process in a tab crashes, it should bring down the entire tabbed interface window of all tabs. Maybe even a blue scream of death.
* resizing of the command line window should have awkward effects on all embedded command lines within it
What am I missing?
Does marketing / management have any additional requirements? Like each tab should have a URL? And a UUID, just because, of, um . . . something.
To transfer files: right-click on file, pick Copy. Unplug mouse, plug mouse into other computer. Right-click, paste.
(Score: 4, Funny) by Snospar on Wednesday April 24 2019, @07:54PM
Nah, it will be a completely flat interface with no visual clue that multiple tabs exist at all. To switch to the correct tab you simply start typing something that you already typed in that tab and... you get the picture.
Huge thanks to all the Soylent volunteers without whom this community (and this post) would not be possible.
(Score: 2) by All Your Lawn Are Belong To Us on Thursday April 25 2019, @02:15PM (1 child)
There shall be no command line. It will be tabs all the way down, I tell you!
This sig for rent.
(Score: 3, Funny) by DannyB on Thursday April 25 2019, @05:21PM
The command line will be replaced by Windows 3.1 Program Mangler and File Mangler.
To transfer files: right-click on file, pick Copy. Unplug mouse, plug mouse into other computer. Right-click, paste.