On Wednesday, May 28, 2014 8:12:24 PM UTC+2, [email protected] wrote: > > Yes I find tiddlyweb particularly interesting and promising and I'm > looking forward to the point where I have a solid TW5+TiddlyWeb environment > :) >
Using a TW5 + TiddlyWeb instance is a bit experimental at the moment. The TW5 TiddlyWeb adapter module isn't stable yet ... The adapter should work with the nodejs backend and the tiddlyweb backend. ... While the nodejs backend has very limited functionality atm ( no bags and recipes ....) When I found out about TiddlyWeb I instantly tried to figure out how the > pieces fit together, but at the time it was very confusing. Then I stumbled > across tank and now I know that it's time to dig into it. > tank is an application from Chris Dent, the inventor of tiddlyweb, based on tiddlyweb. If you have a look at pypi [1] package index, you'll see its not packaged yet. So installing it may be a bit tricky. > I have problems though grasping how reliably the pieces work together and > how mature they are. I'd love to have an instance of TiddlyWeb and tank but > I don't know if I would be able to use it productively at this time. > tiddlyweb and its plugins [1] are pretty mature already. TiddlyWeb powers TiddlySpace.com since several years ... but as you write, figuring out, what to combine is tricky. ... > It seems that you did some really important groundwork for setting up > instances of TiddlyWeb, thank you very much! Can you recommend a strategy > to get going? > I did several experiments with a "vanilla" tiddlyweb installation ... combining it with TWclassic [2]. I also tried to create a "1 click" setup with the help of vagrant and VirtualBox, to make experiments easier. .. But this configuration doesn't work well with TW5 out of the box. IMO TW5 needs a different approach, which is pretty straight forward. nginx + wsgi + tiddlyweb, where nginx serves a "lazy" TW5.html file ... As above the TW5 adapter isn't finished yet. > TiddlyWeb has some server side plugins, that could do indexing, that can >> be accessed with a query string in the URL. >> > > That's great! Does this work already with TW5? > That's independent from TW5. I was thinking about the server side whooser plugin [4]. TW5 has no UI to use this function. Indexing also depends on your tiddler store. So if you use the file store, or a sql database. Which increases the number of moving parts .... > >> But the work needed is significantly more, than splitting the content >> into different TWs, if possible. >> > > What do you mean, what is needed exactly? > As I wrote, there is no TW5 UI atm. > Is this a categorical thing, i.e. does the core of TW or TiddlyWeb need > major adjustments to the core? > Or is it only the glue that's missing, i.e. api calls and filling various > hooks and callbacks? > You need to do the server side configuration right. I also don't get the "splitting into different TWs, if possible" part. > If your TW is too big, you can split it into several TWs, so every file has less tiddlers. IMO splitting a TW is much less work than dealing with the server side. But if you want multi user TWs imo you'll need a server side. ---- Stefan, you have an gmx.at acount. So where are you from? -mario [1] https://pypi.python.org/pypi?%3Aaction=search&term=tiddlyweb&submit=search [2] http://tweb-at-home.tiddlyspace.com/tweb-vagrant [3] http://tweb-at-home.tiddlyspace.com/ [4] https://pypi.python.org/pypi/tiddlywebplugins.whoosher/0.9.28 -- 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/d/optout.
