Ahoy !!
We've done a tonne of work !  Close 50+ bugs (https://github.com/orgs/MyRobotLab/projects/1)

But wait there's more !  ... We've made better documentation, now all our Services Pages which document our MRL building blocks have an auto-magically linked Python example at the bottom ... called "Examples"

But wait there's more ! ..  A MRL service called the Test service - can auto-magically test each and every one of these python scripts - not only during each build, but on different devices too !

So I'm now in the process of virtualizing hardware in all the scripts to make them worky without hardware.  I do it in a way that I hope is clear, and you can turn off virtualization simply by changing someVirtualThingy = False at the top of the scripts.

Let's take a peek at the InMoov "Service Page"

http://myrobotlab.org/service/Inmoov

When you scroll to the bottom of the documentation you'll see an 

Examples:

and below you'll see our awesome InMoov script ... but its not so awesome..  I think it can be much more awesome since I have virtualized the hardware.  I'm curious about the differences of this script vs "other" official & non-offical scripts, perhaps its time we normalize ?  What is the difference between using startup batch files too ?  
 
"As a user" .. I want the service/InMoov.py to do lots of cool things, and be worky every release !! (Is that too much to ask for ? .. I don't think so)
 
This script is pretty  "weenie" .. needs more meat !

USE THIS LINK FOR THIS PAGE - SINCE IT IS THE DEVELOP BRANCH  !!! - http://myrobotlab.org/content/inmoovpy-service-page-script?branch=develop

[[service/InMoov.py]]

 

Hi Gael !

I'm glad you asked,

because when scripts are under pyrobotlab/service/{serviceName}.py they become Auto-Magical !

They are "auto-magically" included in documentation at the end for each Service Page.
They are "auto-magically" referenced in help menus.
They are "auto-magically" included in "examples"

/service/{serviceName}.py most "auto-magical" aspect is :

Testing Every Build !

Wuh ? did I hear that right. Someone is going to test these python scripts every single build.  So testing everytime the code changes ?  Who has that dedication ?  Who has that stamina ?  Who can be testing 24/7 365 days a year ?

Auto-magical Elves !  That's who 

Ok, so thanks for the direction .. I'll look at the scripts references you sent and start updating

/service/InMoov.py
/service/InMoovHead.py etc ...

Because the elves are very eccentric and particular, they will only look at scripts which are placed in :
/service/{serviceName}.py

They also live in the virtual world....
And don't really see "real" hardware, but must use virtual hardware..

They are funny that way ..

InMoov service need documentation refresh !!! and little inventory...

- We need testing script for humans ( sometime humans like to do the job of auto-magical Elves , and they like to understand how a single file with few code lines worky , for education )

- We need testing for Auto-magical Elves

- We need a switches to launch the magic, out of the box

- We need to merge !

 

First, the inventory, about what I know ( lot of things ?? )

Minimal testing scripts used by humans :

https://github.com/MyRobotLab/inmoov/blob/develop/InMoov/testScripts/

Magical script ( start_inmoov.bat is the switch )

https://github.com/MyRobotLab/inmoov/blob/master/InMoov/Inmoov.py

Service script & documentation

https://github.com/MyRobotLab/pyrobotlab/blob/master/service/InMoov.py ( InMoov.* )

Test script used by compilater

( Is this Service script ? )

 

So. Maybe we can use Minimal testing scripts used by humans, for Auto-magical Elves.

By exemple if they see rightPort = "COM42" -> They decide to mount a virtual arduino

Maybe auto-magical Elves can test Magical script too ? By default it launch allready virtual things. Ant It will be usefull for us.