Hi Mat, In TW5 you are in no way limited to a single file TW. In TW5 you are in no way limited to a directory full of single tiddlers. In TW5 you are in no way limited to use the jar file, to save with Chrome, Safari, Opera ... WebKit based browsers. In TW5 you are in no way limited to use TiddlyFox with Geko based browsers in order to be able to save. ... IMO you are not limited in any way. ... Saver modules, browser plugins and TiddlyDesktop [2] are add ons, for the users convenience.
One distribution format of a TW happens to be a collection of tiddlers, that are saved in a single file. That's a convention, nothing else. We call it a file TW. Many users love it, because you can save it in a "public folder" and share a single file, with there family or friends. Any "file sync plattform" can be used for this usecase. Eg: Dropbox, Box, seafile / cloud and many others TiddlyWeb can be used as a backend for TW5. Where TW5 is a Single Page App [1] (SPA). TiddlyWeb builds around a collection (bags) of tiddlers, that can be "shared" / included ... You can set access rights in a very fine granularity, which gives you endless and incredibly powerful possibilities. The backside of the coin is its complexity. I did try to make TiddlyWeb handling easier [3] with several step by step howto's. But there is "real server" management involved, which seems to frighten the hell out of non techy users. The TW5 project includes a development server [4], that allows you to save tiddlers back into the file system. This is very usefull, because it allows users, that use TW as there tiddler editor, to directly manipulate single tiddlers. ... but setting up the node stuff is kind of complicated (see TWeb). I did create a dev / test environment named tw5-vagrant [5], that should make the start for contributors easier. It's easy to use if installation of the dependencies goes well. ... So there's TiddlyDesktop for the rescue. TD [2] basically is a TW management application that is available for win, linux, mac. The advantage here is, that all the stuff is bundled in a "nice" way, which makes installation easier. .. At the moment it is able to handle single file TWs. TWclassic and TW5. ... but a future version will be able to handle "tiddler directories". So imo there are no conceptual nor technical barriers to handle single tiddlers. There is just not enough UI to satisfy everyone’s expectations. Jeremy explained several times, that for him, the single file nature of TW is a key feature. So imo it's a USP [6] ;) But I think he should speak for him self. Chris Dent explained several times, that for him, the nature of a tiddler is a key feature, and using them with TWs is cool, but there may be other interesting possibilities. He's doing a new project called: "tank" [7], which is alpha (2014-02-02) but imo very interesting. So I think, it doesn't matter, if you want to use tiddlers with file TWs or tiddlers in combination with server side software. Depending on your expectation or personal preference the development focus may be right or wrong. ... It's just a matter of your point of view. have fun! mario [1] http://tw5tiddlyweb.tiddlyspace.com/tw5 [2] https://github.com/Jermolene/TiddlyDesktop/ [3] http://tweb-at-home.tiddlyspace.com/ [4] http://tiddlywiki.com/static/Installing%2520TiddlyWiki%2520on%2520Node.js.html [5] https://github.com/pmario/tw5-vagrant [6] http://en.wikipedia.org/wiki/Unique_selling_proposition [7] https://groups.google.com/forum/?fromgroups#!topic/tiddlyweb/lCPFLO9zSKY -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/groups/opt_out.
