> changes to be saved automatically so that only the first person to > open the wiki has the delay while the updates take place.
Whenever <<loadTiddlers>> is processed, the entire remote file is read- in and it's tiddlers are compared with the tiddlers in the current document. As such, nearly all of the processing overhead occurs *each and every time* the macro is invoked, regardless of whether or not the tiddlers in the current document are 'up-to-date'. Thus, auto-saving after updating will *not* result in any significant speed enhancement for subsequent users of that document. In addition, I really don't like the idea of *automatically* overwriting the file immediately after *automatically* replacing some of the tiddlers in the document. Inasmuch as <<loadTiddlers>> processing has minimal user interaction, you might not notice which tiddlers are being replaced during the import. Sure, a backup file is usually created when you save the document, but backing out the updated tiddlers while retaining any other changes you might have made can be a real hassle and should be avoided whenever possible. At the very least, a manual 'save file' action means that the user has a *chance* to review what was imported *before* overwriting their saved document. -e Eric Shulman TiddlyTools / ELS Design Studios --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
