How do I choose between them (pros/cons)?
First my questions, which I hope you'll help me with, then, if you care, the context.I want to use TW5 for notetaking, on Windows, but shared (not simultaneously) between multiple computers via DropBox or a web service.A) I can choose from TiddlyIE, Node.js, and TiddlyDesktop.
B) I can choose to share via a DropBox folder (replication), TiddlySpot, TiddlySpace, or TiddlyWiki in the Sky.How do I choose between them (pros/cons)?
C) I can choose to save as a single file wiki, or (with node.js only?) as a wiki folder.
D) Is it best practice to use TW-style wiki markup or something else, specifically, is the Markdown plugin officially supported?
Context: I used to use TWC heavily. I've got about 10 fairly large wikis of notes (each one a different topic) and 1 for job searching - they all share a base wiki which has all my customizations - and that uses the SharedTiddlersPlugin extensively
da...@bakins-bits.com wrote:A) I can choose from TiddlyIE, Node.js, and TiddlyDesktop.TiddlyIE - I'm guessing you know that there is no such thing. There is regular TW used on IE. I can't tell anymore if IE is a good idea but one reason why I switched to FF and Chrome many years ago was because of IE's quirks. Personally, when I develop stuff for TW I don't even bother testing it in IE.
First my questions, which I hope you'll help me with, then, if you care, the context.I want to use TW5 for notetaking, on Windows, but shared (not simultaneously) between multiple computers via DropBox or a web service.A) I can choose from TiddlyIE, Node.js, and TiddlyDesktop.
- How do I choose between them (pros/cons)?
- After getting started with a particular TW (adding nodes to it), can I switch between platforms?
B) I can choose to share via a DropBox folder (replication), TiddlySpot, TiddlySpace, or TiddlyWiki in the Sky.How do I choose between them (pros/cons)?
C) I can choose to save as a single file wiki, or (with node.js only?) as a wiki folder
- How do I choose between them (pros/cons)?
- Can I change my choice later for this wiki?
- Is my choice here dependent on whether I'm using TiddlyIE, Node.js, or TiddlyDesktop?
- If saving as files, there are multiple formats. How and when do I choose between them?
D) Is it best practice to use TW-style wiki markup or something else, specifically, is the Markdown plugin officially supported?
Context: I used to use TWC heavily. I've got about 10 fairly large wikis of notes (each one a different topic) and 1 for job searching - they all share a base wiki which has all my customizations - and that uses the SharedTiddlersPlugin extensively so when I update the customizations in the TWC base.html it is automatically available in all my wikis. At some time, maybe 9 months ago, when I was still reading this group regularly, I wanted to try TW5. But not only was the documentation poor, but it seemed that there was no equivalent to SharedTiddlersPlugin or any mechanism for simulating it (that I didn't have to write myself). So, when it started to be the case that "trivial" IE10/IE11 updates kept breaking the save mechanism I moved away from TWC entirely.
I thought things might be different with 9mo further development and I'd now give TW5 a try. I'm willing, at this point, to give up the SharedTiddlersPlugin functionality just to start with TW5. But on reading tiddlywiki.com I immediately find I have the questions above and no answers. Having to make these choices immediately on starting to use TW5 with no guidance on how to make these choices gives me an insurmountable hurdle to begin with.
Frankly, it's easier to just buy a subscription to Evernote or use my Office 365 OneNote subscription: Even those are much more limiting solutions than TW5 offers, I can get started with them in no time and get on to my real work.
It's just that TWC was so great for me for so long I'd like to give TW5 a try. The thing is: As an experienced TWC/wiki user I'd be able to use TW5 easily - markup, structuring, indexing, etc., no problem. And I could customize it eventually, with help from this group, if I care. But I can't get started while these questions are pending.
Thanks! -- David
D) Is it best practice to use TW-style wiki markup or something else, specifically, is the Markdown plugin officially supported?
I personally use TW markup and I don't even need to see it rendered. It just works ;) ...
Markdown is an option, ... _but_ you'll lose TW specific functionality.
What most people don't know about the TiddlyWiki NodeJS version is that it can actually run a file server and rest API to serve and save TiddlyWikis. I've used it quite a bit and it works very well.
The biggest advantage for you in using it is that one wiki can inherit another. The biggest disadvantage is that each one has to run on its own port number if you want to access more than one at the same time. Of course, you could just make a tiddler in your base wiki with links to all of them, so that would probably take care of that.
It is relatively easy, if you are familiar with NodeJS, to hack together a more versatile server which can serve multiple wikis. There are a lot of optimizations that could be done along those lines, but it will work fine for what you want.
If you go with TiddlyWiki in the Sky on Dropbox that will work well unless you have a slow upload speed on Dropbox. What I have done is make a loading script for Electron.io that allows me to run a TiddlyWiki in a lean, chromium-based window. I also store the electron files on Dropbox, and have found it much easier to work with than NodeWebkit. But I'm a custom script type. :)
If you use TiddlyDesktop, you will have an active support community (this one) and the interface itself is defined in a TiddlyWiki :)
As far as format, there are only two right now, NodeJS/TiddlyWeb/TiddlySpace tiddler "syncing" and Browser/TiddlyDesktop/TiddlySpot/Dropbox file "saving". What you are familiar with is the second one. The first one is the way the NodeJS server works.
Anytime you want to switch between the two formats it is usually very simple, just drag and drop. Well, file to server. The other direction involves either copying the code from View Source in your browser into a new HTML file or making a download button inside the TiddlyWiki and clicking it. Anyone here can tell you how to do that.
Hope that helps. Feel free to ask if something isn't clear.
-Arlen
--To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/d7212384-b9af-4e0d-9b03-210c28acc719%40googlegroups.com.
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscribe@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
TiddlySpot/Dropbox file "saving". What you are familiar with is the second one. The first one is the way the NodeJS server works.
I wonder if someone might expand on this a bit for me, a pretty much non-technical user. It seems that the difference between syncing and saving is kind of critical, and I'm pretty certain I don't quite understand it. Where would github fit into this discussion -- in which it seems I use TiddlyDesktop or Browser to "save" my wikis, and then use GitHub to "sync" them.
Thanks!
//steve.
Hi Steve, glad to be of help.
The way TiddlySpace, TiddlyWeb, and the NodeJS server work is that all of them serve a copy of your tiddlywiki to the browser and then as you make changes each tiddler is saved individually back to the server, changes from the server also end up on the TiddlyWiki in your browser, thus we say they are kept in sync with each other. This is what we call "syncing".
TiddlySpace and TiddlyWeb were built for TiddlyWiki classic and I have not used them much for TW5. The NodeJS version, however, is just a copy of the TW5 files on GitHub and is used to compile standalone TiddlyWikis from scratch via the command line. Another set of arguments starts the webserver, using the same NodeJS files. So it is definitely built for TW5. :)
TiddlySpot and TW5-in-the-sky-on-Dropbox (TWitS5-Dropbox) do it a little bit different. Every time you save, it compiles and uploads the entire TiddlyWiki to the cloud, not just the tiddler that got changed. The file saver mechanisms used for TiddlyDesktop, TiddlyFox, and TiddlyChrome do the same thing, but because they are saving to the hard drive, you don't notice it.
The server version is also fast, and should be even on the internet, although I have not tried it. I have considered making TWitS5 support syncing tiddlers, which would make it faster.
I'm not familiar with saving to GitHub, but I think it would save the entire file.
There should be instructions tiddlywiki.com for using the server version, but feel free to ask if you have any questions.
-Arlen