Plans for Glasstron 2

[NyaomiDEV]

Glasstron 2.x will be made, sometime in the future (no ETA). Currently searching for other people willing to help, like it was done for Glasstron 1.x.

Main stuff I want to clarify here and now:

• The entire module will be rewritten to take advantage of modern ECMAScript conventions (ES6+) and it will be rewritten in TypeScript. As such, people using TS to develop will have correct type definitions and we are all happy.
• Avoiding prototype pollution as much as possible is the new goal. Glasstron will expose an API to which you will pass an already constructed Electron BrowserWindow. No new Glasstron.BrowserWindow() will survive. Hopefully this makes sense in everyone's head.
• macOS support will be dropped because it was only a wrapper that I used to get the last vibrancy mode set, but it turned out to be a pain to maintain and no one actually used it. Plus, developers who have to remember values can make their own functions to do so.
• Linux support will be dropped. It's useless to advertise Linux if there's only one configuration that works among countless ones, plus more code to maintain and easy spaghetti (see Linux code on Glasstron 1.x and try to figure out how it works before your brain melts away). Also, it has always been buggy, flickery and overall unreliable.
• Windows support is basically what Glasstron will be about. It will be rewritten with Windows 11 in mind first and foremost, but the main goal is to offer a consistent blur with the rest of the system. By this I mean, Windows 11 will have Mica blur; Windows 10, Acrylic blur; and Windows 7 (is that still around?) Aero blur. All of this will be handled by Glasstron 2 internally, and the developer will only have to call one function to toggle the blur on and off. Note that the usual Windows caveats could still apply (transparent has to be true; no Aero Snapping; Acrylic slowdown on mouse drag 'workarounds').

Glasstron 2 will be a "breaking update" on purpose. I made it with little to no Node/Electron knowledge and it shows. It is time to give people a proper module.

Future plans will probably be reimplementing blur in Plasma and in GNOME to get "on par" with Glasstron 1, but it is not top priority since there's still no way (to my knowledge) to talk to the Wayland compositor from external modules that run in Electron's "main" context.

Naomi, now that you announced plans for Glasstron 2, will Glasscord 2 ever be a thing?

The official answer is nope.
The not-so-official answer is "with proper funding". I miss having Discord look consistent with my setup, too; but it is a burden I don't want to replicate all alone and with basically no time at disposal if there's no gain nowhere, since I am still a student.

[NyaomiDEV]

Screw it.