> So we're loading tiddler contents on demand - in contrast to loading > entire tiddlers on demand, which has even more complex implications.
We've come up with an concept: #1 load document (including the essential tiddlers mentioned before) #2 on load, fire off an XHR to retrieve all tiddlers in skinny form #3 (optional) load tiddler contents in the background With including the last step, we're losing the advantage of minimizing the amount of data sent over the wire - however, it increases responsiveness on startup and eliminates most problems with plugins/macros. We haven't implemented this yet, but it sounds like it just might work... -- 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 -~----------~----~----~----~------~----~------~--~---
