[Prev][Next][Index][Thread]
Re: Java Future
>
> Hint Hint Hint
>
> Instead of the usual approach of developing a stand-alone
> Java browser how about a Java DSOM object.
> The product would look something like this.
>
>
> |-----------| |----------|
> |awt | methods |JAVA |
> |(Visual |<------------>|(DSOM |
> | part) | | object) |
> |-----------| |----------|
> ^
> |
> |
> |
> |
> |-----------| |
> |3rd party | methods |
> |application|<-----------------|
> | |
> |-----------|
That's an interesting idea. Problem is, if you
do SOM stuff, it is a lot easier to use the commercial
compilers than EMX. (I only have EMX).
I have managed to get some of the SOM examples
from the SOMObjects 2.1 Toolkit to compile with
EMX, but it is a pain.
Does anybody have experience doing SOM + EMX?
--
Craig Rodrigues | Life always looks clearer through the bottom
Chemical Engineering | of a beer bottle.
University of Toronto |
rodrigc@ecf.toronto.edu | http://www.ecf.toronto.edu/~rodrigc
------------------------------------------------------------------
OS/2 Java Porting mailing list: sl65r@hyrum.declab.usu.edu
To unsubscribe: send to above address with the single word
"unsubscribe" as the subject. (the message body will be ignored)
Any problems with the list service, please email sl65r@cc.usu.edu.
------------------------------------------------------------------
References: