custom CSS elevated to global scope to be effective in any workspace? #351
peterjosvai
started this conversation in
Ideas
Replies: 1 comment
-
|
There is an issue tracking this! #13 Definitely something that would be useful. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
hi,
Tangent's Custom CSS functionality is truly amazing! Especially with the CRTL+I "inspector" view...
This is so much better than theming!!! :)
But it is unfortunately limited to workspaces.
This is logical, and makes sense.
But a custom css could as well be picked to be elevated to "global" scope...
For this, only a Styles directory would be necessary, in the (Linux) $USER / config / Tangent dir...
Only a "make this (style sheet ) global" button would be needed -- as far as I can see :)
Once a custom style sheet is made global, it could be independent of the original My_Custom_Styles_num , i.e. copy and not symlink...
it could become the My_global_style_1.... or Global_styles_1
The point: if another style sheet gets "globalized" in another workspace, it shouldn't overwrite the previous one...
I know that people have learned to imagine more and more complexity all the time... while playing with any type of building bloc... thinking that more means better :)
Well, I don't think so! :)
In my opinion, the simpler the better.
But using a global style sheet instead of manually copying a custom style sheet... is actually simpler :) :)
Either way, have a good day!
Peter
Beta Was this translation helpful? Give feedback.
All reactions