While crafting the ability to change quantity of fits, it's become apparent that the base Eveapraisal code was meant to do one thing and one thing well - grab a bunch of data from a textarea and parse it. I've wanted to fine tune the code to support individual fits, and plan to expand on the capabilities of fitShop (ability to add single items, etc).
These expansions to the code would be much easier if everything wasn't set in the submit() function. I've created a branch that aims to split the code into more modular sections, such as:
authenticate() - used liberally to make sure you can modify result data
prepare_results() - take the information we have about a result so far and prepare the results dict to be loaded into templates (includes market data fetching and sorting)
display_results() - actually display the result (do we need a separate function for this?)
While crafting the ability to change quantity of fits, it's become apparent that the base Eveapraisal code was meant to do one thing and one thing well - grab a bunch of data from a textarea and parse it. I've wanted to fine tune the code to support individual fits, and plan to expand on the capabilities of fitShop (ability to add single items, etc).
These expansions to the code would be much easier if everything wasn't set in the
submit()function. I've created a branch that aims to split the code into more modular sections, such as: authenticate() - used liberally to make sure you can modify result data prepare_results() - take the information we have about a result so far and prepare the results dict to be loaded into templates (includes market data fetching and sorting) display_results() - actually display the result (do we need a separate function for this?)