[119] in DeathTongue Changes
Installed VisualJ++ 6.0, WS_FTP client
daemon@ATHENA.MIT.EDU (David Wang)
Sat Nov 21 08:21:45 1998
Date: Sat, 21 Nov 1998 08:20:00 -0500
To: licks@MIT.EDU
From: David Wang <d_wang@MIT.EDU>
I think that installing VisualJ++ is alright because Sun's JDK will
co-exist with it. However, you'll have to "instruct" the Java viewer
differently to use Sun's Java classes -- at the appletview/jview level.
This is because the Package Manager has an ordered list of places (I think
7) that an non-local package call will be looked up in. CLASSPATH and
WINNT\Java\CLASSES\CLASSES.ZIP are way down there in priority while
WINNT\Java\Packages and Java Class Code Module Registry Keys (not the VM
Registry Keys, those are down there in priority with the CLASSES.ZIP) are
way up there (right after command-line specified).
I also had the fortune (rather fortuitous, actually) to talk with the
person who coded the package manager (yup, an MIT student made this. He
claims any problems with Package Manager is not completely his fault
because Microsoft gave him very little time. He also says the loss of
power over the Java classes was intentional, by design). He says that
there's an "undocumented" place where Java classes are looked up, but he
never got around to telling me where.
So Deathtongue is now ready for some Java work now (ignoring WFC and the
like, of course).
--David
