rewbs / sd-parseq

Parameter sequencer for Stable Diffusion
https://sd-parseq.web.app/
MIT License
361 stars 39 forks source link

Feature request: Storing documents on a local environment option (no Firebase) #126

Open verybluebot opened 1 year ago

verybluebot commented 1 year ago

Adding on option to save the document with a custom name locally.

From what I saw at the moment (using v0.1.57) you are storing in indexDB the current document and you can access you older ones only with Revert in the UI which is basically pulling from parseqVersions under parseqDocs.

Would be nice if there would be a button for Save or Save Local that would add the document in a new entry under parseqDocs

So you could manage your docs with names instead of using Revert

Also adding a Delete button again helping you managing better your docs.

For me personally I prefer using it locally and I don't need thousends of document. The way I'm using Parseq is testing around until Im satisfied with the document result then re using it over and over using the initial template.

Opened an issue as a request but would gladly do it myself. Just wanted to check if this is a desired direction before start working on a PR

As commented on Youtube, This project is incredible Brilliant work

rewbs commented 1 year ago

Hi! Thanks for taking the time to write this up.

I have a few questions to make sure I understand what you want to do:

Would be nice if there would be a button for Save or Save Local that would add the document in a new entry under parseqDocs

Have you tried the new "Clone current document" option in the "New..." dialogue? It creates a new document from the current version of the active document.

image

Additionally, if you want to create a new document from an older version of a document without reverting, you can go to the Browser, click on the versions of the doc you're interested in, find the desired version in the table, and click clone:

image

I think these two features do what you're asking for. If not, could you elaborate on the difference you'd like to see?

Also, the subject mentions:

Storing documents on a local environment option (no Firebase)

Note that All documents are stored locally – indexeddb is fully local. The only case data is uploaded is if you explicitly upload via the share button or when uploading rendered manifests. Aside from that, all versions of all your documents are local.

rewbs commented 1 year ago

Also adding a Delete button again helping you managing better your docs.

You can delete whole documents under the version list (see screenshot above). Is that what you want?

(Or do you mean deleting individual versions? That's not available yet but you can run clean DB under Manage Database in the browser, which will reduce all documents to 65 versions max. If you'd like to be able to delete specific versions let me know.)

verybluebot commented 1 year ago

Oh sorry sorry sorry! I forgot was running Parseq not on 3000 last couple of days (3000 used for other day to day dev env's)

So suddenly all my template dos disappeared from the Load New option and surely under name in indexDB there was only the current doc.. I ran it on :3000 and now all of my docs there.

Sorry silly mistake.

About the delete, yes would be nice to be able removing a document directly from the UI. They accumulate pretty fast. and naming starts to be a challenge

rewbs commented 1 year ago

No probs! If you want to move all your documents between localhost:3000 and the prod site, you can got to Browser / Manage Database – you'll find import/export functions there.

verybluebot commented 1 year ago

Yes :) used this already. What do you think about the delete per doc feature?

rewbs commented 1 year ago

Easier access to deleting docs and deleting specific doc versions are both good ideas!