Open GoogleCodeExporter opened 9 years ago
[deleted comment]
I agree that you can simplify it by adding the replace keyword, but I think a
better question is should this be common use? The argument could be made that
you should only create the window once, populate it, and then re-use it on
future runs of the code. Your common pattern becomes:
self.win = getWindow(self.NAME)
where getWindow will either return the existing window or build one. This could
have the side effect of encouraging MVC patterns (which I find to be a good
thing) by having the getWindow function act as the view creator.
An argument against this is that during development you often need to rebuild
the window but that can be solved by a small alternation to getWindow that
wouldn't go into production.
Original comment by tdor...@zindagigames.com
on 10 Apr 2013 at 9:32
Original issue reported on code.google.com by
chad...@gmail.com
on 10 Apr 2013 at 8:44