Frank Schönheit - Sun Microsystems Germany wrote:
Hello Barbara,
Ouch! Me and my big mouth, and my obligation to put my "money" where my
mouth is!
:)
The languages that I worked in were mainframe-based, as you
can probably guess from the timeframe (S/360 Assembler, anyone?), and
didn't include Java or any of the C variants (though I have an in-house
expert in C/C++ in my son). Those are the implementation languages for
OOo, right?
C++ instead of C, then yes.
I'll admit, the idea does intrigue me, though I don't know just what I'd
be getting into or how much time it would take. I'm certainly used to
learning new languages quickly, of course, since I worked in IBM's
Federal Systems Division and we had to code in whatever the government
had bought! But assuming I'm willing to bite the bullet, how would I get
started? From the other stuff we've been talking about around this
issue, I'll need to get into wiki authoring first, but maybe after that
I could give it a try.
Setting up the environment to build OOo is the first pre-requisite.
Depending on your preference, this could be done on Linux or Windows
(well, of course also Solaris and FreeBSD and Mac and other supported
platforms - but the majority probably uses Linux or Windows). Linux is
reported to be easier to get it to fly, Windows is more convenient on
the long run, if you appreciate a development IDE / debugger with all
bells and whistles.
There's a whole category in the Wiki collecting developer-related
things: http://wiki.services.openoffice.org/wiki/Category:Development.
I'd say http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org
could be the first the entry point.
Ciao
Frank
Thanks, Frank. I'm on WinXP at this point, but probably not for too much
longer.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
