I've been messing with making a human version of pawlabeling and so far so good. It as mostly a matter of deleting the widgets I didn't want.
While its nice and dandy that certain widgets, like on the contacts widgets are called "left_front", this information is pretty useless. What the model cares about is what contact_label something has.
So I'd like to see how I can refactor those widgets, such that they check the settings to see how many contacts they should draw (2 or 4) and what they refer to. Then I only have to add a toggle to the settings, so you can switch between the two versions (possibly restart the application) and off you go. That way I can also guarantee that the application will have one common codebase, instead of multiple versions for animals and humans
Ok this is a bit hairy, I ended up adding a boolean variable human to settings.py which tweaks several important layout things and the contact_dict. So I'm closing this
I've been messing with making a human version of pawlabeling and so far so good. It as mostly a matter of deleting the widgets I didn't want.
While its nice and dandy that certain widgets, like on the contacts widgets are called "left_front", this information is pretty useless. What the model cares about is what contact_label something has.
So I'd like to see how I can refactor those widgets, such that they check the settings to see how many contacts they should draw (2 or 4) and what they refer to. Then I only have to add a toggle to the settings, so you can switch between the two versions (possibly restart the application) and off you go. That way I can also guarantee that the application will have one common codebase, instead of multiple versions for animals and humans