dannooppo

joined 4 months ago
[–] [email protected] 1 points 6 days ago* (last edited 6 days ago)

It's all about you learning how to tell the AI what you want. I've started using the prompt [brain] button on many of the generators (usually to the right of the prompt, below the [dice] button), essentially the AI-Text-plugin at work in the background. It creates a prompt from a few keywords you put in. I've learned that (English not being my native language) it simply does a better job than I will ever be able to.

Using this generator, no-style, 6 images, with the [brain] button I filled in:

Portrait photo of a very casual Caucasian female, plain Jane, unassuming, fairly triangular face with wider than normal cheek bones, somewhat pointy chin, regular shaped thin lips, blonde medium length straight bob-cut hair, little inquisitive frown on her forehead, positively Kirsten Dunst's younger sister.

And it generated this:

A very casual and unassuming Caucasian female with a touch of resemblance to a younger Kirsten Dunst. She has a fairly triangular face with distinctively wider than normal cheekbones that add a unique character to her visage. Her somewhat pointy chin is softened by the gentle curve of her jawline, and her regular shaped thin lips are parted slightly in a way that hints at a subdued smile or a contemplative thought. Her blonde hair is cut into a medium length bob, the straight strands grazing her chin and framing her face in a way that accentuates her delicate features. The most engaging element of her expression is the little inquisitive frown that furrows her forehead, suggesting a curiosity about the world around her. Her attire is simple and comfortable, blending into the background of the photo and allowing her natural beauty to take center stage. Her eyes, though not explicitly described in the prompt, one can't help but imagine, hold a spark of intelligence and a gentle warmth that would be quite captivating. The overall effect is one of understated elegance and approachability, leaving the viewer with the sense that she is someone who is both easy to talk to and full of hidden depths.

Without making any changes, you will get 'normal' lips (next to the dreaded supermodel lips, btw). Casual Photo works too, while Cinematic and Professional Photo will bring back the supermodel lips.

It's all a matter of fiddling and tweaking the prompt. Either by changing the [brain] input, or making slight changes to what it generated.

And I just noticed that Cursed Photo will yield a perfect Plain Jane

[–] [email protected] 2 points 1 month ago

Thanks for the input, but this is a Javascript coding issue inside the plugin(s), not directly related to Perchance syntax for creating generator lists.

[–] [email protected] 2 points 1 month ago* (last edited 1 month ago)

remember = true is not related to the remember-plugin but part of t2i-framework-plugin-v2. Basically both plugins save the value of a select to localStorage when activated and it can happen that one of the plugins has updated localStorage while the other hasn't (just yet). Especially when you close a generator before image/text generation has finished localStorage can (or may) contain two different values of the same select causing your issue. Depending on how you created the generator AND the order values get retrieved from localStorage it may SEEM that your generator suffers from dementia. You can (probably) resolve this by using either one, just not both 'remember' methods. I am still on the learning track, so don't ask me how to solve your specific problem. I need to figure out a lot more before ever being any use in that respect...

Off the bat I'd say don't use remember = true when you're using the remember-plugin.

 

Hi Perchance!

Trying to understand the inner workings of Perchance t2i-framework-plugin-v2 I cloned this plugin and added a few console.info() lines.

Especially in and around function updateInputVisibilities() (line 145+) to learn how userInputs[name] was set up.

Using my version of the t2i-framework plugin in a generator I saw in the console that on Generator pageload the function updateInputVisibilities() gets triggered by ___pageLoadHandler746291937() (which is to be expected, we need the elements set up), but also that ___selectElChangeEvent746291937() gets triggered for each <input>/<select>/<textarea> in the generated HTML.

In my case updateInputVisibilities() got triggered 21 times on Generator pageload instead of just once. The function gets triggered for each list/input used in the generator.

After some searching I found out that this is caused by the remember-plugin.

On Generator startup remember-plugin retrieves values from localStorage and updates the various input elements in the HTML, as to be expected. However, in doing so, it changes the element.value which in turn triggers the element.onchange event triggering ___selectElChangeEvent746291937(). While true, something has indeed changed, it is unwanted behaviour on pageload.

This little bug also unveiles that t2i-framework-plugin-v2 executes updateInputVisibilities() for each change in a single <select> updating all other selects as well.

I am still working my way into these two plugins, so I cannot exactly pinpoint what code needs to be changed. With just a few remembered inputs in localStorage it does little harm, but with large amounts of inputs, pageload time gets unnecessarily long.

My versions (for testing):

Be aware: when loading the generator for the first time with an empty localStorage nothing special will be noticed, however:

  • Change a few selects to fill localStorage
  • Clear the DevTools console to get rid of clutter
  • reload the generator => [Ctrl-F5]
  • Check the console info
  • Check if 'Danno Count' is >1
  • Filter console with 'trigger' to see the amount of ___selectElChangeEvent746291937() getting triggered
 

Hey everyone!! I'm a retired software engineer and the last few years I have gained a lot of knowledge about HTML/CSS automatic element scaling and responsive design in general. Been pretty busy on Stackoverflow and Codepen in that respect. I just love the perChance philosophy and what you people did with the place and I want to share my knowledge and start to maintain elaborate HTML/CSS/JS files on perChance (with all simple trickery) for everyone to use, starting with generic CSS and some JS convenient oneliner functions. MY QUESTION: what is the best way to store, import and access generic CSS (as well as HTML/JS) on perChance without having to copy content for each generator over and over again.

(I know and/or @import will work just fine, but I want to do it the 'proper perChance' way. I've been here for just a week, so gimme time to dive into the whole list and plugin sharing mechanism....)