Hi Chris
> The readme in the tw5 repo is intended to give that information, so >> feedback appreciated if it doesn't. Basically, download the repo, mkdir >> jermolene.github.com parallel to the repo, cd into the repo and run >> bld.sh >> - actually, the abbreviated qbld.sh should be fine for you. >> > > I've been able to make some headway by cooking the wbld.sh and have a > semi-working version on a branch: > > https://github.com/cdent/TiddlyWiki5/compare/tank?expand=1 That's great, thank you, very easy to follow. First, a top level thing: the tiddlywebadaptor is currently used unchanged for talking to TiddlyWeb/Space and TW5's own noddy HTTP server. I'd like to retain that approach, which suggests that some of the changes need to be parameterised, as you've noted. In TW5-land the way to provide configuration to a global component like tiddlywebadaptor would be via tiddlers with special titles (eg, the current code retrieves the template for the host portion of the URL from '$:/config/tiddlyweb/host'. This implies that we should create a new "edition" for the this Tank work, which is to say a folder like "editions/tw5tiddlyweb". The edition would contain configuration tiddlers that set things up for Tank, with corresponding configuration tiddlers in "editions/clientserver" for TW5 talking to the TW5 server component. I'm not sure whether we should continue to support the current tw5tiddlyweb edition. It's not really usefully functional, and I think we'd probably both rather put effort into Tank, perhaps? As noted in the commit message there, I'm having some trouble with a > field in fields named fields being generated at least with drafts, but > maybe sometimes with the "proper" tiddlers. > Thanks, I'd missed it but had the same problem with tw5tiddlyweb. I've fixed it here: https://github.com/Jermolene/TiddlyWiki5/commit/1086c51019539560768d8e97ac527ae19260cbe5 My approach is to get it working in gross form and then smooth it out > once I have some notion of what's going on. I have a bit better sense > of how things build and what the syncer is doing, but feel quite a > distance from elegance. > Seems like good progress to me. * It would be awesome if TW didn't have to worry about login/logout, just redirecting to the appropriate SPAs to handle it. The tricky case is maybe when a user has made changes that they can't save without logging in. * How might we handle extracting the recipe from the URL if a custom domain is being used? * The current code excludes the app by appending ?select=title:!app to the end of the skinny tiddler URL. As it's only a skinny version presumably there'd be no problem with instead doing the exclusion on the TW config side? > It looks like the current tiddlywebadaptor.js code requires the current > user be logged in. Is there a particular reason for this Jeremy? That > comp above is designed to be public, but unless isLoggedIn is true the > callback after status is not called... Fixed: https://github.com/Jermolene/TiddlyWiki5/commit/190ced7cddf367b192192ef9b8c05ee2cb937197 Best wishes Jeremy Little help? > > > -- > Chris Dent http://burningchrome.com/ > [...] > > -- > 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. > -- Jeremy Ruston mailto:[email protected] -- 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.
