Hi Danielo > > 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. >
Yes, it's a bit of a chicken and egg thing. It's one of the reasons that you may be better off creating a separate module that just syncs the media tiddlers, and doesn't affect the loading of the main wiki tiddlers. > 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? > Deserializers aren't just used in the initial loading of the wiki; they are also used in import operations. But to confirm, yes, it's not currently possible to extend the set of deserializers that are used for loading the wiki tiddlers. Best wishes Jeremy -- Jeremy Ruston mailto:[email protected] -- 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.
