Peter Kirchner wrote: > > Read Status.html and search the archives related to javadx . I think the > entire thread is covered by the above. > > javadx was designed to enable use of dx from a browser (i.e. running visual > programs, not programming them). For the dx > user to give access to interactive views of their data without giving up the > programs and data, there is no good > alternative. Even if posession of the programs and data is not an issue, > for the uninitiated, installing dx, an X > server, transferring programs and data, sorting out environment variables, > unix permissions, etc. etc. can discourage > casual attempts. Instead, here's a URL, and go. (well, enable java, open > the java console, and try to figure out why > it isn't working from there... it isn't always as trivial as we would like). > > The VPE is a hefty bit of X/Motif code making javafying the VPE difficult. > And where would you "save" the program and > who could modify it? how would you authenticate? Would you disable the > System() module? What advantages --to the > programmer-- would this offer? The goal of javadx is clearcut, with a large > pool of prospective users, with clear > advantages (e.g. easy access, no client installation) to offset the negatives > (e.g. slower and more constrained than the > workstation implementation). That said, someone might have a vision and want > to implement some portion of VPE function > in java. I'd suggest discussing it on opendx-dev before embarking, though. > > The goal of "I want to program DX but I don't want to have to install X on > my win32 machine" is really separate and, I > think, being addressed. I don't know if it will be free, though. David?
Ooops... Peter I didn't mean actually the vPE... I meant the control panel or what it is called ... Sorry about that confusion... But I guess what Kate wrote about the CLASSPATH is my problem.. Thanks... and Sorry again... Alex
