New Release
v0.5.24
I’m happy to announce this new Release that finally makes Sync over LAN / Relay work on Windows, too!
This is working great for me on Windows over LAN - great work!
1 Like
5.25 on Linux Manjaro, (tar.gz package).
Node.js still not coming up. This line in the error output
[TiddlyDesktop] tried: "/home/mark/Apps/TiddlyDesktopRS/tiddlydesktop-rs-0.5.25-linux-x86_64/bin/resources/tiddlywiki/tiddlywiki.js" (exists=false)
You know, I actually like the way imports work on Android better than on the desktop. It fixes the long-standing problem of keeping your data all in one place.
Would it be possible to have the option for imports to work on the desktop the same way that they do on Android? That is, the files are placed in a sub-directory.
This would help to make TW work more like an actual note-taking tool. Just because I import a file from the Downloads directory, doesn’t mean that that file is always going to be in the Downloads directory, or always be in the same relative location everywhere the TW file is located.
Thanks for listening!
Hi @Mark_S yes, that’d be an option.
I was already thinking about this.
What do you think would be the best possible approach?
Thank you!
Simon
Can you verify if this happens with a NEW install / a fresh tar.gz ?
The resources directory might have changed between versions, my bad.
I extract each update to its own dir.
I think it might be a pathing problem. Here’s where I find tiddlywiki.js:
./tiddlydesktop-rs-0.5.26-linux-x86_64/lib/tiddlydesktop-rs/tiddlywiki/TiddlyWiki5/tiddlywiki.js
./tiddlydesktop-rs-0.5.26-linux-x86_64/lib/tiddlydesktop-rs/tiddlywiki/TiddlyWiki5/plugins/tiddlywiki/codemirror-mode-x-tiddlywiki/files/mode/tiddlywiki/tiddlywiki.js
Here’s where it is looking:
[TiddlyDesktop] tried: "/home/mark/Apps/TiddlyDesktopRS/tiddlydesktop-rs-0.5.26-linux-x86_64/bin/../Resources/tiddlywiki/tiddlywiki.js" (exists=false)
Thanks!
Mark
I’m not seeing a “Resources” (capital “R”) directory, searching as far back as vsn. 3.63.
Hi @Mark_S … I hope with the next release coming within about 20 minutes this is fixed. If I don’t break anything else, fingers crossed.
v0.5.31 on Linux Manjaro (tar.gz)
Node.js is back!
In the dashboard, I see
(for single file wiki).
Question –
How do I reconnect to a wiki without losing data?
So, when I do a new install, frequently the dashboard is empty. Let’s say while it was offline I added a couple tiddlers to my single-file instance.
I re-enter the credentials for synching. It shows me an existing peer. It offers me the chance to connect to the peer and it’s version of my single-file instance. My single-file instance is then overwritten, losing the tiddlers I had added.
What is the best protocol to follow so that I don’t lose those tiddlers while re-establishing a connection?
Thanks!
I believe “Linking” the wikis is the best way, have you tried that?
Basically, on your new install you open the wiki, it’s not synced. You should see a “Get wiki” and “Link” button at the bottom, below the connected Room. Click on “Link” and select the added wiki. They should then be linked again for syncing.
When you then start both wikis, sync should happen and “copy” your newer tiddlers to the wiki that doesn’t have them or where they are older.
I think while you’re still in beta it would be a good time to just change the default behaviour to save to “files”. Ideally there would be a subdirectory field. I guess there would need to be a setting for which mode (local paths, or defined directory) is wanted when importing. There’s a use case for both uses, but saving to a defined directory brings TW more in-line with other note-taking apps, and enhances portability.
You are absolutely right about this. But I’m absolutely not settled. I’m primarily thinking about “folder wiki” to “file wiki” conversion. That’s easily done with having the attachments folder beneath the wiki.
An idea for a good, straight-forward mechanism would be much appreciated!
Maybe when converting a “folder wiki” to a “file wiki”, in the directory where the “file wiki” will be stored, we create the attachments directory if it’s missing and copy the content of the “files” directory into it… but that would destroy the _canonical_uri linking within the wiki. I don’t know. It’s easier for me like it is now.
But I’m still thinking about your idea copying attachments to the attachments directory also on Desktop.
I would suggest colouring that link like a button. It’s easy to miss. That’s my excuse and I’m sticking to it. 
When I try linking, I get this message:
And if I try a second time I get an RSOE:
Hmm. Should I have added the file to a room first?
Thanks!
Hi @Mark_S I thought this error would have gone. No you don’t need to add the wiki to a room first, you do that later.
Edit: try a third time 
I know that’s silly but when I encountered this error at least it worked then.
Would the files folder not be in the same relative position? Below the wiki info file or below the single file wiki? It’s been awhile, so maybe I have the wrong mental model.
Thanks!
I don’t know either, I never used it. I’m a single-file-first user.
It’s not a clean 3rd time, because I had already closed down TDrs. But indeed, the third time (numerically) was the charm.
But, I think, I had to toggle what room the file was in, even though I had linked. Not sure if that selection is following the status of the TW file or not.
Thanks!
This is a bad error, I forgot about it because I wanted to. It will be fixed in the next release (hopefully) for both Android and Desktop
Well, it seems like your synching mechanism effectively does all the things that we might otherwise have used node.js for, so, single-file-first feels like a good stance.
So, at least looking at my instances, the “files” directory is at the same level as the “tiddlers” directory. So it’s at the same level relative to the server root as the attachments folder is to the single-file TW file. It seems like its a one-to-one mapping.