The build system of OpenOffice is fantastic.
by
CyricZ
·
· Score: 4, Interesting
The build system of OpenOffice is truly a fantastic beast to study. Indeed, when one looks deeply at it you see the sort of work that needs to be done to support the building of a massive C++ application with many different compilers on many different platforms. It's truly a feat of engineering what they accomplish in the build system alone, completely ignoring OpenOffice itself.
-- Cyric Zndovzny at your service.
Re:The build system of OpenOffice is fantastic.
by
rdwald
·
· Score: 4, Interesting
The build system of OpenOffice is truly a fantastic beast to study. Indeed, when one looks deeply at it you see the sort of work that needs to be done to support the building of a massive C++ application with many different compilers on many different platforms. It's truly a feat of engineering what they accomplish in the build system alone, completely ignoring OpenOffice itself.
I guess that's why it takes 5 hours to compile in Gentoo, then. I wish I were exaggerating.
Re:Just a Microsoft Office clone
by
Kjella
·
· Score: 4, Interesting
Anyone want to have a go at rethinking word processing, spreadsheet, and presentation software?
Lots of people are ready. The users don't want to.
-- Live today, because you never know what tomorrow brings
OpenOffice in government contracts...
by
Spoing
·
· Score: 4, Interesting
I need help.
I have a good chance to include the OpenOffice format (specifically, a reference to the Oasis Open Document specification), as part of a specification for a US Federal Government system. The current specification includes MS Office formats as acceptable document formats for reports, etc...and OpenDocument would be inserted along with MS Office as an acceptable report format. This specification will be the basis for a few more related specifications.
What I need are references to other US federal (preferred), US state/local, or non-US government use of OpenOffice (the app) or OpenDocument (the Oasis document standard). The higher profile the better.
So far, I've scraped up a couple references but not enough to make a simple and direct case for the inclusion of OpenDocument. (The practical and technical benifits are not always a good argument to make...who's using what seems to be more effective.)
-- A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
Ever store a pointer in a long?
by
soullessbastard
·
· Score: 4, Interesting
Disclaimer: I am a Mac OS X OpenOffice.org developer and a founder of the NeoOffice project.
Ever write code that just stores a pointer in a long and assume void * is the same size? Ever written Win32/Mac code where you dump a pointer in a window reference constant and then just cast it out? This happens quite a bit in the OpenOffice.org code. Of course, since such assignments require casting, they're still valid even if the size of void * is no longer the sizeof long. gcc4 may spit out a warning at you, but it'll still be valid C.
I could go off on how a word processor/presentation program really should have no underlying need to address more than 2GB of memory, but I'll leave that for another time...I almost can fathom spreadsheets, but really the unsigned int row index will bite you in the ass *waaay* before a 2GB per process memory limit:)
Slashdot Mirror
The build system of OpenOffice is truly a fantastic beast to study. Indeed, when one looks deeply at it you see the sort of work that needs to be done to support the building of a massive C++ application with many different compilers on many different platforms. It's truly a feat of engineering what they accomplish in the build system alone, completely ignoring OpenOffice itself.
Cyric Zndovzny at your service.
Anyone want to have a go at rethinking word processing, spreadsheet, and presentation software?
Lots of people are ready. The users don't want to.
Live today, because you never know what tomorrow brings
I have a good chance to include the OpenOffice format (specifically, a reference to the Oasis Open Document specification), as part of a specification for a US Federal Government system. The current specification includes MS Office formats as acceptable document formats for reports, etc...and OpenDocument would be inserted along with MS Office as an acceptable report format. This specification will be the basis for a few more related specifications.
What I need are references to other US federal (preferred), US state/local, or non-US government use of OpenOffice (the app) or OpenDocument (the Oasis document standard). The higher profile the better.
So far, I've scraped up a couple references but not enough to make a simple and direct case for the inclusion of OpenDocument. (The practical and technical benifits are not always a good argument to make...who's using what seems to be more effective.)
A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
Disclaimer: I am a Mac OS X OpenOffice.org developer and a founder of the NeoOffice project.
Ever write code that just stores a pointer in a long and assume void * is the same size? Ever written Win32/Mac code where you dump a pointer in a window reference constant and then just cast it out? This happens quite a bit in the OpenOffice.org code. Of course, since such assignments require casting, they're still valid even if the size of void * is no longer the sizeof long. gcc4 may spit out a warning at you, but it'll still be valid C.
I could go off on how a word processor/presentation program really should have no underlying need to address more than 2GB of memory, but I'll leave that for another time...I almost can fathom spreadsheets, but really the unsigned int row index will bite you in the ass *waaay* before a 2GB per process memory limit :)
ed