Currently at a fork in the road as far as allocating a highly variable model/view build.
Several QMenus all trigger a singular model/view; within which are relativistic formatting parameters
determined by a indication string detailing the type of model/view needed (included w/the button trigger).
While things run 'fine' at current, I have some concerns about moving the design beyond the bench - and making it available to new users. In that, will this manner of condensed capability result in errors down the road?
As broad as the question may be, I feel I can narrow it best by the following:
Is a multi-tool or swiss-army-knife style (as far as capabilities within a single model/view) acceptable?
Or is it idealized to divide each particular model/view format into its own module (*.py file)?
Best thanks,
Bookmarks