How to write a tiddlerdeserializer

[Danielo Rodríguez]

Hello

I am trying to write a tiddler deserializer for this task: extract tiddlers from a custom file extension.

I know that I have to create a module-type: tiddlerdeserializer, I did, but i have no clue to where register the fileExtensionInfo. Currently I'm doing it on the deserializer itself, but it is not working. How should I configure this? What is the correct way? Seems easy, but I'm obviously missing something.

Thanks in advance.

[Danielo Rodríguez]

Just to be clear,

The  problem is that the files with that custom extension are not being loaded when the node.js server starts. And the place where I register the extension is just before the exports of the deserializer module.

Regards

[Jeremy Ruston]

Hi Danielo

Under Node.js, tiddlers are loaded from the wiki folder during the boot process. There's a Catch-22 with the ordering of loading the tiddler files and processing plugins: we can't process the plugins before we load the files containing them, therefore the plugins are not available when we load the files.

What is your use case?

Best wishes

Jeremy.

--
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 tiddlywikide...@googlegroups.com.
To post to this group, send email to tiddly...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/9c8854de-7b1d-4ddd-acc8-d175ec68f936%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Jeremy Ruston
mailto:jeremy...@gmail.com

[Danielo Rodríguez]

Hello Jeremy,

It's not a plugin, it's just a plain deserializer module. I want to register my deserializer for certain type of files, and make the core load that tiddlers through my deserializer. It works when the wiki is loaded already and I drag a file of that type, but it does not work with files contained in the Tiddlers folder.

[Jeremy Ruston]

Hi Danielo

It's not a plugin, it's just a plain deserializer module. I want to register my deserializer for certain type of files, and make the core load that tiddlers through my deserializer. It works when the wiki is loaded already and I drag a file of that type, but it does not work with files contained in the Tiddlers folder.

It's the same for a module: modules don't get registered until after all tiddlers have been loaded from the file system. Therefore modules in those tiddlers are not available during the loading process. See the sequence here:

https://github.com/Jermolene/TiddlyWiki5/blob/master/boot/boot.js#L1819-L1836

Best wishes

Jeremy.

 

--
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 tiddlywikide...@googlegroups.com.
To post to this group, send email to tiddly...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.

To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/16be5f47-d892-4211-9298-25a315e4d3f1%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Danielo Rodríguez]

So the only way to accomplish this is modifying the core, right? It's not even possible with an startup module. Unless you specifically search for the files of course.

[Jeremy Ruston]

On Sun, Jun 14, 2015 at 2:06 PM, Danielo Rodríguez <rdan...@gmail.com> wrote:

So the only way to accomplish this is modifying the core, right? It's not even possible with an startup module. Unless you specifically search for the files of course.

That's correct. This is an area where the boot kernel is primitive merely because the need to be smarter hasn't arisen before.

Can you expand on the use case a bit more?

One possibility may be to have your files in a different folder within the wiki folder (eg "danielo_tiddlers" instead of "tiddlers"). That way the filesystem adaptor will ignore them, and your plugin can process them when it starts up.

Best wishes

Jeremy

 

--
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 tiddlywikide...@googlegroups.com.
To post to this group, send email to tiddly...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywikidev.

To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/61c7659e-6acf-4c3c-9d60-60699eefca38%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Danielo Rodríguez]

Hello Jeremy

 

That's correct. This is an area where the boot kernel is primitive merely because the need to be smarter hasn't arisen before.

Can you expand on the use case a bit more?

I am  using tiddlymap to create an searchable comfortable way of viewing my company DB. For doing so I export tables definitions as plain text files. In order to turn tables and its properties into tiddlers with relations, I wrote a tiddler deserializer to parse the export files. I would prefer to just put those files on a certain folder and import them on startup instead of having to drag and drop them once TW has started. 

 

One possibility may be to have your files in a different folder within the wiki folder (eg "danielo_tiddlers" instead of "tiddlers"). That way the filesystem adaptor will ignore them, and your plugin can process them when it starts up.

I am not creating a plugin, it's just a plain tiddler deserializer. I think this task does not deserve an entire plugin. But maybe I should create also a startup module. But, I think this kind of things is something TW should implement sooner or later.

[Jeremy Ruston]

Hi Danielo

Without a concrete proposal for how we'd address the chicken-and-egg problem of loading serialisers from tiddlers that are loaded from serialisers (!), I'd recommend taking the approach of a separate folder within the wiki folder, and a startup module.

Best wishes

Jeremy.