https://perchance.org/list-management-plugin
Helper functions to add and remove children from a Perchance list.
My newer generators are not having their screenshots generated. https://perchance.org/perchance-object-reference
Though this one works somehow: https://perchance.org/list-management-plugin
They're using the same formatting and scripts for the page as all my others.
Currently it's quite fiddly, making sure all the keys/names arrays are up to date so it still functions as expected.
If it used a set and delete handler it could handle all that internally. Or if there was some special methods we could use like .addValue() and it would figure out what kind of value it is--property, node, function--and handle it correctly.
Of course, I'm working on a plugin now to handle this for people. 😜
There's a lot of stuff that becomes real fiddly to do because they are not iterable... that would be real easy to do if they were iterable. I believe there's a proxy "trap" for iterating over properties somewhere in there.
https://perchance.org/override-color-scheme-plugin
Override the device's colour scheme using existing styles.
Most likely SUPER not a priority. But you know me 😅
https://perchance.org/prompt-style-tester#edit
The "go" button updates the entire page. As the options are generated this means they are re-generated, which means the chosen option resets, and you can only ever test the top option: Painted Anime.
Simple fix though: put a div with an id around the generations, then update that div only. That's all that needs updating anyway.
As we have ignorePerchanceErrors() and clearPerchanceErrors(), seems fair to have this function too, for public use.
Would be useful to be able to see the images just in the page so we don't accidentally delete the wrong one, stuff like that. I know we can click on the link, but this would just be a nice feature to make it easier.
https://perchance.org/learn-perchance
A primer on how to code using the Perchance language. Learn as much as possible as quickly as possible.
Seems to be related to this: ___htmlToElements(). It takes a string which is the text, ignoring the fact that HTML entities are not normal characters and should not be interpreted as normal HTML. For example, <
will be interpreted as <
which can open a tag.
Example: https://perchance.org/qzi72h52te#edit
So if an element contains any perchance code, and HTML entities, the HTML entities are essentially lost and become real characters. Which isn't what you want if you're trying to present plain-text code to the user.
Definitely does not work as expected at least.
@wthit56
@lemmy.world