>Greg, > >This is fine by me. I was supposed to help submit some ReadMe's for >different platforms and compiling, but I'd like to see an example of >what you need. The platform specific README's that exist for running >DX may only need minor fixes. > >David >
I'll use this as a cue. I have been sort of following all the great work everyone has been doing. Here are two scenarios that I've recently encountered. I figure if these are dealt with, we've got a solid delivery system. (1) I have a client new to openDX but excited about it. He wants to buy an intel laptop and install openDX. He would be happy to install Linux on same if that is better. Assume he's not a system weenie (cause he isn't). Is there a document, or can one be created, that would be a step by step recipe for installing opendx under NT and/or a recipe for installing Linux (specific to the Linux flavor), then openDX under Linux, suitable for use by a newbie? Don't react by saying if he doesn't know what he's doing, he shouldn't be doing it. We're trying to attract new players and it is necessary to do some complicated systems things to install openDX, unfortunately. He's a scientist: he wants to do visualization. He doesn't want to become a guru (any more than I do). We have to address this. I think intelligent people can follow well written instructions without necessarily understanding why it all works. A hallmark of well written instructions is a section that describes common errors or troubleshooting, not the straight line from A-Z that never seems to actually work in real life. If it did, we wouldn't have had half the mail we've had on this list. I'm not busting anyone for past efforts, just suggesting that we start thinking ahead to attracting newbies and making it work out of the gate. (2) I have another client who is trying unsuccessfully to install openDX on NT, using the commercial 3.1.4 version. For some reason they don't seem to be able to use the public key. They keep getting 5-min trial version startup. I read Nancy's note a week ago, but I'm not sure if she meant the key broke only on Feb 29 or is now broken completely. Can anyone tell me? (I know we've only got 3 weeks left on it anyway). I figure if they are having this much trouble installing the commercial version, they may not be able to get openDX for NT running either, so again, a nice clear doc on getting it up and running is needed. They are in a position (unlike some others) to purchase Exceed if that is still required. I'm confused at this point about what build of openDX requires (works with) which Exceed flavor, so I assume the README would explain all this clearly. Oh, and what Cygwin build is needed. Maybe we should approach Exceed about a deal for openDX customers...? So in summary, docs needed: Installing openDX on NT Required software, versions, costs if any, where to acquire Tips on building the basic system configuration required for openDX Known problems with other software, graphics cards that work/don't work, etc. Installing openDX under Linux Specific Linux flavor instructions Tips on building..... Known problems..... (as above) This may be more than a quick touchup of the existing docs, or maybe that is all that is needed. I'm also not volunteering Dave T. to do all this! I hope other people will participate. I will be happy to test the WinNT docs, and client 1 above would be grateful if the Linux recipe existed. Obviously client 2 will need the NT stuff soon as well. Thanks! Chris Pelkie Vice President/Scientific Visualization Producer Conceptual Reality Presentations, Inc. 30 West Meadow Drive Ithaca, NY 14850 [EMAIL PROTECTED] (607) 257-8335 or (607) 254-8794
