You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I guess it requires that the file type is renderable in TiddlyWiki. I'm thinking of images particularly, but PDFs should also be fine.
The flow (for example):
User wants to make a photo album
User clicks "Upload images" from the Tiddlyhost actions menu and selects (say) 50 jpeg files
These files are saved by Tiddlyhost
The next time the site is reloaded, all the photos automatically become tiddlers with an "external content" field that links to a url with the file content so they photos appear. (Alternatively they could be "lazy loaded" tiddlers with the content embedded, as long as we can ensure that they do not become embedded in the TiddlyWiki when it is next saved.)
User can then created a nice photo album in TiddlyWiki in whatever way they like.
The TiddlyWiki file remains manageably small.
How to manage the uploaded files is still to be determined, e.g. what if you want to delete them later?
There's some overlap here with #236 which talks about using the upload files plugin. This idea doesn't exclude that one, but I consider this idea easier to prototype because it doesn't rely on a TiddlyWiki plugin, and because Tiddlyhost already supports injecting Tiddlers into a TiddlyWiki file when it is served. Also it doesn't require any change to the current TiddlyWiki saving mechanism afaict.
The text was updated successfully, but these errors were encountered:
I guess it requires that the file type is renderable in TiddlyWiki. I'm thinking of images particularly, but PDFs should also be fine.
The flow (for example):
How to manage the uploaded files is still to be determined, e.g. what if you want to delete them later?
There's some overlap here with #236 which talks about using the upload files plugin. This idea doesn't exclude that one, but I consider this idea easier to prototype because it doesn't rely on a TiddlyWiki plugin, and because Tiddlyhost already supports injecting Tiddlers into a TiddlyWiki file when it is served. Also it doesn't require any change to the current TiddlyWiki saving mechanism afaict.
The text was updated successfully, but these errors were encountered: