this post was submitted on 26 Jul 2024
3 points (100.0% liked)

Perchance - Create a Random Text Generator

448 readers
17 users here now

⚄︎ Perchance

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!

Rules

1. Please follow the Lemmy.World instance rules.

2. Be kind and friendly.

  • Please be kind to others on this community (and also in general), and remember that for many people Perchance is their first experience with coding. We have members for whom English is not their first language, so please be take that into account too :)

3. Be thankful to those who try to help you.

  • If you ask a question and someone has made a effort to help you out, please remember to be thankful! Even if they don't manage to help you solve your problem - remember that they're spending time out of their day to try to help a stranger :)

4. Only post about stuff related to perchance.

  • Please only post about perchance related stuff like generators on it, bugs, and the site.

5. Refrain from requesting Prompts for the AI Tools.

  • We would like to ask to refrain from posting here needing help specifically with prompting/achieving certain results with the AI plugins (text-to-image-plugin and ai-text-plugin) e.g. "What is the good prompt for X?", "How to achieve X with Y generator?"
  • See Perchance AI FAQ for FAQ about the AI tools.
  • You can ask for help with prompting at the 'sister' community Casual Perchance, which is for more casual discussions.
  • We will still be helping/answering questions about the plugins as long as it is related to building generators with them.

6. Search through the Community Before Posting.

  • Please Search through the Community Posts here (and on Reddit) before posting to see if what you will post has similar post/already been posted.

founded 1 year ago
MODERATORS
eatham
[email protected]
VioneT
perchance
3
Blocking Update for code (self.perchance)
submitted 3 months ago by wthit56 to c/perchance
8 comments fedilink hide all child comments
 

Maybe there's some way of doing this, not sure. But if you've got some function that returns HTML, and use it like [fn()] in your HTML, then use update(), that function will be called again, right? There's no way of blocking that, as far as I know--which could do things like reset state and such.

Not even sure how you'd implement such a feature. Maybe pass an argument to the function telling it it's updating or something? Or mark the code as only-run-once somehow? [:code run once]? Not sure... Could be useful for certain plug-ins though to avoid users of the plugin accidentally messing it up by using update().

you are viewing a single comment's thread
view the rest of the comments
[–] VioneT 1 points 3 months ago (1 children)

Yup, a good example of it is the tap-plugin, different outputs but is remembered by the page.

[–] wthit56 1 points 3 months ago (1 children)

Ooh, an interesting plugin! It doesn't work in the way I'm talking about at all though.

The function would need to be able to generate some return value when called. But always return that same return value for that source call every time, so that when update() is called on an element that contains code that calls the function... it's as if that code block was not re-evaluated at all.

That tap plugin specifically does not use update() at all. And specially does generate new values when it's interacted with. I'm not sure how it's relevant. Maybe you could point me to the part you think is doing what I'm talking about?

[–] VioneT 2 points 3 months ago (1 children)

Maybe the locker-plugin might be a better example. It essentially stores the 'locked' value, so when update() is used, it would only return the 'locked' value.

[–] wthit56 2 points 3 months ago

Ah I see, that seems to work about as expected. Only annoyance is, the user of the plugin has to come up with a unique name and track those, make sure they don't use the same name twice or whatever.

This method would work, which is cool. I still feel like it would be a useful feature for the engine anyway. If only to save on processing those code blocks that the user only wants to "run once."