oship-dev team mailing list archive

[Roberto Siqueira <siqueira@xxxxxxxxxxxxxxx>]

Hi, Tim:
 I've done a fresh install of the "adl2py" branch on my home computer, 
and the installation went flawlessly. [So, no problems with this step.] 
After launching the server (with: bin/oship-ctl fg) and browsing to 
http://localhost:8080, this is what I observed:

- The password has changed. It is no longer "admin", as described in 
https://answers.launchpad.net/oship/+faq/391, but "abc123" [Is this the 
new default value for the main trunk, as well? If so, faq/391 needs to 
be updated];

- The 4 files:  device_v1.py,  level_of_exertion_v1.py,  encounter_v1.py 
and blood_pressure_v1.py were (re)created (under .../openehr/py_files/) 
every time I clicked on a newly-installed: "oship (oship)" application 
[Shouldn't be only once, and just when the "Setup" function: 
http://localhost:8080/oship/setup is run (which, by the way, does not 
exist yet)?];

- Except for the bad "Setup" link (already cited above), the 
instructions at http://localhost:8080/oship/setuppage seem clear enough, 
for a developer;

- I've got an unexpected: "ValueError: time data did not match format:  
data=yyyy/mm/dd  fmt=%Y/%m/%d" when I tried to add a patient (on a new: 
"bptrack (bptrack)" application).

 That's all for a quick "weekend" run, I'm afraid. HTH,
Roberto.

Tim Cook a écrit :
> Are there at least two people that will commit 2 - 3 hours this weekend
> (9-10 May) to evaluating the lp:~timothywayne-cook/oship/adl2py branch?
>
> I would like to be sure that it installs, operates (as far as
> advertised) and the application developer's documentation makes sense
> before committing it to the trunk.  This represents a huge advance in
> OSHIP.
>
> This update represents (probably) in excess of 200 hours that I have put
> into it.  Please help me out here and do a little evaluation.  Record
> some bug reports on Launchpad etc.
>
> I'll be sending a more detailed email on Friday as far as what should be
> checked.
>
>
> Thanks,
> Tim
>