JDEE can be used pretty well with a dumb terminal, but I like to use xt-mouse so that I at least have mouse support. I don't know what you do about packages like Speedbar that open new frames. Most of the time I do as Paul suggested -- I run a PC X client (Exceed) into our Unix server.
Yes, you can and should certainly set up shared resources on the Unix server. Probably most of your jar files and Unix executables (emacs) will shared. Each developer will probably want his/her own web server and development workspace. Of course each developer will also have a personal .emacs file that s/he will waste hours honing ;-) Our development shop has a nightly jar file that is compiled on and published (via samba) from a Unix server. Developers can either develop directly on PCs (Windows and Linux) or use Exceed to run Xterms and emacs on the Unix server. I like doing my development on the Unix server because I find it easier to continue working on the files when I get home and access the Unix server from home. I now have a fast enough pipe that I can viably throw xterms and emacs windows across the internet, but if you have slower connection you might want to do you editing locally at home and occasionally pump the files back to ther server at work. I used to use mac's ange-ftp (which now has a new name) for this. Other folks do their development on PCs using NT-emacs or a variety of PC-based editors and IDEs. We use CVS for version control and that works well from PC, Linux or Solaris. Hope that helps. -----Original Message----- From: Paul Kinnucan [mailto:[EMAIL PROTECTED]] Sent: Monday, February 25, 2002 12:31 PM To: John Cobo Cc: [EMAIL PROTECTED] Subject: Why JDEE ? John Cobo writes: > Paul, > > I am looking to set up a shared JAVA development > environment on a (UNIX) server which allows several > developers to use it from their clients PCs. > > I am new to this stuff, but it seems that Forte, Net > Beans, etc. all assume that the user is sitting on the > machine they are developing on. Correct ? > I don't know. > Am I correct in thinking that your JDEE allows a > single set up of the JDK, Emacs, Tomcat, Web server, > any shared JAR, WAR files for the development team, > etc. on a shared server. Developers can then 'simply' > access the environment through a window on to the > server ? > Do you mean use a shell window running on a PC to open an instance of Emacs on a Unix server and then interact with the Emacs running on Unix through the shell window running on the PC? Although I've never tried working this way, I'm pretty sure it would break some of the JDEE's features. A better bet would be to run X Servers on the PCs that would allow the PC users to start instances of Emacs on the Unix server that could then display on the PC in a full window that supports all JDEE features. You could use the server to maintain a shared source code repository from which developers created their own sandboxes on their PCs. I am copying this reply to the JDE mailing list' in the hopes that other JDE developers who have had more experience developing web server apps can give you some advice. Paul
