These notes are pretty much the same steps as the two extensions list, it's just that I had to collate them together because neither seems to list it fully in the proper order.
-
Install Synthwave ’84/Synthwave + Fluoromachine theme on VS Code (I used the Fluoromachine one)
-
Install Custom CSS and JS Loader
-
Command + Shift + P to open command palette > "Preferences: Open settings (JSON)"
-
Add to the settings object this key, and the value is an array containing the path to the CSS file for your extension. On a Mac it should be the following:
{
"vscode_custom_css.imports": [
"file:///Users/${username}/.vscode/extensions/${extension folder name}/${extensions css file name}.css"
]
}
So for Synthwave + Fluoromachine on my Mac it's:
{
"vscode_custom_css.imports": [
"file:///Users/katesmac/.vscode/extensions/webrender.synthwave-x-fluoromachine-0.0.9/synthwave-x-fluoromachine.css"
]
}
- Quit VS Code and go to terminal so we can restart it with proper Permissions
- Type
sudo chown -R $(whoami) PATH TO CODE
where PATH TO CODE is actually the file path, and you actually type${whoami}
as well
So I typed exactly:
sudo chown -R $(whoami) /Applications/Visual\ Studio\ Code.app/Contents/MacOS/Electron
- the back slashes in front of the space are important
6a. According to Custom CSS and JS Loader, if you are using 'Insiders Branch' then the VS Code file path might be: /Applications/Visual Studio Code - Insiders.app/Contents/MacOS/Electron
but idk what that means
-
Should prompt you for your password
-
Reopen VS Code
-
Command + Shift + P > "Reload Custom CSS and JS"
-
Restart VS Code one more time and hopefully you'll see the glow!
- SPECIAL NOTE: If Code complains about that it is corrupted, simply click “Don't show again”.
- NOTE: Every time after Code is updated, please re-enable Custom CSS.
- NOTE: Every time you change the configuration, please re-enable Custom CSS.
https://github.com/paulyc/vscode/compare/master...paulyc:paulyc/auto-sxf?expand=1
Well it's a start, I got rid of all the error messages and permissions issues anyway.
But I admittedly have no clue how to work this build system so I'm still trying to figure
out how to get it to load the CSS with no user intervention. But, as I facetiously noted before,
electron and its build system take up an absolutely absurd amount of RAM and I can't even have
Chrome or Firefox open when I build or it runs out of RAM so I've had enough of that for the day!
But, if anyone more familiar with node-on-the-desktop and better endowed with RAM knows any of those
magical incantations to keep the build process and the theme engine happy, im open to PRs,
or you can simply take what you want of my changes if theyll help. Little too wary of getting an
earful about somebody's sacred cow or CSRP or some kind of node-ecosystem-javascript-security stuff
I'm not getting paid nearly enough to listen to, so I'm not sure I really want to make a binary build
of this particular beast or try to support it at all, but if you like, have at it!
Not sure what's so bad about CMake that the world needs all of these awful RAM hogging GC languaged
build systems, I mean if you went back in time to 2000 and told them we'd be building desktop apps
written in JS with a build system written in JS they'd never have believed you, or indeed that such apps would build
or work at all. It's like autotools was so bad that everyone's still making up for lost time creating new build systems,
but "better than autotools" ain't saying much.