OpenOffice.org SDK Released
Jules V.D. writes "The OpenOffice.org group on Friday announced a kit that lets programmers build new modules for open-source alternatives to the Microsoft Office suite.This new SDK is an add-on for OpenOffice.org 1.0.2. It provides the necessary tools and documentation for programming the OpenOffice.org APIs and creating your own extensions (UNO components) for OpenOffice.org."The highlight of this SDK is the new Developer's Guide. This comprehensive guide provides, in 900 pages, a detailed description of the OpenOffice.org API concepts, the OpenOffice.org UNO component model and how to use the API in the context of the different application areas.""
I think one of the strong reasons why we have Microsoft's dominance on Office programs is the add-on programs that take advantage of APIs provided in the office. So this is a good step, although I am very suspicious about how strong these APIs are compared to MS Office.
Can you do things like embedd Open Office into Evolution? That would be spiffy. I have Office XP at work and MS Word has hijacked the standard editting for e-mail messages in Outlook.
--------
Free your mind.
You still forgot to copy MS Access, guys.
Seriously, how hard would it to be to put an easy to use interface and reporting engine on top of mysql (or postgre or whatever)?
There are a ton of workstations all across the corporate world that are running MS Office just for Access.
If you want such options then just suggest them or implement them yourself.
Exactly! That's why open sores blows! I don't give two flying shits about writing programs all day; we have people to do that sort of thing. All I want is a word processor! This guy comes up to me and says, "Try Open Office! It's just as good as Microsoft Office, and it's free!" So I try it, and find that it doesn't even do footnotes, for chrissakes! So I tell my friend about this, and he says, "WTF? If you want such options then just suggest them or implement them yourself."
What would your reaction be if you went to a car dealership to testdrive a car and discovered that the car had no windshield? Sure, it's possible to drive the car without a windshield, but who'd want to? Wouldn't your reaction be, "Gee, that's a shitty car!" And if you found little (that is, big) problems like that with every car on the lot, wouldn't your reaction be, "Gee, that's a shitty car company!"
Open sores: Gee, that's a shitty software company!
At least Microsoft gives me a fucking word processor that fucking works. Open Office is a car without a windshield or any mirrors but with a god damned 24 karat gold-plated air freshener on the dash.
When will my Karma get better?
At this rate, never.
I've played around with an Alpha version of the SDK in October, and it was pretty nice. It is hard to get your head around some concepts, because the whole SDK is kind of baroque, just like OOo itself, but from my limited experience, it is very powerful.
I built a bridge for the Lua scripting language on top of the Java UNO bridge and used it to script 2D animations for a movie that I had to create for my research. I used OOo Draw to specify the animated elements, and traced out their paths via other elements and object prperties.
The scripts inspected the objects and their properties, animated them accordingly in an OOo Draw canvas, and saved the frames to the disk. All in all, it took me about a week to get this to work; time that I consider well-invested.
Maybe someone will cut out all the source code for open office except for the word processor,
and complie THAT puppy. Then do the same for the spreadsheet... bam, smaller programs that load in a reasonable amount of time.
I see from the site that 1.1 Beta is comming along and wondering if 1.1 was going to be basicly the same API or total different API.
OpenOffice is enormous. The code is mindboggling. It has its own portable runtime, its own object model, its own widget toolkit. It's like Mozilla.
You can't "port" it to KDE, any more than you could port it to GTK/GNOME. What Ximian have been doing lately is simply touching up the edges, making it use the same font/colors as GTK, use GNOME artwork etc, but it's not a "port".
[soapbox]The original KDE vision of producing an integrated desktop through making kickass APIs that everybody would use was a cute one, but ultimately short sighted - your average Linux desktop is a mishmash of different platforms and toolkits, KDE, GNOME, OpenOffice, Mozilla, Wine - there's no way all this sofware can be ported to KDE, so the only solution is to eliminate the idea of KDE/GNOME as a platform and become based entirely on standards, with KDE merely providing an implementation via C++ APIs.[/soapbox].
Check 3.4 in Automation Brdige in the developers guide with the kit and then look at Service Manager Component. Com/Dcom is supported by UNO. aka Unified Network Object model in which c++, java, jscript, and basic all use.
The section on com/dcom is quite large and I am very impressed. I am simply amazed at how complex this product is. No wonder people complain its bloated good lord. Each section according to printer preview in IE is about 200 pages each! Its close to 2k pages in total.
http://saveie6.com/