[475] in java-interest
Re: Java on OpenDoc
daemon@ATHENA.MIT.EDU (Mark Richer)
Fri Jun 23 16:03:44 1995
Date: Fri, 23 Jun 1995 12:43:44 -0700
To: kevinpu@attachmate.com (Kevin Purcell), hotjava-interest@java.sun.com,
java-interest@java.sun.com
From: richer@island.com (Mark Richer)
Cc: edanuff@protagonist.com
>OpenDoc provides a cross-platform mechanism for automation, as extension of
>the OSA but provides no policy in the form of a cross-platofrom scripting
>language of choice. Java could be useful in this as becoming the OpenDoc de
>facto cross-platform language.
If SOM succeeds, then one should be able to use the language of their
choice with OpenDoc. There should be no need for a defacto cross-platform
language, which is a relief because if there is one, then it will
necessarily be C++. In fact, one should be able to mix and match components
written in different languages if this stuff works as advertised (it
doesn't yet).
Now here's some of my ideas for integrating Java with OpenDoc.
Apple is creating a cross-platform framework called OpenDoc Development
Framework. Besides supporting OpenDoc, it includes libraries for various
basic kinds of functionality like graphics, strings, collections, etc. The
framework is designed so that there are one way dependencies between
subsystems which means you can use part of the framework without using all
of it.
I have suggested to some Apple folks that ODF should have a SOM interface
rather than only a C++ interface. That won't happen in 1.0 but it could be
done for a later release. I suggested this as a long-term strategy for
making Dylan a viable language. The same can be done with Java, though it
can be viable as just a niche Internet language. However, how would you
like to have a cross-platform set of libraries at your disposal for
developing applications, component part editors, Internet applets, and
more, and be able to choose a language depending on your needs.? Or would
you rather learn to use Java and its frameworks, C++ and Apple's APIs to
write Mac applications, and VC++ and MFC to write Windows apps. Obviously
this is ridiculous if you are on the Internet and what Sun is trying to do
with Java's cross-platform libraries is just what's needed, but why is
everyone always reinventing the same wheels. It only leads to Microsoft
owning the car and parts factories. If the cars were great, I suppose I'd
even be happy.
Obviously there are several issues in getting to SUN to colloborate with
Apple (like the fact that I can't really think of any precedent for this).
One thing is that ODF supports only Mac and Windows today. Apple said at
their last developer conference that there might be a OS/2 version in the
near future. There could probably be a Solaris version if the parties
involved saw the benefits of this. I can't remember --- has there been any
announcements about OpenDoc being supported on Solaris? If not, what
component software strategy does Sun have? I know that SUN has a different
object model than SOM and a different COBRA-compliant solution than DSOM --
I guess it's DOE. Will this get in the way of SUN collaborating with Apple
and IBM?
Despite the differences between Apple and SUN and Apple's relationship with
IBM now, I think the three companies would do well to work together to
provide better solutions for developers and customers. This is what it will
take to compete against Microsoft.
_________________________________________________________________
Mark Richer, Senior Software Engineer (415) 491-1000 x2167
richer@island.com Fax: (415) 491-0402
Island Graphics Corp. http://www.island.com
4000 Civic Center Drive San Rafael, CA, 94903
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
