[SciPy-user] SciPy and GUI

Jeremy Sanders jeremy@jeremysanders....
Mon Jan 26 10:59:44 CST 2009


Gael Varoquaux wrote:
 
> On the other hand, matplotlib's model is very much imperative and
> script-based. This makes it easy to understand, but really is not the
> right paradigm for interactive applications in an object-oriented
> language. Chances are that, unless you are very experienced with the MVC
> pattern and interactive application design, you will make architectural
> errors when building an interactive application with Matplotlib. Chaco
> will constrain you, force you to do things according to its model, which
> you will hate (we all did at some point), but later on you will be happy
> that it enforced on you some object-oriented structure, on some
> separation of concerns (think model-view-controller, which can be
> transcribed in terms of data-plot-interactor in Chaco). In addition, the
> fact that Chaco plugs into Traits seemlessly gives you a huge amount of
> benefit for interactivity. The focus switches from registering callbacks
> all over the place to reactive programming on attribute modification.

Veusz may be an alternative option (disclaimer - I wrote the thing). It is 
object-based and would naturally fit in a PyQt system as it is written in 
PyQt.

http://home.gna.org/veusz/

You can simply inherit the Veusz SimpleWindow to get a QWidget you can stick 
in your application.

Jeremy




More information about the SciPy-user mailing list