Peter Damoc wrote:
Does your app work? Is it reasonable to maintain? If so, don't rewrite.
It's a learning project... No time or cost considerations. The original is not compatible with current pyhon/wxPython versions. And the original was also a learning project, thus it has a lot of convoluted code I'd like to clean up.
I agree with Josiah... if is not broken... don't fix it. You risk a lot due
to Second System Effect <http://c2.com/cgi/wiki?SecondSystemEffect>
However if you like to read more about MVP/MVC take a look at
ModelViewPresenter
<http://wiki.wxpython.org/index.cgi/ModelViewPresenter>page from the
wiki.
I for one am for MVP, I've used it in my projects and I do believe that for
large projects it is easier to maintain. For simple projects... it might be
an overkill.
Very interesting - IIUC, MVP basically splits the controller from MVC into the presenter and interactor(more clarity, that's good). And the listening/callback techniques are simplified by removing them from the model, and maintaining a presenter 'update state' dependent on whether view events are initiated by the user or by the presenter updates themselves(cleaner model, also good).
I need to 'think' about how my original dictionary issue gets handled by turning Listening on/off, but at least the Model is simplified, and conventional object methods should behave as expected, without being concerned with callbacks. Ahhh, So much time, and so little to ponder 
Yeah, Right!
Thanks,
Dan
ยทยทยท
On 9/5/06, Josiah Carlson <jcarlson@uci.edu> wrote:
Peter
--
Dan Cherry
dscherry (@) bellsouth.net
Finding a solution to a problem doesn't solve the problem...
Implementing the solution solves the problem.