montymxb / banter Goto Github PK

The reader will be accessed by the core to get data from a file, process or folder. The program state will be passed to the reader to determine which to use.

The core part of the program should handle interacting with the reader and the mapper for the cli.

Final exit point of the program. Writes render-ready data out to a given destination as indicated by the current program state.

The cli for the first program needs to be implemented. Will break apart command line args supplied to the program. These args will be used to set the program state used later on.

The second program will take and display render-ready data from the first program (cli). This will likely be done in python or another language with decent graphical support. This program will have to be designed around available graphics APIs for the target system (ex. directx on windows, opengl on mac, etc.)

The command line args need to be validated in order to continue on with the program. I figured we could put the Usage here as well. So if we do:

banter 

Then the usage will be printed out. From there we can implement piece by piece as well. If we could draft the usage up first then that would help tremendously with figuring out what still needs to be done

The mapper will take reader data and construct render mapping data. This will be passed back from the core to the outputter at the end of the program. The mapper will need to map data for position, coloring, and specificity if sequence identification, comparison or analysis is desired.