Hi there,
Since @[email protected] was OK with bugging them with features, I’ll seize the opportunity. Previously, I’ve published the list with improvements earlier (https://lemmy.world/post/17986442), which was received well, but I see how it can be overwhelming. I wasn’t sure if it was a good idea to continue posting in that thread or make new one, so I’m making a new one. Feel free to merge threads if forum staff deems this necessary.
I picked a few low-effort features out of that list which I think could be considered essentials, and which would be great to see pushed upward in your TODO list, namely:
Prompting
- Introduce copy button in prompt and anti prompt fields for better UX on mobile (click to copy). Though, since I do not own any generators, I’m not sure if this is something that generator owner could do on their own?
Gallery
- On mobile, thumbs up and thumbs down buttons on images in the gallery should show up without having to tap on an image to reveal these buttons to make it easier for people to upvote or downvote.
- Implement search/filter in galleries (at least most simplistic, regex-based search by prompt and saveTitle/saveDescription). If you rather not touch database at all at this point, since prompt is stored in HTML after an image is generated, could be a simple JS script that searches within image containers as a starter. Users could manually load gallery pages they wish to search in. Though, is this also something that the owner of the generator could potentially cook up on their own?
- Store the galleries that the user visited earlier in local storage, so it is easier to switch between them when saving or browsing. The galleries could be presented as dropdown listed sorted alphabetically ascending.
Two items from that list are potentially the ones that can be implemented by generator owners, please enlighten me if this is the case - I’ve seen some very fancy looking generators, but wasn’t sure if most of it is just CSS. Thank you, and looking forward - it’s always cool to see Perchance evolving!
True with the iframes. However, once the image is in the gallery, it is just a
div. Prompt lives inside adiv.image-desc, intitleattribute. One could write very basic search engine that parses all such divs, tokenizes tags and filters out what user is looking for.But the gallery is inside an iframe. You can’t style stuff inside an iframe from outside an iframe, and scripting from outside the iframe is blocked because of the different subdomain–that’s what I was saying.
Ouch, my bad I never noticed this. Thank you for clarification!