Hi Danielo
And this is where I get confused. I understand the need of this, that is
> not my problem. The problem is when I want to create globals that should be
> available from the browser side, but they only has sense if we have a node
> environment behind.
>
The only thing that can create globals on the browser side is a module that
is executing in the browser. So that means a plugin included in the browser
wiki. The plugin would also have to be installed in the Node.js wiki, so it
would be coded to only activate itself on the browser.
> The filesystem adaptor runs on the browser right ?
>
Well, it's executed, but it remains inert when require("fs") is undefined.
> So I have to set my modules to run on node and the browser. This is
> getting more and more twisted. Basically I need globals which information
> is from the FS, so only the node instance has access to them, but I want
> them to be available on the browser... this is getting confusing as I said.
> Now I understand why yo insisted on creating a new syncadaptor module.
>
What is it that the plugin in the browser needs to do in your scenario?
Does that help?
>>
>
> Yes it helps. One question. What if my sync-adaptor returns fat tiddlers
> when it is asked for skinny ones?
>
It would work, but would negate the advantages of lazy loading: you'd load
all the tiddlers as fat 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.
