I think I'm right in saying that it's currently not possible to use
TiddlyWiki's import function (the one accessed through the backstage)
under TiddlyWeb.
Since TiddlyWikis accessed via TiddlyWeb are served by the CherryPy
server, and viewed over http, they are affected by the infamous cross
domain error caused by browser security.
For TWs on typical php enabled web servers, BidiX wrote a php proxy
script that, used in tandem with a small TW plugin, solves this cross
domain problem and allows transparent importing from TiddlyWikis
hosted at any location.
Unless I'm very much mistaken a php proxy script is not an option when
TiddlyWeb is used standalone. I do recall reading that it's possible
to run TiddlyWeb under another web server, like Apache, in which case
BidiX's proxy service should work.
Still it would be nice to have this feature natively, without needing
a php enabled server, and I don't think it would be very difficult to
do. Essentially TiddlyWeb needs a python proxy, a python counterpart
to the php proxy script.
I'd like to know the proper way to implement this in TiddlyWeb. My
guess from looking at the code is something like this:
*Add a new URL map to urls.map, like: /proxy[.{url}].
*Write a corresponding handler, tiddlyweb.web.handler.proxy, that
mimics proxy.php.
...that was almost too short for a bullet list, maybe I'm missing some
steps.
With the above in place, the proxy could be triggered by starting the
server, and visiting:
http://0.0.0.0:8080/proxy?url=http://www.tiddlywiki.com
and tiddlywiki.com would be fetched and displayed.
That would be the server proxy part.
To enable this to work transparently in TiddlyWiki, BidiX's
LoadRemoteFileThroughProxy plugin (http://tiddlywiki.bidix.info/
#LoadRemoteFileThroughProxy) could be used as is. The plugin uses
whatever proxy address it finds in a tiddler called SiteProxy, such
as: http://0.0.0.0:8080/proxy?url=.
When the url to the target wiki (the wiki to import tiddlers from) is
entered into the backstage import wizard, the proxy address is
automatically prepended to the url. This should trigger the /proxy URL
map, and invoke the handler, which should download the intended
TiddlyWiki and make it possible to import tiddlers.
Seems pretty easy, the main thing is to write a proxy in python and
use it as a handler. Please fill in any gaps and tell me if this is
indeed possible. I'll be really embarassed if there's already a way to
do this. I'm aware of twanager's importing capability, which is great
for whole wikis, but the TiddlyWiki import wizard makes it easy to
import individual tiddlers.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/TiddlyWikiDev?hl=en
-~----------~----~----~----~------~----~------~--~---
