gsisko / roboteqpython Goto Github PK

I have to write tests to start testing roboteq serial command. All changes on Dev should receive testing coverage before being pushed to master. I'm not sure If I followed this for the serial changes, however...

Right now I am very verbosely naming everything. This is by design so that I can keep track of specific RoboteQ code, however it is too defensive. As I start to use each of these modules, the RoboteQ prefix must be removed. This will happen in a refactoring effort represented by this issue.

Need to add Unit tests to all importers before they can be pushed to master

Had to change this when project was moved to pybuilder. I Haven't done this since I am still a little bit unfamiliar with PyBuilder.

We need to be able to create dictionaries that encompass all roboteq control commands, queries, and configuration settings. Right now, many of them are defined in a header for the RoboteQ C++ API

Using clang, these lists can be converted to python dictionaries internally. Eventually, more markups will have to be supported as these commands should exists in a master list that will serve useful for documentation and testing, while providing the flexibility needed to keep RoboteQ python agnostic to the RoboteQ device it is communicating with.

I think this is going to lead to major changes to the python library design.

This will be done using RoboteQDevice, a controller that represents a device.