Do i3 workspaces have to be linear?
Clash Royale CLAN TAG#URR8PPP
Currently the way i3 does workspaces, they're all linear 0-9. Under a normal workflow this typically means you have one workspace for browsing the web, and one for managing media, and messaging/chat .. etc.
Browsing for alternative ideas, I found this description for Enlightenment,
Enlightenment allows the user to have a grid of workspaces called virtual desktops. Switching between them is achieved by hurling the mouse cursor to the edge of the screen, at which the desktop appears to slide across to reveal the next. The maximum grid size is eight by eight desktops, and the user can have 32 grids (each with a different background), making 2048 total possible desktop spaces (users can enable a map of the desktops, in case they get lost, which is called the pager).
The desktop dragbar allows a desktop to be 'slid back' to reveal the desktop 'underneath'. The E team use the analogy of sheets of paper, stacked on top of each other, where the user can slide off a piece partially to reveal what's beneath.
I kind of like that philosophy. Normally for my projects, I need
- An editor for the front-end code (under a different repo)
- An editor for the back-end code (under a different repo)
- A database connection
- A browser, to view and research the project's problems.
In this sense, the linear organization of i3 doesn't make sense and this is really what I want. Is there anyway to get this out of i3?
I would rather think of Workspace 1 as "Project 1" and then go
- up to the browser
- left to the back-end of the project
- right to the front-end of the project
- down to my sql-client.
Some of them get a bit more complex. For example, I could see have left-left going to testing the back-end, and right-right go to the testing of the front end.
Is there any way to hack together a notion of a "project" which has different facets unique to it that I can access relative to the "project"?
desktop-environment i3 workspaces enlightenment
asked Dec 16 at 19:53
Evan Carroll
5,11794279
add a comment |
Currently the way i3 does workspaces, they're all linear 0-9. Under a normal workflow this typically means you have one workspace for browsing the web, and one for managing media, and messaging/chat .. etc.
Browsing for alternative ideas, I found this description for Enlightenment,
Enlightenment allows the user to have a grid of workspaces called virtual desktops. Switching between them is achieved by hurling the mouse cursor to the edge of the screen, at which the desktop appears to slide across to reveal the next. The maximum grid size is eight by eight desktops, and the user can have 32 grids (each with a different background), making 2048 total possible desktop spaces (users can enable a map of the desktops, in case they get lost, which is called the pager).
The desktop dragbar allows a desktop to be 'slid back' to reveal the desktop 'underneath'. The E team use the analogy of sheets of paper, stacked on top of each other, where the user can slide off a piece partially to reveal what's beneath.
I kind of like that philosophy. Normally for my projects, I need
- An editor for the front-end code (under a different repo)
- An editor for the back-end code (under a different repo)
- A database connection
- A browser, to view and research the project's problems.
In this sense, the linear organization of i3 doesn't make sense and this is really what I want. Is there anyway to get this out of i3?
I would rather think of Workspace 1 as "Project 1" and then go
- up to the browser
- left to the back-end of the project
- right to the front-end of the project
- down to my sql-client.
Some of them get a bit more complex. For example, I could see have left-left going to testing the back-end, and right-right go to the testing of the front end.
Is there any way to hack together a notion of a "project" which has different facets unique to it that I can access relative to the "project"?
desktop-environment i3 workspaces enlightenment
asked Dec 16 at 19:53
Evan Carroll
5,11794279
add a comment |
Currently the way i3 does workspaces, they're all linear 0-9. Under a normal workflow this typically means you have one workspace for browsing the web, and one for managing media, and messaging/chat .. etc.
Browsing for alternative ideas, I found this description for Enlightenment,
Enlightenment allows the user to have a grid of workspaces called virtual desktops. Switching between them is achieved by hurling the mouse cursor to the edge of the screen, at which the desktop appears to slide across to reveal the next. The maximum grid size is eight by eight desktops, and the user can have 32 grids (each with a different background), making 2048 total possible desktop spaces (users can enable a map of the desktops, in case they get lost, which is called the pager).
The desktop dragbar allows a desktop to be 'slid back' to reveal the desktop 'underneath'. The E team use the analogy of sheets of paper, stacked on top of each other, where the user can slide off a piece partially to reveal what's beneath.
I kind of like that philosophy. Normally for my projects, I need
- An editor for the front-end code (under a different repo)
- An editor for the back-end code (under a different repo)
- A database connection
- A browser, to view and research the project's problems.
In this sense, the linear organization of i3 doesn't make sense and this is really what I want. Is there anyway to get this out of i3?
I would rather think of Workspace 1 as "Project 1" and then go
- up to the browser
- left to the back-end of the project
- right to the front-end of the project
- down to my sql-client.
Some of them get a bit more complex. For example, I could see have left-left going to testing the back-end, and right-right go to the testing of the front end.
Is there any way to hack together a notion of a "project" which has different facets unique to it that I can access relative to the "project"?
desktop-environment i3 workspaces enlightenment
asked Dec 16 at 19:53
Evan Carroll
5,11794279
Currently the way i3 does workspaces, they're all linear 0-9. Under a normal workflow this typically means you have one workspace for browsing the web, and one for managing media, and messaging/chat .. etc.
Browsing for alternative ideas, I found this description for Enlightenment,
Enlightenment allows the user to have a grid of workspaces called virtual desktops. Switching between them is achieved by hurling the mouse cursor to the edge of the screen, at which the desktop appears to slide across to reveal the next. The maximum grid size is eight by eight desktops, and the user can have 32 grids (each with a different background), making 2048 total possible desktop spaces (users can enable a map of the desktops, in case they get lost, which is called the pager).
The desktop dragbar allows a desktop to be 'slid back' to reveal the desktop 'underneath'. The E team use the analogy of sheets of paper, stacked on top of each other, where the user can slide off a piece partially to reveal what's beneath.
I kind of like that philosophy. Normally for my projects, I need
- An editor for the front-end code (under a different repo)
- An editor for the back-end code (under a different repo)
- A database connection
- A browser, to view and research the project's problems.
In this sense, the linear organization of i3 doesn't make sense and this is really what I want. Is there anyway to get this out of i3?
I would rather think of Workspace 1 as "Project 1" and then go
- up to the browser
- left to the back-end of the project
- right to the front-end of the project
- down to my sql-client.
Some of them get a bit more complex. For example, I could see have left-left going to testing the back-end, and right-right go to the testing of the front end.
Is there any way to hack together a notion of a "project" which has different facets unique to it that I can access relative to the "project"?
desktop-environment i3 workspaces enlightenment
desktop-environment i3 workspaces enlightenment
asked Dec 16 at 19:53
Evan Carroll
5,11794279
asked Dec 16 at 19:53
Evan Carroll
5,11794279
asked Dec 16 at 19:53
Evan Carroll
5,11794279
asked Dec 16 at 19:53
Evan Carroll
5,11794279
asked Dec 16 at 19:53
Evan Carroll
5,11794279
5,11794279
add a comment |
add a comment |
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489372%2fdo-i3-workspaces-have-to-be-linear%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489372%2fdo-i3-workspaces-have-to-be-linear%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown