Thanks to Ballard Andrews and Peter Daniel Kirchner I've no installed the commercial release 3.1.4B for HP-UX; the installation was easy and all seems to work correctly.
> Some followup regarding HP: there is a good hybrid solution. Since the > opendx dxexec has proved straightforward to build on HP, just copy the > opendx dxexec into bin_hp700 of the 3.1.4B installation. Since HP's > newer hardware has moved to OpenGL, opendx dxexec (opengl by default) is > also a better match. > > Of course, we should fix the opendx codebase so dxui compiles easily on > this platform. Perhaps someone with opendx and HP interests could > volunteer. Meanwhile, 3.1.4B binaries and keys continue to be available > through http://www.research.ibm.com/dx/transition.html > > Pete > > ballard andrews wrote: > > > >Johannes-Maria Kaltenbach: > > > > Suggestion: > > > > Since you are having problems with OpenDX get yourself > > a copy of the commercial release 3.1.4B and a "trial key". > > I am not tracking DX but I believe these are still available? > > > > > > > > > > -- > > Dr. A. Ballard Andrews > > Senior Research Scientist > > Schlumberger Doll Research > > Old Quarry Road Ridgefield, CT 06877 > > tel: 203-431-5522 fax: 5521 > ------------------------------------- [EMAIL PROTECTED] wrote: ... > However, the strength of IDL is the high-level language. It's more > complete from a programming perspective than the DX scripting language but > much more primitive from the data perspectives (i.e., IDL's variables are > only simple arrays at most). IDL doesn't handle non-regular data, even 2d, > very well or even correctly, although it gives the appearance of doing so > (e.g., curvilinear grids, triangular meshes). DX is better in that regard. > However, if you never deal with such data, than such an advantage means > little. Thus, a less general tool but one focused on your problems is a > better choice. We want to handle both, regular and non-regular data. This could be a strong point in favour of DX, but my colleage, who is testing IDL says (from reading the manuals, not from really trying it) that IDL can also handle non-regular data; we have to test it. > You can add functions to DX or have your software invoke DX. There's been > some discussions on that in the DX mailgroups and there's a lot of > documentation about that. Can you please give me a hint were to find this documentation. [A note to the documentation: I've downloaded 4 manuals in PostScript, Quick Start Guide, User's Guide, User's Reference, and Programmer's Reference; each Version 3, Release 1, Modification 4. Is there newer or more documentation available? My colleague thinks that the IDL documentation is better; decumentation is one of the points of the management's decisions matrix.] > Open vs. proprietary (bazaar vs. cathedral) is of course a subject of wide > debate, so I won't talk about the relative advantages and disadvantages of > each... I've circulated the papers of ESR, an OpenSource book from O'Reilly, etc. in our department, but they didn't even read it; they still descriminate "good professional software" from "open source (or freeware) hacking", (always with a bad connotation of hacker that I cannot understand). And the word "free" let them think on "free beer" (same problem in german as in english); pointing them to the explanations of RMS doesn't help; there are still some who think they only have to pay a lot of money to get the best (and vice versa).
