Hi Erwan
> It sure has, indeed, but it also has strengths that might be out of reach in
> pure TW: I've come to realize that, in some use cases, if using external
> scripts (made possible thanks to the node.js TW interface) can fit the bill
> more easily than pure TW, why not? But I'm aware
Thank you for that! Does that mean if I want to eventually have concurrent
access and widespread access to all patient data I should seriously consider
tiddlyweb?
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group
Hi Dave,
I have not done larger projects in TW myself so far, but here are a few
things to give you an idea of what might be a good start.
TW with nodejs works by having a nodejs server in the background which
delivers a fully funtioning TiddlyWiki to the browser which then has its
contents
Am 27.09.2015 um 19:42 schrieb Dave:
Thank you for that! Does that mean if I want to eventually have concurrent
access and widespread access to all patient data I should seriously consider
tiddlyweb?
It does mean that by the time you are getting to that, you can only hope
that there is a
I have a project I'm thinking of starting in TW5 having made some progress in
the past with TWclassic, but I think most of the cool developement is happening
now and in the future with TW5.
So I'll be kind of starting from scratch. I have a best practices question:
<<
(having decided that
5 matches
Mail list logo
