Mmmm... most strange
Can I ask a few things
1) Are you using the most up to date version of the plugin? (http://
nicetagging.tiddlyspace.com/#NiceTaggingPlugin)
2) Which web browser are you using? (I've tried in Chrome and Firefox
and both seem to work)
3) What other plugins have you got installed
Hijack does seem to be the right word. The idea with hijacking is
// cache the old value of the function
var _cache = TiddlyWiki.prototype.saveTiddler;
// override the existing value
TiddlyWiki.prototype.saveTiddler =
function(title,newTitle,newBody,modifier,modified,tags,fields,clearChangeCount,c
I got the error in both chromium and firefox on Linux. And I tried it on a
freshly downloaded tiddlywiki 2.6.5
The only other plugin I had was messagefadeout wich only changes the
behaviour of the yellow messagebox when saving.
It works as you describe, so that is alright. I can also add tags if
On Dec 13, 7:04 pm, Jeremy Ruston wrote:
> So, at the beginning of December I took a deep breath and
> transliterated the existing TiddlyWiki wikifier code into cook.js. In
> the process, I massively refactored it, and structured it much more
> sensibly. Instead of using jQuery and the DOM, it now
> I've been mulling over (for a couple of months) the idea of using
> node.js to implement a store-and-forward message queue to use with TW,
> for many of the same reasons you selected it, I'm sure. Mainly I
> wanted to be able to use the same code/modules in the node.js server
> as I would in the
> So, at the beginning of December I took a deep breath and
> transliterated the existing TiddlyWiki wikifier code into cook.js. In
> the process, I massively refactored it, and structured it much more
> sensibly. Instead of using jQuery and the DOM, it now parses the
> wikitext into a generic tree
> On Dec 13, 7:04 pm, Jeremy Ruston wrote:
>> So, at the beginning of December I took a deep breath and
>> transliterated the existing TiddlyWiki wikifier code into cook.js. In
>> the process, I massively refactored it, and structured it much more
>> sensibly. Instead of using jQuery and the DOM,
>> node.js runs on the 2 main O/Ses I care about (Linux and XP), and
>> javascript is now an integral part of the Gnome desktop. That makes a
>> pretty level playing field for better integration of TW based apps
>> with my personal desktop, and still provding for a relatively simple
>> connection p
> +1. This is something I think we've all wanted for quite a long time.
> Is there a description of the tree format anywhere (I couldn't find
> one in the repo)? How are macros intended to fit into this tree?
> (These may be questions better asked in a twdev thread instead).
The tree format is doc
> I'm not sure it's relevant, but there's now a few SSJS engines
> knocking around (e.g. SilkJS http://silkjs.org/)
Interesting. My first reaction is not to like the JST file idea, but
I'll dig around a bit.
>> Yup, I'm finding that lots of modules that I'm interested in are
>> already built and
On Wed, Dec 14, 2011 at 1:02 PM, Jeremy Ruston wrote:
>> +1. This is something I think we've all wanted for quite a long time.
>> Is there a description of the tree format anywhere (I couldn't find
>> one in the repo)? How are macros intended to fit into this tree?
>> (These may be questions bette
> Cool. Being able to do something like:
>
> node tiddlywiki.js *.js *.html *.css > spa.html
>
> or whatever would be really useful.
Yes, that's very nice. I do intend to add wildcard support. Earlier
versions of the code worked by writing to stdout, which does integrate
with the shell wonderfully
On Wed, Dec 14, 2011 at 1:16 PM, Jeremy Ruston wrote:
>> Cool. Being able to do something like:
>>
>> node tiddlywiki.js *.js *.html *.css > spa.html
>>
>> or whatever would be really useful.
>
> Yes, that's very nice. I do intend to add wildcard support. Earlier
In Bash at least, the wildcards w
On Dec 14, 2:02 pm, Jeremy Ruston wrote:
> (Parenthetically, I'm planning to resolve the tension between docs in
> the source files and in the readme.md by auto generating the readme
> from the code).
Hi Jeremy,
Nice work !!
Have you seen dox [1] project. It can handle markdown and JSDoc style
t
> Hi Jeremy,
> Nice work !!
>
> Have you seen dox [1] project. It can handle markdown and JSDoc style
> tags. The big difference to other doc generators is, that it produces
> JSON output, that can be rendered by any templating engine.
Thank you, I hadn't seen that. I'm intending to use a full Jav
Downloaded the thing the other day. Seems interesting. Can it be used
as a blog tool? That is can I attach it to a website by installing a
header and site navigation above it as if it were a blog? Or, am I
just on the wrong track!
--
You received this message because you are subscribed to the Goo
On Dec 14, 8:48 am, Webiter wrote:
> Downloaded the thing the other day. Seems interesting. Can it be used
> as a blog tool? That is can I attach it to a website by installing a
> header and site navigation above it as if it were a blog? Or, am I
> just on the wrong track!
TiddlyWiki documents ar
> I don't suppose you have some general-purpose plugin, that is run on
> every bit of TW markup before it gets evaluated, and replaces
> by something else?
Hmmm nothing *yet* but I think it's an interesting idea...
perhaps as an enhancement to my AliasPlugin. You could define a
special t
Hello all
> e.g., suppose you define [[Aliases]] to contain something like:
>
> |path|c:\path\prefix\|
> |projectname|sometext|
>
> (i.e., a slice table with two entries, "path" and "projectname")
>
> then, when a tiddler is about to be wikified(), the Ali
Thanks all for the replies.
Skye - yes, smart thinking. Something like
<>
with the PATH tiddler just reading
http://jokenet.net
works fine!
Eric - from a quick look, it seems like AliasPlugin may already do
what I want? But I agree, it would rock even more with a %%%...%%%
style syntax
Ooopa..now thats exactly what I wanted to know. now to work to
see if I can get it woring as I want.
Thanks
Skye
On 14 dez, 08:18, rakugo wrote:
> Hijack does seem to be the right word. The idea with hijacking is
>
> // cache the old value of the function
> var _cache = TiddlyWiki.prot
On Dec 14, 7:54 pm, Jeremy Ruston wrote:
> One of my next steps is to rewrite the wikifier as a peg.js grammar,
> developing a revised TiddlyWiki wiki format that is largely backwards
> compatible but handles paragraphs sensible, and brings in the best of
> markdown (I'm very used to writing `cod
22 matches
Mail list logo
