On Mon, Mar 23, 2009 at 6:11 AM, Etienne Gaudrain wrote:
> Thanks a lot for the link, and for the suggestions!
> I will probably give a go to Mayavi2, but given how heavy it seems to be
> (compared to matplotlib) it probably requires some custom wrapping...
> which means again a lot time investmen
On Sat, Jul 12, 2008 at 2:35 PM, John Hunter <[EMAIL PROTECTED]> wrote:
> On Sat, Jul 12, 2008 at 3:09 PM, Barry Wark <[EMAIL PROTECTED]> wrote:
>> Work is currently going in the wrong direction for me to be able to
>> implement toolbars etc. in a timely manner. Would y
) the Cocoa native backend. As soon as it meets
the requirements, I will be happy to resubmit it for inclusion with
the matplotlib distribution (including supporting it going forward).
Barry
On Thu, Jul 3, 2008 at 12:14 PM, Barry Wark <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 3, 2008 at 8:41
On Thu, Jul 3, 2008 at 8:41 AM, John Hunter <[EMAIL PROTECTED]> wrote:
> On Wed, Jul 2, 2008 at 3:41 PM, Barry Wark <[EMAIL PROTECTED]> wrote:
>> I've written the start of a Cocoa-native backend for matplotlib and
>> would like to submit feedback on the code and on
I've written the start of a Cocoa-native backend for matplotlib and
would like to submit feedback on the code and on the possibility of
including it in the standard matplotlib distribution. The backend
implementation is not complete (image rendering and mathtext rendering
are currently no implement
On Feb 15, 2008 1:27 PM, Christopher Barker <[EMAIL PROTECTED]> wrote:
> Barry Wark wrote:
> > I'm ramping up to start building at least scipy binaries (see recent
> > post on scipy-users list). I'm just waiting for tester feedback for
> > eggs built from SVN t
ing.
numpy, ipython, and matplotlib all apear to be available via
EasyInstall, so scipy seems to be the only missing piece.
barry
On Feb 15, 2008 12:41 PM, Christopher Barker <[EMAIL PROTECTED]> wrote:
>
> Barry Wark wrote:
> > I would take a look at the Scipy Superpack (http://trichec
José,
I would take a look at the Scipy Superpack (http://trichech.us/).
Alternatively, you can download and install the MacPython 2.5 for OS X
10.4 (http://www.pythonmac.org/packages/py25-fat/index.html). This
installs a separate Python framework (leaving the system python
framework unchanged). Th
+1 for adding this feature if it's not already available!
On Feb 8, 2008 8:35 AM, Brian Blais <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Is there an easy way to turn the box of an axis off, but only the top and
> right lines, keeping the bottom and left lines of the axis visible? I'd
> like to make
just speculation, at this time... we're just getting started but will
share our results as soon as they're ready.
barry
On 12/5/07, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> Barry Wark wrote:
> > We (at my work) are just starting to think about writing a mor
Ping,
You should investigate scipy.optimize.lsqFit for using least squares
to fit an arbitrary function and scipy.odr for regular or orthogonal
least squares fitting.
barry
On Dec 5, 2007 9:45 PM, Ping Yeh <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have (x,y) data that I want to fit to the formula
>
Stephen,
The CocoaAgg backend is not supported in IPython. You can use it in
the non-interactive form (i.e. with a pylab.show() but you will have
to close the window in order to return control to the IPython shell).
It is possible to embed an MPL plot in a Cocoa application using the
same
8:00 PM, Chris Fonnesbeck wrote:
On Dec 3, 2007 7:34 PM, Barry Wark <[EMAIL PROTECTED]> wrote:
sorry instances of self.plotView.image
On Dec 3, 2007 3:38 PM, Chris Fonnesbeck <[EMAIL PROTECTED]> wrote:
I replaced the one instance of this that I found. I now get the
followi
sorry instances of self.plotView.image
On Dec 3, 2007 3:38 PM, Chris Fonnesbeck <[EMAIL PROTECTED]> wrote:
> OK, I'm having a bad backend day (insert joke here).
>
> Since I am on OSX, I decided to switch over to the CocoaAgg backend,
> but it fails when trying to show a histogram, yielding the fo
Chris,
This error is due to more stringent error checking in pyobjc2 which
ships with Leopard. I was just preparing a patch to send to the
matplotlib dev guys, but if you replace all instances of self.image
with self._image in backend_cocoaagg.py, things should work. Because
PlotView is an NSImage
Matt,
Yes, I agree. I wasn't coming at so much from the goal of making Pylab
a Matlab clone (as you point out, that's silly, and misses much of the
advantage of Python), but rather from the goal of making interactive
use as efficient as possible. When I fire up ipython -pylab to do some
quick expl
Perhaps we should consider two use cases: interactive use ala Matlab
and larger code bases. In the first case, being able to import * saves
a lot of typing and the namespace polution problem isn't a big deal.
The second use, obviously, benefits from avoiding import *.
Returning to the OP's questio
In the process of creating a Cocoa app for scientific data
acquisition, I've built an NSImageView subclass that displays an MPL
figure in the Cocoa NSView hierarchy. It's based on the CocoaAgg
backend code in MPL. There are also some subclasses that allow the use
of Cocoa Bindings to supply the dat
18 matches
Mail list logo
