>
> This means your module is active from the beginning on. Sounds like a
> startup module to me. not a library and not a widget.
>
Yes. In fact I was thinking in a syncer module, but there is no such type
of module. There is only one syncer and it is a module type of global. As I
said to Jeremy, maybe I can create a startup module that initializes my own
syncer. I have been inspecting the code of the syncer module and has some
methods that are exactly what I need but not all of them are exactly "how"
I need.
> Hmm, maybe you should be careful here.
>
Sure :)
> Either (1) your module works in the background and is not imported or
> directly used by any other module (something like a daemon in linux)
>
I think I will go with this implementation.
> or (2) it is directly referenced by other modules that call its functions
> and actively trigger actions ("on demand"). If it works in the background,
> it works invisibly and maybe uses queues or an event-subscriber mechanism
> to process events.
>
>
I think it will be better to let it work in the background. I will keep the
functions that uploads and downloads things to the server in the utils
module, so any widget can use them also.
--
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.
