death.crafter wrote: ↑April 4th, 2022, 10:30 pm
Actually there is an interface for interacting with Rainmeter. But since it's incomplete and can change khan hasn't documented it yet. All you can do for now is look at the code that covers the javascript interface. Also, you can just run a local server using Node and disable CORS for local host. But yeah, it's a pain for only running a skin.
Anyways, glad you got it working.
Yep, I'll play with the things I can play for the moment and wait for the plugin to evolve and mature in terms of abilities - hopefully it will turn up well, because what it can do so far with minimal performance impact is impressive - and you don't even need a low update to do it. It's you I have to thank for letting me know of the alternative I had, this one is much more compact and performance friendly than what I had in mind, but you know, one only works with the tools at his disposal or that he knows of.
Nice to know that both interaction with Rainmeter and other minor drawbacks are worked on, but IMHO the CORS thingy is a problem, especially for regular users who might either not know or not want to use such workarounds, not to mention depending on being online if one wants to use a non-local URL. Personally, I tried to use a image data URL to bypass CORS and it worked, but dealing with such long strings reminds me of my previous idea, plus, the image itself is not the same as the original after encoding.
I'll continue to experiment with it, but I can already say that it looks to be the winner choice in my case, bar the inconveniences. Thanks again for the idea, you just "crafted" saving GBs of drive space for me on this one, LOL. Let's hope Brian and khansas can eventually add this to Rainmeter the proper way, so more users will benefit from it.
P.S. Also, it would be nice to make triggering the Edge context menu optional, because it's a good way to verify if the HTML / Javascript works via Inspect.