Simon and I have been experimenting with skinny tiddlers on ccTiddly,
and I thought we'd share what we've learned so far.
(It's just an experiment to explore the possibilities and obstacles.)
The reasoning for looking into this in the first place was to reduce
load times on a document with a large number of content-heavy tiddlers.
So we're loading tiddler contents on demand - in contrast to loading
entire tiddlers on demand, which has even more complex implications.
We've had to hijack and override a few core functions to make this work:
http://tinyurl.com/6apu97
(http://svn.tiddlywiki.org/Trunk/association/serversides/cctiddly/Trunk/tiddlers/plugins/skinnyPlugin.js)
(The implementation is very hacky at this point.)
Note that plugins/macros relying on tiddler contents (e.g. certain
ForEachTiddler macro calls) will have problems with this approach.
The problem here is that many functions (whether core or third party)
access tiddler properties directly rather than through a well-defined
interface, which means we can't intercept that access.
Also, there are certain tiddlers that must not be loaded on demand:
* plugins (evaluated on startup)
* shadow tiddlers (relevant to the page layout)
* themes (theoretically, this only applies to the selected theme)
(this list might be incomplete)
-- F.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
