mirrors/TiddlyWiki5
1
0
Fork 0
mirror of https://github.com/Jermolene/TiddlyWiki5 synced 2024-11-23 10:07:19 +00:00
Code Issues Releases Wiki Activity
A self-contained JavaScript wiki for the browser, Node.js, AWS Lambda etc.
22 Commits 101 Branches 68 Tags 90 MiB
JavaScript 96.9%
TeX 1.3%
Shell 0.9%
CSS 0.7%
Batchfile 0.1%
Other 0.1%
dc3546380a
Go to file
Jeremy Ruston dc3546380a Cleaning up 
Mostly murging adjacent var statements.
2011-11-28 17:04:39 +00:00
js Cleaning up 2011-11-28 17:04:39 +00:00
test/data Converted recipe handling to use async IO 2011-11-28 13:47:38 +00:00
.gitignore Introduced tmp/ directory for test artefacts 2011-11-25 15:51:02 +00:00
cook.js Converted recipe handling to use async IO 2011-11-28 13:47:38 +00:00
ginsu.js Adopted a saner convention for handling modules that export a single class 2011-11-27 09:46:02 +00:00
readme.md Added ginsu to readme 2011-11-28 13:49:36 +00:00
server.js Cleaning up 2011-11-28 17:04:39 +00:00
test.sh Improved test script 2011-11-26 13:23:26 +00:00

readme.md

cook.js

This is an attempt to modernise TiddlyWiki's build system, which is based on tools written in Ruby called Cook and Ginsu (see https://github.com/TiddlyWiki/cooker for details). This new version is written in JavaScript for node.js, with the intention that it can share code with TiddlyWiki itself.

Usage

node cook.js <recipefile>

Cooks a recipe file and sends the output to STDOUT

node server.js <recipefile>

Cooks a recipe file and serves it over HTTP port 8000

node ginsu.js <tiddlywikifile> <outputdir>

Splits a TiddlyWiki file into separate .tid files and a split.recipe file.

Testing

test.sh contains a simple test that cooks the main tiddlywiki.com recipe, first with the old Ruby-based tool, and then the new one. It uses OS X's opendiff to display the differences between the two files.

Current status

As of 22nd November 2011, cook.js can now build a fully functional TiddlyWiki from the existing recipe files. There are still some minor differences in the layout of tiddler attributes, and some whitespace issues that prevent full byte-for-byte compatibility.