This is a Lemmy Community for perchance.org, a platform for sharing and creating random text generators.
Feel free to ask for help, share your generators, and start friendly discussions at your leisure :)
This community is mainly for discussions between those who are building generators. For discussions about using generators, especially the popular AI ones, the community-led Casual Perchance forum is likely a more appropriate venue.
See this post for the Complete Guide to Posting Here on the Community!
1. Please follow the Lemmy.World instance rules.
2. Be kind and friendly.
3. Be thankful to those who try to help you.
4. Only post about stuff related to perchance.
5. Refrain from requesting Prompts for the AI Tools.
text-to-image-plugin and ai-text-plugin) e.g. "What is the good prompt for X?", "How to achieve X with Y generator?"6. Search through the Community Before Posting.
Also, would be useful for things like having $output be a function. But give it properties also. Unsure how to do that currently. ...Though, also not sure if this $onload() thing would let that work anyway.
Any advice on doing this? @[email protected]
having $output be a function. But give it properties also
It's hacky, but I do that like this:
$output = [getPlugin()]
getPlugin() =>
if(!window.__fooPluginFn) {
function foo(a, b, c) {
// the actual plugin code
}
foo.prop = "blah";
foo.anotherProp = 123;
window.__fooPluginFn = foo;
}
return window.__fooPluginFn;
I have thought about something like $onLoad before, but there were some complications. Currently the lists panel is purely "declarative" (loosely speaking, in the sense that no state is altered during parsing/init) and all actual execution is done via calls from the HTML panel. It's definitely possible to have something like $onLoad but it does lead to a few extra "if/thens" that devs need to keep in their mind when importing something, and I'd need to change some ~deep-ish engine code. When I've had this need in the past I also noticed that I sometimes wanted it to only run if it was a direct import - i.e. not an import of an import. So there are a few DX questions there too. For now I think this one is further down the todo/to-think-about list, since it's pretty easy to just add [yourPlugin({init:true})] to the top of the HTML panel.
I see. So is that only run once, to store it in the local list-variable by the user? That's an interesting way to do it. And lets us add properties... but that would only work after it's accessed? Or could the user do [plugin.prop] and it would work as the first code block?
So is that only run once
Ah, no, good catch - that would have re-run every time. I've updated the code above to fix that.
could the user do [plugin.prop]
Yep, $output will resolve to window.__fooPluginFn which is the foo function, so if you've got fooPlugin={import:foo-plugin} then you can write fooPlugin.prop immediately and it'll work fine.
Cool 👍
Basically, an $onload function to be called like that automatically would be all it takes, I think. I don't think I've seen the actual importing code, but presumably it injects stuff into the top-level page or something. At which point it could call the onload maybe?
A simple, practical approach (for now) would be to put the function inside the $output() like this:
$output() =>
if (!window.__onloadExecuted) {
onload(); window.__onloadExecuted = true;
}
// ...
// The homemade onload function
onload() =>
// ...
However, it only works when at least one instance of the plugin is being executed in the generator code.
Yes, that's exactly what I do--and exactly why I'm making this request.