Move shell code to a different file

Issue #227 resolved
Samir Menon repo owner created an issue

It's time to start breaking up RobotApp. The monolithic structure seems to be hard for new folks to deal with.

As it is, if the central data share is the database, it shouldn't really matter.

There are two ways this could go: 1. We move the shell into a purely data access role, in which case it loses purpose when the data back end is redis.

  1. We move the shell into a part data access and part computational role. In this case it might still hold some purpose, but it is likely that clients will have to write some code for the computations. Should simplify this with a few examples.

  2. We move the shell into data access + computations "on accessed data". In this case, we might as well rewrite the shell in python.

Moving forward, we really should transition to a library like structure shattering monolithic components so that multiple people can contribute self contained modules.

Think about this...

Comments (1)

  1. Samir Menon reporter

    Moved to a different file that eats SDatabase as an arg. It's up to the caller to avoid threading issues.

  2. Log in to comment