[wxpython-users] code structure - suggestions? (classes for
gui, data, calculations...)
Igor Jese
igor at jeseonline.com
Mon May 19 07:23:00 PDT 2008
> You can do it in similar manner even more robust: your classes that
> actually do something (the "model") in one file, GUI in 2nd and flow
> (the "controller") in the 3rd (of course you can have more than one for
> each, where needed)
PS. And if you have enough "utility" functions (you mentioned
calculations, for additional example you can have charset transcoders and
similar), put them in the 4th file. Usually all packages (GUI, Model,
Controller) can use the "utilities" freely.
So to recapitulate: GUI uses only Utils, Model uses only Utils, Utils
doesn't use anything, Controller uses everything
Igor
--
Igor Jese, igor at jeseonline.com
http://MockupScreens.com
http://SimpleProjectToDo.com
More information about the wxpython-users
mailing list