This could give the ability for devs to have a cleaner, more readable way to write scheme files.
If this idea gets rejected, I’m willing to make a transpiler (from CSS - or muxcss - to .ini) instead, so it can stay a community tool and nothing else.
2 Likes
What? Why?
While I can see where you’re coming from with wanting a more structured or familiar format like CSS, this is something we’re not going to implement, this is not web development.
The main reason is that introducing a CSS-like format adds unnecessary complexity for both users and developers. While you might be comfortable with CSS, most users (and even some contributors) are familiar with the simplicity of INI files. INI uses a straightforward Header > Key = Value structure that is easy to read, edit, and, importantly, parse directly in C with very minimal overhead.
Switching to (or even supporting) CSS-formatted schemes would mean introducing a new parser or additional tooling, which increases maintenance burden and makes things more complicated for very little real benefit. INI keeps things simple and accessible to a broader audience.
If you’re still interested in writing a tool or “transpiler” as a personal project, go for gold! As far as the official standing goes, INI will remain the standard.
3 Likes