Hello,
As I advance on the development of tiddlydrive things are getting bigger
and complex. I am thinking if I should move some of the existing code to a
new module with the new code should income. Currently I have four JS files:
- An TW utils module that manages most of the work. It
Hi Danielo,
It should listen and track changes to tiddlers,
This means your module is active from the beginning on. Sounds like a
startup module to me. not a library and not a widget.
be responsible of telling what should be uploaded, what can be refreshed
and to start the process of
Hi Danielo
First of all, I am acutely aware that it sounds like I'm telling you what
to do, and I can understand how frustrating that might be. Of course,
you're free to do things however you want, and there's nothing wrong with
anything that works for you.
My comments are relevant because we're
Hello Jeremy,
First of all, I am acutely aware that it sounds like I'm telling you what
to do, and I can understand how frustrating that might be. Of course,
you're free to do things however you want, and there's nothing wrong with
anything that works for you.
I'm sorry about our last
Hi Danielo,
Maybe I can create a startup module that starts a modified version of the
syncer module
Can't you use the core syncer as the prototype so as to implement and
initialize your custom syncer on top?
Or is there a need to somehow disable / replace it?
Yes, I saw it happening
Hi All,
I just downloaded TW5 from GitHub and am trying to start the node server.
However it gives this output.
C:\Users\Arlen\Desktop\Arlen's Stuff\NodeJS\TW5.1.5node tiddlywiki --init
tw5.com-server
Copied edition 'tw5.com-server' to C:\Users\Arlen\Desktop\Arlen's
Stuff\NodeJS\TW5.1.5
you missed the edition.
node tiddlywiki editions/ --server
-m
--
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
Hi all,
I am working with the renderTiddler command and the tiddlywiki server, and
the renderTiddler command seems to URI encode links to other tiddly
documents. I am referring to the commands in this tiddler:
http://tiddlywiki.com/#Generating%20Static%20Sites%20with%20TiddlyWiki
For instance,
To explain in more detail, I am working on adding single page views to
tiddlywiki that use the static mechanism but are generated on request. I
think if I would put the title through decodeURIcomponent twice it would be
fine, but I wanted to make sure that this is according to design.
-Arlen
On
Hi Arlen
The default static templates reconfigure the way that links are rendered so
as to convert internal tiddler links into file links.
At the top of $:/core/templates/static.template.html you'll see:
\define tv-wikilink-template() static/$uri_doubleencoded$.html
The docs for the link
Thank you.
Here is the result of my exploring today. In order to generate static pages
dynamically (!!!???), this code gets inserted into server.js. The only
other change was to clone the $:/core/templates/static.template.html
tiddler and change the link you mentioned to remove the static/
Actually, if you change the first one to path: /^\/static.html$/, it
would work fine too.
-Arlen
On Tue, Dec 9, 2014 at 4:48 PM, Arlen Beiler arlen...@gmail.com wrote:
Thank you.
Here is the result of my exploring today. In order to generate static
pages dynamically (!!!???), this code gets
Hi Arlen
First, to Mario's point, if you omit the edition folder from the tiddlywiki
command then it defaults to using the current directory.
The error message seems to show that you've somehow managed to have your
TiddlyWiki core files (such as C:\Users\Arlen\Desktop\Arlen's
Hi Arlen
Here is the result of my exploring today.
Great stuff, well done. I'd be happy to take a pull request for these
changes, if you're able. The associated documentation also needs updating.
There are a few related tickets on the HTTP server module:
Thanks, for your help, Mario. I discovered that after a bit.
Jeremy, I downloaded the 5.1.5 tag from github, and then copied the node
executable into the folder beside tiddlywiki.js. That makes it easier for
me than worrying about the node command line and so forth. So I was in the
root folder of
15 matches
Mail list logo