P Kishor wrote: > > Matthew Kenworthy wrote: > > > I've compiled PDL 2.4.6 with PGPLOT built in. I've sent to Chris > > Marshall and it should appear in the next day or so, but if you are > > (brave!) enough to try it, grab a copy at: > > > > http://www.strw.leidenuniv.nl/~kenworthy/bin/SciKarlv2.4.6.dmg > > > > I'm also grinding through the PLplot problem you're having. If I > > managed to get it built on my Mac and pulled into SciKarl, would that > > solve your problem?
I've downloaded the package. Should have it up on the sourceforge site by tomorrow. Was there a README.txt that you wanted to go with the file, Matt? > <snip> > > 1. If I can build it then I will understand it > better, and unlike other prepackaged programs, I > do have to understand PDL well in order to use it > well. You'll definitely learn how to build it. > 2. If I can build it, then it means that building > it is easy enough for other newbies to be able to > build it as well. The most important thing here is to figure out what the build problems are and get them fixed in the various project components. > In my view, that will push PDL that one small > step closer to being more usable by most normal > scientists and not just programmer scientists. It will make PDL more accessible to folks looking to contribute to PDL development. My experience is that 1-click (or less) PDL access is important to getting folks to use PDL. If they have to become a C programmer, perl programmer, and system admin to get PDL installed, they won't have much time or desire to try PDL for their science/research/work... > I have another, less scientific and less > generous reason for PDL to succeed in general > usage -- I am fairly sick of the bright-eyed > users of Numpy and Scipy here on campus who talk > excitedly about the wonderful things they can > do with Python. I want to evangelize PDL use, > particularly for remote sensing/GIS/image analysis > kind of work (essentially replace IDL without > having to use Scipy/Numpy). I would like to have a core PDL working on all the supported platforms: windows, mac os x, and unix/linux. Right now, mac os x and windows are only partially covered with the basic PDL functionality. mac os x is a bit easier to fix since many of the external libraries that cause portability issues *are* available there. Windows, on the other hand, will require us to implement a bundled package since there is not package manager for win32 software. --Chris
_______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
