hamcha/faulty.equipment
1
0
Fork 0
Code Activity Actions

onshape has dark mode!
All checks were successful
Deploy to Artifacts / deploy (push) Successful in 13s
Details

Browse source
This commit is contained in:
Hamcha 2024-10-09 00:50:52 +02:00
parent 668f6e7de9
commit b954afdd3a
Signed by: hamcha
GPG key ID: 1669C533B8CF6D89
2 changed files with 4 additions and 74 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
content/posts/cad-shootout-onshape.md
View file

@ -45,12 +45,11 @@ As Onshape was created by ex-Solidworks engineers (including the legendary Jon H
### Dark Mode
There is no officially supported dark mode, but being a browser app you can use browser extensions to inject custom CSS. [Dark Reader](https://darkreader.org/) works fine but there are many weird gotchas like material colors and the shading being inverted (shadows are bright and reflections are dark, etc.)
~~There is no officially supported dark mode, but being a browser app you can use browser extensions to inject custom CSS.~~
DaviDokuro made a userscript that adds enough CSS to have a proper Dark mode ([DaviDokuro/Unofficial-Onshape-Dark-Theme](https://github.com/DaviDokuro/Unofficial-Onshape-Dark-Theme)). I modified it somewhat to fix some stuff, so also check out [my version](https://gist.github.com/Hamcha/690e1be79aa72816566b8e5364ab6e3f).
This is what it looks like:
![Onshape UI with the unofficial dark theme](/media/onshape/onshape-dark.png)
{{< update "2024-10-09" >}}
There is now a experimental "Dark mode" option in Onshape, and it looks pretty much the same as the add-on I recommended, so this section is pretty much void now.
{{</ update >}}
Even thought it doesn't look great and sexy I have been using it and will use it for the examples shown below, so apologies if you're a light mode fan but at least you won't get flashbanged.

69
content/posts/tgstation-roles.md
View file

@ -1,69 +0,0 @@
---
title: "Thoughts on /tg/station roles"
date: 2022-06-27T17:02:09+02:00
draft: true
---
This is a long winded post full of personal rants, if you want the short version:
{{< tldr >}}
I think Viro and Geneticists are bad roles as they should be reworked from the ground up to be less isolated and less "click on window and hope the RNG doesn't hate you"
{{< /tldr >}}
Do you have no clue what that was about? Cool, keep reading!
<!--more-->
## PREFACE: Space Station 13
_TODO: EXPLAIN SS13 IN A PARAGRAPH SOMEHOW_
### PREFACE act 2: /tg/station is a game design trial by fire
SS13 is an incredibly complex game, providing emergent gameplay in a multiplayer settings with constant changes and many communities testing different things.
With the same people playing for upwards of decades with very fast iterations (the average round on my preferred /tg/station server is ~45 minutes), players will generally react strongly to changes and when given the opportunity and test the limit of every new mechanic as soon as it is introduced.
Any new design has to account for weird interactions with the existing 9999 systems, exploits that might be found, [playerbase anger](https://hackmd.io/@tgstation/HJCoL8MUw#Ethical-and-Moral-Considerations-to-Avoid-Angering-Players) and cannot rely on secrets as the code is public.
I believe this to be an incredibly tricky environment but with opportunity to foster truly unique experiences. For coders, Space Station 13 is an incredible sandbox in which you can sneak your passions for everyone to poke at. For players, mechanics can be something to explore, just pass the time or can even become a story device.
## The roles
_TODO_
### Note on personal experience and role omissions
_TODO_
### Function vs Roleplay
_TODO_
### What makes a good functional role
_TODO_
### Good functional roles
_TODO_
#### Chemist
_TODO_
#### Engineering (Station engineer, Atmos Tech)
_TODO_
### Bad functional roles
_TODO_
### How RP level affects roles
_TODO_
## Closing notes
_TODO_