On Wed, 12 Feb 2014, Jeremy Ruston wrote:
Host might appear to be a distinction but if the code itself is loaded
from the same place as the tiddlers (as it usually does) then host can
be '/'.
At the moment TW5 reads the template for the host URL through the magic
tiddler $:/config/tiddlyweb/host, which was done in response to this ticket:
https://github.com/Jermolene/TiddlyWiki5/issues/92
Would setting the host "/" have worked for supernovus?
Perhaps '/notes/'? As long as where the wiki is coming from is the
same place that stuff is being sent, the browser will not need host,
right? So in that proxy situation the hostname stays the same for
subsequent requests after the first get. It's just the path that's
interesting.
In fact TW5 simplifies on TWC quite a bit in the sync area. TWC's sync
used fully qualified URIs, presumably because back in the (good?) old
days a twc actually could sync with multiple hosts.
[login/out]
OK, so it sounds like TW shouldn't attempt to handle logging in. What might
we do in the situation where people have changes and yet aren't logged in
in order to save them? On the TW side it's easy for them to download a
plain copy of the updated wiki from the control panel "Server" tab.
Usually TiddlyWeb uses cookies for credential extraction, after the
initial challenger stage, so once option would be a link to a new tab
where auth happens. Then the browser would have the right cookie for
subsequent puts from the tw5.
I don't think I quite understand the details of your question? Are you
asking what happens if there's an internal rewrite (rather than
redirect) from somecustomdomain.com/ to defaultdomain.com/some/path?
Yes, I think so. I was wondering what might happen if Tank had
TiddlySpace-style custom domain support; presumably we'd have the same
problem of needing to pass the recipe name through some other means).
If that ever happened I suspect it would go in to status in much the
same way that TiddlySpace does. However I'm undecided if tank will do
virtualhosts natively. It might instead operate on some kind of
rewrite mechanism. I'm unsure. It largely depends on who uses it and
how that use develops.
In any case, the problem is not insurmountable.
[rendering]
There's a simple demo app that shows how to use the TW5 parser/renderer as
a library:
https://github.com/Jermolene/TiddlyWiki5DemoApp
Ah okay, I think I had seen that before and forgot about it. Will
revist. Thanks.
[1] I'm using the /comps path in Tank to distinguish both from the API
URI and from the fact that a recipe represents a collection of
tiddlers, whereas a comp loads one tiddler (app) from a recipe.
One of the learnings from tiddlyspace was that as much as it initially
appears nice for the API and human interface to overlap, it ends up
getting messy on various dimensions.
Interesting. So /comps/<recipe> is a shortcut for
/recipes/<recipe>/tiddlers/app?
Effectively, yes.
By the way, can you explain how to create a comp in Tank?
For the tw5 case it's something like this:
* on your dashboard (/dash) create a tank on the right
* at the bottom on the left is a list of "Available Comps"
* click on tw5
* on the following page click on 'This tank is composable'
* choose a name
* choose the tank you created from the drop down
* confirm
There will be other directions from which to do it, in the future, but
for the moment the "find a composable tank, use it" path is the only
one that is exposed.
Under the covers the result of that is a recipe:
/bags/tw5/tiddlers
/bags/<your tank>/tiddlers
So somebody could use the API to create one by other means.
I've removed quota restrictions on your account so you can create more
tanks (the base limit is 5).
--
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.
