From luke350 at onemodel.org  Tue Aug 22 14:00:00 2017
From: luke350 at onemodel.org (luke call)
Date: Tue, 22 Aug 2017 12:00:00 -0600
Subject: [om-list] testing the "sharing" feature
Message-ID: <7c905d22-7f0f-0351-9abc-f2ec21dc02c2@onemodel.org>

Hi all.  Remember OneModel (http://onemodel.org)?  I still work on it 
when I can.

Does anyone use it?   (I use it every day to stay organized, for 
schedule/tickler file, tasks, contacts,  capturing & organizing thoughts 
on a variety of subjects, exporting them to html and web sites 
sometimes, etc.  Extremely efficient & effective for those things, given 
familiarity.)

BUT: I am interested in anyone's input on past or future work, because 
discussion improves ideas.

The latest is:  I'm working on the basic "sharing" feature, to allow one 
OM instance (personal knowledge base) to link to another (with limits), 
copy info, see what has changed, get updates, push info, etc.  In the 
latest code in Github I've added initial support for one OM instance 
linking to another: via the Play framework, client support for linking, 
and a REST API.  The REST server currently is launched in development by 
running "sbt" and "~ run", but is to be like a simple standalone web 
server in the future).

In addition to the prior unit tests, I've created automated tests of the 
REST API and of the program's interactive menus, to make future testing 
hopefully easier.  These use "dejagnu" and "expect" (in Tcl); they do 
some setup on the test database, then they run the program & verify it.

I am thinking now to extend those dejagnu/expect tests, along these lines:
- make a shell script to create any user (replacing manual updates to 
the postgres config, at least for testing);
- make tests use that and create a new OM test instance, and start sbt 
(for now) to serve on an http port;
- make the two test OM instances talk to each other, linking information 
between them, and later other sharing of info, between them;
- automate the running of (scala) tests of the REST API that are now 
launched manually.
- if there are users who want to share anything securely, switch to 
HTTPS, and continue to extend the limited security features already in 
place.

I have many more written plans and details, just haven't yet published 
them on the web site.  One is to make it very easy to host OM instances 
so no one has to manage their own postgres instance unless they want, as 
a step toward making installation simple, even with the managed sharing 
between instances.

That means we could start having instances that can see and talk to each 
other easily, and add features with convenient testing to know we 
probably didn't break stuff.  Of course, an instructional video, web and 
mobile UI, and very easy installation, would be a big help eventually.

Questions / comments?  Wide open... Thanks.

Luke
- - - - - - - - - -
Things I'd like to say to more people (needs updating): 
http://lukecall.net  .