3 ms·

Tiddlywiki is exactly what I want as a note-taking system, except for one detail: image handling. I have heaps of screenshots that I want to store along with my

Tiddlywiki is exactly what I want as a note-taking system, except for one detail: image handling. I have heaps of screenshots that I want to store along with my notes, and Tiddlywiki either: 1) embeds the image into the wiki itself (not sustainable); or 2) requires you to create image tiddlers with a _canonical_uri pointing to an external image file (which makes the Wiki not self-contained). This works but it's not as simple as drag and drop like in, say, Obsidian. This small friction is the only reason I've picked a different tool for note-taking.

rpdillon 4y ago
Agreed. I'm working on an extension that allows pasting of e.g. screenshots. It requires two components: a change to the wiki itself to trap the paste event and detect an image and call the backend to store it, and a server that can accept a POST that stores the images alongside the wiki. I needed the backend to support seamless saving via WebDAV anyway, so this was a small update to that code. I've finished the backend portion, but I'm still working on the frontend; I want it work in both the normal tiddler editor as well as my log-based extension. I'm excited to get it working, but it does break the "all in one HTML file" aspect. I'm OK with that: I can archive the directory of images alongside the wiki, but it might not be for everyone.
- Datagenerator 4y ago
  Good to hear, please keep the number of possibilities high by storing the images just as files. Do you have public code to test or follow for interested TW5 users? Thanks!
  - rpdillon 4y ago
    Yes, the images are just files in a directory called "s" (for static) that sits alongside my wikis. I've describe this system a few times, but this is the first time I've gotten some interested replies. I have a long weekend this weekend; I'll take a stab at cranking through the frontend code and making it available publicly.
- saqimtiaz 4y ago
  You might find the FileUploads plugin of interest. Every time it detects an image in TiddlyWiki that meets a specified filter, the image is uploaded to a storage backend. Demo: https://talk.tiddlywiki.org/t/image-imports-in-tw-5-2-0-and-fileuploads-plugin/122 https://talk.tiddlywiki.org/t/image-imports-in-tw-5-2-0-and-... The choice of backend is pluggable via Uploader modules. There is already an experimental PUT Uploader that is WebDAV compatible. The version currently published is very simple though there is an advanced PUT uploader that I need to polish up and publish that allows for things like creating directory structures if needed when uploading an image and sanitizing tiddler titles to ensure that they are valid file names. Installation is via a plugin library: https://saqimtiaz.github.io/SQPL/ https://saqimtiaz.github.io/SQPL/ Discussion: https://talk.tiddlywiki.org/c/plugins/file-uploads/8 https://talk.tiddlywiki.org/c/plugins/file-uploads/8 If you are working with TiddlyWiki and WebDAV, you might find this writeup of interest as well: https://saqimtiaz.github.io/sq-tw/webdav/ https://saqimtiaz.github.io/sq-tw/webdav/
  - rpdillon 4y ago
    This is extremely useful info, thanks so much for posting it! I was unaware of the FileUploads plugin, and I've been trying to piggyback as much as possible on TW's builtin WebDAV support so Notedeck remains lightweight. If I could update my existing backend code (it's a single, 320-line Python file at the moment) to support some additional WebDAV calls so it works with FileUploads, I would consider that a complete solution.
AlanYx 4y ago
Another source of friction with Tiddlywiki is the interface. To create a tiddler, you need to enter a title, then tab to the tag name field, then tab to the content field, enter your content, and then there's no way to tab to the "Add" button; you have to pick up the mouse and click it. If you're using tags or categories, there's even more friction. I love it conceptually, but if you're entering short discrete information (e.g., a number of todos, each as their own tiddler), it's more work than it needs to be.
- rpdillon 4y ago
  Agreed. This is precisely why I built the logging system: it removes the need to add titles, and makes creation as simple as Ctrl-Enter. Unlike many of the popular tools, it's got primitives one can compose to a solution that's smooth and fast, but doesn't provide it out of the box. I hope more tiddlywiki "distros" will be shared that bridge the gap.

rpdillon 4y ago

Agreed. I'm working on an extension that allows pasting of e.g. screenshots. It requires two components: a change to the wiki itself to trap the paste event and detect an image and call the backend to store it, and a server that can accept a POST that stores the images alongside the wiki. I needed the backend to support seamless saving via WebDAV anyway, so this was a small update to that code. I've finished the backend portion, but I'm still working on the frontend; I want it work in both the normal tiddler editor as well as my log-based extension. I'm excited to get it working, but it does break the "all in one HTML file" aspect. I'm OK with that: I can archive the directory of images alongside the wiki, but it might not be for everyone.

Datagenerator 4y ago
Good to hear, please keep the number of possibilities high by storing the images just as files. Do you have public code to test or follow for interested TW5 users? Thanks!
- rpdillon 4y ago
  Yes, the images are just files in a directory called "s" (for static) that sits alongside my wikis. I've describe this system a few times, but this is the first time I've gotten some interested replies. I have a long weekend this weekend; I'll take a stab at cranking through the frontend code and making it available publicly.
saqimtiaz 4y ago
You might find the FileUploads plugin of interest. Every time it detects an image in TiddlyWiki that meets a specified filter, the image is uploaded to a storage backend. Demo: https://talk.tiddlywiki.org/t/image-imports-in-tw-5-2-0-and-fileuploads-plugin/122 https://talk.tiddlywiki.org/t/image-imports-in-tw-5-2-0-and-... The choice of backend is pluggable via Uploader modules. There is already an experimental PUT Uploader that is WebDAV compatible. The version currently published is very simple though there is an advanced PUT uploader that I need to polish up and publish that allows for things like creating directory structures if needed when uploading an image and sanitizing tiddler titles to ensure that they are valid file names. Installation is via a plugin library: https://saqimtiaz.github.io/SQPL/ https://saqimtiaz.github.io/SQPL/ Discussion: https://talk.tiddlywiki.org/c/plugins/file-uploads/8 https://talk.tiddlywiki.org/c/plugins/file-uploads/8 If you are working with TiddlyWiki and WebDAV, you might find this writeup of interest as well: https://saqimtiaz.github.io/sq-tw/webdav/ https://saqimtiaz.github.io/sq-tw/webdav/
- rpdillon 4y ago
  This is extremely useful info, thanks so much for posting it! I was unaware of the FileUploads plugin, and I've been trying to piggyback as much as possible on TW's builtin WebDAV support so Notedeck remains lightweight. If I could update my existing backend code (it's a single, 320-line Python file at the moment) to support some additional WebDAV calls so it works with FileUploads, I would consider that a complete solution.

AlanYx 4y ago

Another source of friction with Tiddlywiki is the interface. To create a tiddler, you need to enter a title, then tab to the tag name field, then tab to the content field, enter your content, and then there's no way to tab to the "Add" button; you have to pick up the mouse and click it. If you're using tags or categories, there's even more friction. I love it conceptually, but if you're entering short discrete information (e.g., a number of todos, each as their own tiddler), it's more work than it needs to be.

rpdillon 4y ago
Agreed. This is precisely why I built the logging system: it removes the need to add titles, and makes creation as simple as Ctrl-Enter. Unlike many of the popular tools, it's got primitives one can compose to a solution that's smooth and fast, but doesn't provide it out of the box. I hope more tiddlywiki "distros" will be shared that bridge the gap.