So, I checked in a sketch of how we can organize the steve-web. The beauty of this setup is: has a place for unit tests the organization generally follows how the python community organizes projects (plus my own preferences :) has a place for unit tests it’s pip installable has a place for unit tests it uses tox for clean testing has a place for unit tests Did I mention it has a place for unit tests? :) (feel free to smack me)
Last week when we talked about making code base more modular, I mentioned that I thought that it should be broken out into several parts: steve-core - generic base level utilities and model management - the M and C of MVC steve-commands - standalone commands for vote management - command line C of MVC steve-web - the web site that Daniel is working on - the V of MVC steve-attic - the old perl etc. code base No one seemed to object so I’ll start the refactoring. Daniel, you can forge ahead and I’ll try to copy your stuff over as I go. The only change is that the core will be Flask but it seems that much of your logic is in JS so the L&F of the site won’t change, nor the application logic. The Flask API will dispatch back to your code so it should be pretty familiar to you Daniel. I am eager to hear your comments as work progresses! At some point you, Daniel, need to stop and we’ll bring the new stuff up to date and we can start coding against that. Regards, Alan
