CSC/ECE 517 Fall 2010/ch7 S36 JB: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
=O-O packages for implementing office suite APIs= | =O-O packages for implementing office suite APIs= | ||
==Introduction== | ==Introduction== | ||
Office suite software has been around now for many years. The first was Microsoft Office, released in 1989, which included a word processor, a spreadsheet, and a presentation program. These were separate programs which were integrated together into a single package. For many years, Microsoft has remained the dominant player in the game, but not the only one. Others have come (and sometimes gone) that have had their own popularity. Although all of them have tried to provide every function they thought their users might need and/or want, none of them are perfect. | |||
Many users have identified shortcomings or wished for special features that are not available in their favorite office suites. Some of the suite providers have recognized this and now offer Application Interfaces (APIs) that allow people to access core functions of their software from outside of the program, using separate scripts or programs. This chapter is a review of the APIs available in various suites and some of the packages that are available to different Object Oriented (OO) languages for implementing this API. | |||
==Office Suites== | ==Office Suites== | ||
===OpenOffice=== | ===OpenOffice=== |
Revision as of 04:53, 2 December 2010
O-O packages for implementing office suite APIs
Introduction
Office suite software has been around now for many years. The first was Microsoft Office, released in 1989, which included a word processor, a spreadsheet, and a presentation program. These were separate programs which were integrated together into a single package. For many years, Microsoft has remained the dominant player in the game, but not the only one. Others have come (and sometimes gone) that have had their own popularity. Although all of them have tried to provide every function they thought their users might need and/or want, none of them are perfect. Many users have identified shortcomings or wished for special features that are not available in their favorite office suites. Some of the suite providers have recognized this and now offer Application Interfaces (APIs) that allow people to access core functions of their software from outside of the program, using separate scripts or programs. This chapter is a review of the APIs available in various suites and some of the packages that are available to different Object Oriented (OO) languages for implementing this API.
Office Suites
OpenOffice
OpenOffice 1 is a free office suite based on Star Office.
Google Docs
Google Docs 2 is also a free office suite. It follows the recent trend of transferring more executables online, making them easily available from anywhere with an Internet connection.
Microsoft Word
Microsoft 3 has long had a reputation for being closed and anti-competitive and entered the API game very late. It is now trying to catch up with the big boys.