On 2/24/15 11:58 AM, Neil Flowers wrote:
The only other option I could think of would be to consider them as two fundamentally different toolkits located in two different subfolders of dabo.ui.
^^^ This may very well be the best option. I'm surprised at myself for not thinking of suggesting it.
This touches on other issues having to do with the DRY (Don't Repeat Yourself) principle. A whole bunch of code exists in uiwx that isn't specific to the wx toolkit. All along we've been like 'well, when we finally implement another ui, we'll abstract those bits away then'.
We need a 2-week sprint with John, Neil, Werner, Ed, and Paul in the same room.
If wx3.0 works, we don't need wx2.8 (older dabo versions support that). But I think we do need python 2 and python 3 compatibility in the same dabo. If adding a ui/uiwxphoenix ui helps in this regard, even if it's sort of temporary, we should consider it. Perhaps app code can still say 'loadUI('wx')' and based on the python version dabo will choose which library to use.
Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
