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 synced with the server. The current process however is unsafe
for more than 1 concurrent user, so either way, unless you make the
necessary changes, your system will only be safe for 1 concurrent user.
By that I mean the nodejs-version and a TW that is synced between computers.
If you create a separate TW for each of your clients as a file, then you
will not have this issue, as now people can edit different client files
without interfering, as long as they edit different clients. That
however, as you pointed out, means that the data will also be separate
and it will be harder to aggregate. So be aware of the limitations to
the number of concurrent users your system can handle.
I would however use one single TW instance for all the data, because TW
really only shines, when you put all the data into it (much like
evernote). The nodejs version is pretty fine for a single user, as it
also means that the data will be kept in individual files that are more
likely to be accessible and compatible by other programs you might use
to work with that data. It also means that it won't be as portable as a
single TW file.
When it comes to your actual application, I can only advise you to keep
your data consistent. By that I mean well defined field names with well
defined definitions as to what data type they contain. TW is actually a
database application in that sense, but one that doesn't enforce that
type of consistency by default. You need to have a consistent model if
you want to work with the data later on. (so make sure there are no
ambiguous inputs or things you have to do manually everytime, like
typing out a specific tag, a specific field name and so on)
When it comes to selling, TW is under a BSD license, which as far as I
know does permit you to sell the final product.
I realize my answer was very broad, if you have any more questions, I
will be happy to address them in a little more depth.
/Andreas
Am 27.09.2015 um 16:42 schrieb Dave:
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 I'll be using TW5 with nodejs) Would it be better to make one TW per client and
import any design changes from a "master" TW file (that was the plan with the TWc version), or
would it be better to have one single TW5 (synced between computers) and access the multiple client
"files" by unique tag in the one system? And if that were the case would it be better to
develop it in tiddyweb (accessible only through intranet)?<<
Here's the use case: I'm a chiropractor seeing multiple patients a day, keeping
track of various symptoms and test results that change gradually over time and
depending on progress generates the need for various modifications of treatment
modalities, e.g. exercises, etc, as well as running suggested prioritized
diagnosis suggestion lists and plans of management options.
Although it would be nice and tidy to have one file per patient, I also at one
point in the future want to be able to compare findings between patients, like
for research (how many patients that I treated by method X got better by Y
points over timespan Z; or, what's the average first measurement of neck range
of motion between age 30 and 50?)), mainly using fields and tags.
Any time I describe what I want, most people just say I should build a database
program, but a) I have no experience with them and b) I just really like
tiddlywiki because its so flexible.
Lastly, I'm an intermediate level user with no formal computer programming
training, slow but steady learner. I've modified plugins (TW classic) but never
made one from scratch.
Any suggestions for a scenario like this?
Oh, one last thing... if I ever actually achieve what I'm dreaming of, what are
the monetization implications given the current licence? Could I sell this to
other chiropractors/ companies? If not, that's fine - I'm going to proceed
anyway and may just eventually just release it if it passes muster.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" 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/tiddlywiki.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/56081232.6090000%40googlemail.com.
For more options, visit https://groups.google.com/d/optout.
