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.


On Mon, Jun 15, 2015 at 7:57 AM, Danielo Rodríguez <[email protected]>
wrote:

> 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
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/CAPKKYJbjKHQF37BM9rgMMV4vwd%2BSB9_TWVyW3WGUYoN7-f5ZEQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to