On Jan 31, 4:29 pm, Jeremy Ruston <[email protected]> wrote: > Aha, that makes sense. I think you're talking about the same > distinction as me with my comment about distinguishing "tiddlers that > are linked to from those that are transcluded. The underlying issue > can indeed be seen as whether one needs the skinny or thick version of > the tiddler. > > So, I'll explore making the dependencies be a hashmap of > {title:,type:}, where type would be "skinny" or "fat" (or something > less confusing).
My latest code[1] is now relatively close to being on par with twikifier. It listens on a socket for info about what to render (tiddler title and context), resolves dependencies, gets them, renders, returns the output. Things I've noticed: * As expected, having the type info discussed above would be useful, most especially in the case where null is returned. If that null can be qualified as not needing text, then a single request (for skinny json of the context collection) can be made rather than either a fat request or a many single requests. The current code does the latter and when the number of tiddlers in the context gets high, up over a few hundred, it is noticed. * This may have changed already, but it appears that when generating links to tiddlers the href is not getting an encodeURIComponent applied, thus [[foo bar]] becomes href="foo bar" where it presumably should be "foo%20bar". The next things to do for me are: * get caching of remote tiddlers and/or stores back in * translate the tiddlyspace link syntax and add it to macros [1] https://github.com/cdent/cook.js/tree/wikify -- 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.
