Timeline for Python - Architecture for related instance attributes
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 3, 2017 at 19:03 | vote | accept | Johndt | ||
| Jan 31, 2017 at 18:35 | history | edited | Jonathan Eunice | CC BY-SA 3.0 | deleted 2 characters in body |
| Jan 31, 2017 at 18:23 | comment | added | Johndt | And thank you for your guidance in a OOP design. I have definitely made use of inheritance where possible. One thing that I could improve upon, and that has been bothering me, is separating the business logic from the view logic (as it should be in a MVC design). PySide has brought its own challenges in properly implementing an OOP design and following Python conventions, as it has some serious quirks. For example, if a widget goes out of scope, it is automatically garbage collected. But you bring up some very good points, and I'll evaluate my code and attempt to improve the OOP structure. | |
| Jan 31, 2017 at 18:18 | comment | added | Johndt | Thanks for the answer! I apologize that the example is a bit silly. Don't worry, I'm not trying to create my own application framework, I'm actually creating a PySide/Qt application. The example given above seemed a good way to provide a minimal code example that required 0 knowledge of external libraries. | |
| Jan 31, 2017 at 15:17 | history | answered | Jonathan Eunice | CC BY-SA 3.0 |