🚀 go-pugleaf

We plan to distribute JRE.

However, we are also interested in whether our app runs in other
environments, so we can gauge how close we are to the day when we can assume
that Java is already there, and distribute only our classes (and the
non-standard library classes, such as JGL).

(Imagine our company distributing application X which requires JRE, and
another company distributing application Y, which requires JView. The
customer, who might have, say, 5000 sites on which both apps need to be
installed, might ask me, "Will your app run on JView, so I don't have to
install two Javas?" I'd like to have an answer other than "Don't know, never
tried,"
or "Tried it, but gave up as soon as I got the first error message.")

Hence, I tried my app with JView, and will continue to experiment with that
combination, as well as others (e.g., Supercede).

Incidentally, the problem may be that JView doesn't support ZIP files. (Does
anyone know
if that is true?)

Chris Dickerson wrote in message <63h0q9$o5n5@forums.borland.com>...
>>I'm trying jview not because I have any problems with jre, but only
because
>>I want to try as many runtime's as possible to get a feel for the
>>universality of my app's deployment. Eventually, I'll want to try it on
>>Unix, too, and I don't think I can get jre for anything other than Sun
>>systems.
>
>
>Marc:
>
>    Since Microsoft is the only one not wanting to play ball..
>    why program for their VM anyway? Distribute Sun's JRE as the
>    desired method of operation..
>
>
>Regards,
>Chris Dickerson         | web http://www.tsc.com/~chrisd/
>Technology Service Corp | JBuilder http://www.borland.com/jbuilder/
>chrisd@tsc.com          | paper
>http://www.borland.com/jbuilder/papers/visualjpp/
>
>
>