> do you assume that the server is always going to be available I think that's a fair assumption when dealing with dynamic loading - provided, of course, that it's optional and you can still get the full document for taking it offline.
> If it's working right, what should happen is the tiddlers are loaded > from the server, as you navigate along them. [...] > If I'm not mistaken, load on demand is actually the natural mode of > operation for TiddlyWiki's core adaptor mechanism. Indeed, TiddlyWiki already has basic support for loading tiddlers on demand. However, that (currently) only works if a tiddler is requested explicitly through the UI, so it's incompatible with many core functions (e.g. search, references) and plugins. > There's no notification when a tiddler doesn't exist. We're aware of that (the mechanism is really very basic at the moment). I don't think there's a ticket for this though - could you report the issue on Trac? So, now that we've outlined the issues, where does this leave us - what could/should we start with to create a simple proof of concept? -- 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 -~----------~----~----~----~------~----~------~--~---
