Hello Jeremy > > Deserializer modules are loaded in boot.js just before loading the > tiddlers of the wiki: > > https://github.com/Jermolene/TiddlyWiki5/blob/master/boot/boot.js#L1783 > > I think there's an error: we should load the deserializers again after > loading all the tiddlers, in case a new module has been defined. >
What if I want to create a new deserializer? Makes no sense to load a deserializer after al tiddlers are loaded. That's why I did not include the deserializer as a tiddler, but I created them on the fly. > > > Because currently I load the tiddlers before the startup startup module. > Will be my deserializer modules loaded at that point? > > Are you dynamically creating the tiddlerdeserializer modules on the fly? > > Yes I do That's probably not the best approach. You can build deserializer modules > that dynamically modify their behaviour according to global configuration. Sorry, I did not get this point. I understand that I can create deserializers that behaves differently depending on global configuration, even depending on the tiddler type, they are just functions after all. But, if I create them after all the tiddlers are loaded.. when will I use it? This makes sense If I load the tiddlers after start-up, during the normal wiki process. Maybe is what you expect? to load the "files based" tiddlers on a sync module? -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
