Comment 3 for bug 691750
Revision history for this message
| Bryce Harrington (bryce) wrote Re: [Bug 691750] Re: application window class should be in a separate file | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
On Mon, Dec 20, 2010 at 02:28:56PM -0000, Michael Terry wrote:
> Well, sort of. The latest code has moved most of the code to a
> BaseProjectWindow class. But there is still a bit of the class in the
> main script, for the user to modify and customize.
>
> But I'm actually thinking now that I'm not sure why we have any widgets
> in the main script. That it should be reserved for initialization code
> (which is getting larger all the time as we add more features and the
> ability to launch from /usr, /opt, or bzr). That way, the python module
> would hold all the widgets.
>
> I'm re-opening with that intention. Maybe we can rename
> BaseProjectWindow to just ProjectWindow and move the last bits of code
> into it.
Yeah, a pattern a lot of python applications seem to follow is to have a
relatively minimal exec script, and nearly all the real logic in module
files. For some, the only logic in the exec script is option handling
(which quickly moves to other files).