Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought

Over 10 years of community discussion and knowledge are maintained here as a read-only archive.

New discussions should be taken up in issues on the appropriate projects at https://github.com/PureMVC

Pages: [1]
Author Topic: Transfering Eclipse GEF experience over to wxPython and puremvc  (Read 13212 times)
Posts: 1

View Profile Email
« on: August 25, 2008, 07:27:04 »

Hello there.

I did lots of programming using the eclipse GEF-framework. This frameworks allows pretty good separation of concerns.
There is a clear border between the model, the view and the controller.

I've switched to wxPython for a new project, and am in desperate need for a similar framework.

The problem is, I seem to mix up the different terms. In GEF for example Commands are the "performing" part of the Model.
Writing all your model-changing code in Commands gives an very easy to handle undo/redo capability.
Now in puremvc Commands (to me) seem to be something totally different.

Is there any stuff that I should read, that helps me to overcome my momentary confusion?

thanks and greetings
Full Member
Posts: 47

 - daniel@onedesign.com.pt
View Profile Email
« Reply #1 on: August 25, 2008, 07:39:48 »

Hi barfoos,

I really don't know that framework and i don't work with python too, but my advices are:

- Read the "Implementation Idioms and Best Practices" you can find it on http://puremvc.org/ on the left with this label "Best Practice" you have some language that you can choose
- Look for some demos in http://puremvc.org/ and try understand how they work!

Daniel Gomes
Global Moderator
Hero Member
Posts: 2871

View Profile WWW Email
« Reply #2 on: August 25, 2008, 10:08:25 »

In addition to the Framework Overview and Best Practices documents which will inform you as to the way the separation of concerns is achieved here, you can also check out the Python demos at: http://trac.puremvc.org/PureMVC_Python/

The documents above are written with examples of Flex and AS3 but don't let that put you off. The framework eschews platform- and language- specific features in order to be broadly portable. So, although you may not be a Flex/AS3 person, you should be able to get the idea easily. In fact I don't know Python but I understand the demos perfectly because they follow the same methodology.

Pages: [1]