Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2010/ch7 7b JB

2010-12-11T04:40:44Z

Jsberry:

=Information Expert Pattern=

==Introduction==

Information Expert Pattern is a principle for assigning responsibility in object-oriented design. The fundamental idea is to identify the class with the most information (expertise) and assign responsibility to it.

==GRASP==

In object-oriented design, the overall problems of assigning responsibility are dealt with by [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29 GRASP 1], or General Responsibility Assignment Software Patterns (or Principles). GRASP has nine principles:
# Information Expert
# Creator
# Low Coupling
# High Cohesion
# Controller
# Polymorphysm
# Pure Fabrication
# Indirection
# Protected Variations

There are often situations in programming object-oriented designs when data needed by an object is spread out across several other objects. Rather than access each object individually and sequentially to get the details one at a time, the Information Expert pattern can be used to keep the program organized and straightforward. This will help to enable later extension of the program to enable new functionality without adding a lot of complexity.

==Process==
Using this approach, the programmer would:
# Identify a responsibility
# Determine what information is needed to fulfill it,
# Locate where that information is stored
# Identify which class contains the largest subset of the required data
# Assign responsibility to that class to gather the remaining data

In some circumstances, this method could be used in a tree structure to have a small number of experts who are responsible for specific types of data. Each contacts a subset of the group of objects containing the needed data and may do some simple processing or combination of the data before passing it back to the original caller.

An example of when this might be retrieval of a database record. The record may be comprised of data from many different databases. One object would be the assigned as the caller. It would be responsible for fetching the necessary data and building the final record. It would contact each database controller, which may each be asked to retrieve records from one or more tables. They would return the requested records (possibly after some minor editing of them). The caller would then extract the fields it needed and build the new record from them. This new record would be returned.

==References==
# [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29 Wikipedia's GRASP article 1]
# [http://cs.armstrong.edu/hsu/Course/CSCI3321/PracticalSoftwareEngineering/html/ch10s04.html Information Expert Pattern overview with diagrams 2]
# [http://programmersnotes.info/2009/03/28/creator-and-information-expert-grasp-design-pattern-series/#expert Creator and Information Expert Principles with sample code 3]

CSC/ECE 517 Fall 2010/ch7 7b JB

2010-12-11T04:31:56Z

Jsberry:

=Information Expert Pattern=

==Introduction==

Information Expert Pattern is a principle for assigning responsibility in object-oriented design. The fundamental idea is to identify the class with the most information (expertise) and assign responsibility to it.

==GRASP==

In object-oriented design, the overall problems of assigning responsibility are dealt with by [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29 GRASP 1], or General Responsibility Assignment Software Patterns (or Principles). GRASP has nine principles:
# Information Expert
# Creator
# Low Coupling
# High Cohesion
# Controller
# Polymorphysm
# Pure Fabrication
# Indirection
# Protected Variations

There are often situations in programming object-oriented designs when data needed by an object is spread out across several other objects. Rather than access each object individually and sequentially to get the details one at a time, the Information Expert pattern can be used to keep the program organized and straightforward. This will help to enable later extension of the program to enable new functionality without adding a lot of complexity.

==Process==
Using this approach, the programmer would:
# Identify a responsibility
# Determine what information is needed to fulfill it,
# Locate where that information is stored
# Identify which class contains the largest subset of the required data
# Assign responsibility to that class to gather the remaining data

In some circumstances, this method could be used in a tree structure to have a small number of experts who are responsible for specific types of data. Each contacts a subset of the group of objects containing the needed data and may do some simple processing or combination of the data before passing it back to the original caller.

==References==
# [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29 Wikipedia's GRASP article 1]
# [http://cs.armstrong.edu/hsu/Course/CSCI3321/PracticalSoftwareEngineering/html/ch10s04.html Information Expert Pattern overview with diagrams 2]
# [http://programmersnotes.info/2009/03/28/creator-and-information-expert-grasp-design-pattern-series/#expert Creator and Information Expert Principles with sample code 3]

CSC/ECE 517 Fall 2010/ch7 7b JB

2010-12-11T04:29:05Z

Jsberry:

=Information Expert Pattern=

==Introduction==

Information Expert Pattern is a principle for assigning responsibility in object-oriented design. The fundamental idea is to identify the class with the most information (expertise) and assign responsibility to it.

==GRASP==

In object-oriented design, the overall problems of assigning responsibility are dealt with by [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29 GRASP 1], or General Responsibility Assignment Software Patterns (or Principles). GRASP has nine principles:
# Information Expert
# Creator
# Low Coupling
# High Cohesion
# Controller
# Polymorphysm
# Pure Fabrication
# Indirection
# Protected Variations

There are often situations in programming object-oriented designs when data needed by an object is spread out across several other objects. Rather than access each object individually and sequentially to get the details one at a time, the Information Expert pattern can be used to keep the program organized and straightforward. This will help to enable later extension of the program to enable new functionality without adding a lot of complexity.

==Process==
Using this approach, the programmer would:
# Identify a responsibility
# Determine what information is needed to fulfill it,
# Locate where that information is stored
# Identify which class contains the largest subset of the required data
# Assign responsibility to that class
# Assign the responsible class to recursively apply the Information Expert Pattern for acquiring any data still missing.

==References==
# [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29 Wikipedia's GRASP article 1]
# [http://cs.armstrong.edu/hsu/Course/CSCI3321/PracticalSoftwareEngineering/html/ch10s04.html Information Expert Pattern overview with diagrams 2]
# [http://programmersnotes.info/2009/03/28/creator-and-information-expert-grasp-design-pattern-series/#expert Creator and Information Expert Principles with sample code 3]

CSC/ECE 517 Fall 2010/ch7 7b JB

2010-12-11T04:15:12Z

Jsberry:

=Information Expert Pattern=

==Introduction==

Information Expert Pattern is a principle for assigning responsibility in object-oriented design. The fundamental idea is to identify the class with the most information (expertise) and assign responsibility to it.

==GRASP==

In object-oriented design, the overall problems of assigning responsibility are dealt with by GRASP[http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29 1], or General Responsibility Assignment Software Patterns (or Principles). GRASP has nine principles, of which Information Expert is one. The others are:
#Creator [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29#Creator 2]
#Low Coupling [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29#Low_Coupling 3]
#High Cohesion [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29#High_Cohesion 4]
#Controller [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29#Controller 5]
#Polymorphysm [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29#Polymorphism 6]
#Pure Fabrication [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29#Pure_Fabrication 7]
#Indirection [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29#Indirection 8]
#Protected Variations [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29#Protected_Variations 9]

==Process==
Using this approach, the programmer would:
# Identify a responsibility
# Determine what information is needed to fulfill it,
# Locate where that information is stored
# Identify which class contains the largest subset of the required data
# Assign responsibility to that class
# Assign the responsible class to recursively apply the Information Expert Pattern for acquiring any data still missing.

==References==
# [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29 Wikipedia's GRASP article 10]
# [http://cs.armstrong.edu/hsu/Course/CSCI3321/PracticalSoftwareEngineering/html/ch10s04.html Information Expert Pattern overview with diagrams 11]
# [http://programmersnotes.info/2009/03/28/creator-and-information-expert-grasp-design-pattern-series/#expert Creator and Information Expert Principles with sample code 12]

CSC/ECE 517 Fall 2010/ch1 S10 ms

2010-12-02T06:33:36Z

Jsberry:

*[[CSC/ECE 517 Fall 2010/ch1 1a vc]]

*[[CSC/ECE 517 Fall 2010/ch1 1a br]]

*[[CSC/ECE 517 Fall 2010/ch1 1b mg]]

*[[CSC/ECE 517 Fall 2010/ch1 1c JF]]

*[[CSC/ECE 517 Fall 2010/ch1 1e az]]

*[[CSC/ECE 517 Fall 2010/ch1 1e bb]]

*[[CSC/ECE 517 Fall 2010/ch1 1f vn]]

*[[CSC/ECE 517 Fall 2010/ch1 25 ag]]

*[[CSC/ECE 517 Fall 2010/ch2 2b dg]]

*[[CSC/ECE 517 Fall 2010/ch1 2e RI]]

*[[CSC/ECE 517 Fall 2010/ch1 S6 aa]]

*[[CSC/ECE 517 Fall 2010/ch1 S6 km]]

*[[CSC/ECE 517 Fall 2010/ch1 S10 GP]]

*[[CSC/ECE 517 Fall 2010/ch1 S10 MS]]

*[[CSC/ECE 517 Fall 2010/ch1 S10 MM]]

*[[CSC/ECE 517 Fall 2010/ch1 S10 PH]]

*[[CSC/ECE 517 Fall 2010/ch2 2a CB]]

*[[CSC/ECE 517 Fall 2010/ch2 2a mw]]

*[[CSC/ECE 517 Fall 2010/ch2 2c ck]]

*[[CSC/ECE 517 Fall 2010/ch2 S23 GP]]

*[[CSC/ECE 517 Fall 2010/ch2 S24 NS]]

*[[CSC/ECE 517 Fall 2010/ch2 S23 SS]]

*[[CSC/ECE 517 Fall 2010/ch2 S23 NR]]

*[[CSC/ECE 517 Fall 2010/ch2 S20 TT]]

*[[CSC/ECE 517 Fall 2010/ch2 2d AS]]

*[[CSC/ECE 517 Fall 2010/ch2 S24 rm]]

*[[CSC/ECE 517 Fall 2010/ch3 3a SN]]

*[[CSC/ECE 517 Fall 2010/ch3 3b ka]]

*[[CSC/ECE 517 Fall 2010/ch3 3e br]]

*[[CSC/ECE 517 Fall 2010/ch3 3f lj]]

*[[CSC/ECE 517 Fall 2010/ch3 3h az]]

*[[CSC/ECE 517 Fall 2010/ch3 3h PW]]

*[[CSC/ECE 517 Fall 2010/ch3 3i IC]]

*[[CSC/ECE 517 Fall 2010/ch3 3i MM]]

*[[CSC/ECE 517 Fall 2010/ch3 3j KS]]

*[[CSC/ECE 517 Fall 2010/ch3 S30 SK]]

*[[CSC/ECE 517 Fall 2010/ch3 4b mt]]

*[[CSC/ECE 517 Fall 2010/ch4 4e ms]]

*[[CSC/ECE 517 Fall 2010/ch4 4f sv]]

*[[CSC/ECE 517 Fall 2010/ch4 4g HW]]

*[[CSC/ECE 517 Fall 2010/ch4 4g km]]

*[[CSC/ECE 517 Fall 2010/ch4 4h am]]

*[[CSC/ECE 517 Fall 2010/ch5 5b mt]]

*[[CSC/ECE 517 Fall 2010/ch5 5b jz]]

*[[CSC/ECE 517 Fall 2010/ch5 5c ck]]

*[[CSC/ECE 517 Fall 2010/ch5 5c IC]]

*[[CSC/ECE 517 Fall 2010/ch5 5f SN]]

*[[CSC/ECE 517 Fall 2010/ch5 5a KR]]

*[[CSC/ECE 517 Fall 2010/ch5 5b RR]]

*[[CSC/ECE 517 Fall 2010/ch5 5e ms]]

*[[CSC/ECE 517 Fall 2010/chd 6d isb]]

*[[CSC/ECE 517 Fall 2010/ch6 6b SK]]

*[[CSC/ECE 517 Fall 2010/ch6 6c AW]]

*[[CSC/ECE 517 Fall 2010/ch6 6d bb]]

*[[CSC/ECE 517 Fall 2010/ch6 6h AS]]

*[[CSC/ECE 517 Fall 2010/ch6 6f AZ]]

*[[CSC/ECE 517 Fall 2010/ch6 6b AK]]

*[[CSC/ECE 517 Fall 2010/ch6 6g ss]]

*[[CSC/ECE 517 Fall 2010/ch6 6d NM]]

*[[ CSC/ECE 517 Fall 2010/ch6 6a PC]]

*[[ CSC/ECE 517 Fall 2010/ch2 4d RB]]

*[[ CSC/ECE 517 Fall 2010/ch7 71 ed]]

*[[ CSC/ECE 517 Fall 2010/ch7 7c ed]]

*[[ CSC/ECE 517 Fall 2010/ch7 7e GP]]

*[[ CSC/ECE 517 Fall 2010/ch7 7e GS]]

*[[ CSC/ECE 517 Fall 2010/ch7 7f PW]]

*[[ CSC/ECE 517 Fall 2010/ch7 7g ms]]

*[[ CSC/ECE 517 Fall 2010/ch7 7i sr]]

*[[ CSC/ECE_517_Fall_2010/ch7 7b JB]]

*[[ CSC/ECE_517_Fall_2010/ch7 S36 JB]]

CSC/ECE 517 Fall 2010/ch7 S36 JB

2010-12-02T06:27:40Z

Jsberry:

=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.

==The Office Suites==
There are many different office suites. Below we review a few of the more popular ones that can be easily found today.
===OpenOffice===
[http://www.openoffice.org OpenOffice] is a free office suite provided as [http://en.wikipedia.org/wiki/Open_source_software Open-source Software] (OSS) by [http://www.oracle.com Oracle] (previously by [http://www.sun.com Sun Microsystems] and before that by Star Division as Star Office). It is available for many different operating systems on many different platforms.
====API====
Through the [http://wiki.services.openoffice.org/wiki/Documentation/BASIC_Guide/API_Intro OpenOffice API], a user can manipulate files created by OpenOffice using the language of their choice. OpenOffice uses the [http://udk.openoffice.org/common/man/uno.html Universal Network Objects] (UNO) interface to provide this functionality.
====Language Support====
In addition to supporting several non-OO languages, OpenOffice supports the following OO languages:
* Perl
* Java
* C++
* Python
* Others
===Google Docs===
[http://www.google.com Google Docs] 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.
====API====
According to the [http://code.google.com/apis/documents/docs/developers_guide.html Google Docs Developer's Guide], "The Google Documents List Data API allows client applications to request a list of a user's documents, query the content of a user's documents, upload/download documents, modify the sharing permissions, view the revision history, and file documents within folders."
====Language Support====
* Java
* .Net
* PHP
* Python
===Microsoft Word===
[http://www.microsoft.com Microsoft] 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.
====API====
The [http://msdn.microsoft.com/en-us/library/aa165081%28office.10%29.aspx Microsoft Office] API provides support for accessing its documents through external scripts and programs.
====Language Support====
* VBA
* .Net?
==Conclusion==
Not all APIs are created equal! Some office suites have been built around their APIs, while others put them in as afterthoughts. A well-defined API can be used by a large number of different programming languages, allows many different file formats to be modified, and provides many ways to manipulate those files.
==References==
# [http://www.openoffice.org OpenOffice.org API]
# [http://www.google.com Google Docs]
# [http://www.microsoft.com Microsoft Word]

CSC/ECE 517 Fall 2010/ch7 S36 JB

2010-12-02T06:19:47Z

Jsberry:

=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.

==The Office Suites==
There are many different office suites. Below we review a few of the more popular ones that can be easily found today.
===OpenOffice===
[http://www.openoffice.org OpenOffice] is a free office suite provided as [http://en.wikipedia.org/wiki/Open_source_software Open-source Software] (OSS) by [http://www.oracle.com Oracle] (previously by [http://www.sun.com Sun Microsystems] and before that by Star Division as Star Office). It is available for many different operating systems on many different platforms.
====API====
Through the [http://wiki.services.openoffice.org/wiki/Documentation/BASIC_Guide/API_Intro OpenOffice API], a user can manipulate files created by OpenOffice using the language of their choice. OpenOffice uses the [http://udk.openoffice.org/common/man/uno.html Universal Network Objects] (UNO) interface to provide this functionality.
====Language Support====
===Google Docs===
[http://www.google.com Google Docs] 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.
====API====
According to the [http://code.google.com/apis/documents/docs/developers_guide.html Google Docs Developer's Guide], "The Google Documents List Data API allows client applications to request a list of a user's documents, query the content of a user's documents, upload/download documents, modify the sharing permissions, view the revision history, and file documents within folders."
====Language Support====
===Microsoft Word===
[http://www.microsoft.com Microsoft] 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.
====API====
The [http://msdn.microsoft.com/en-us/library/aa165081%28office.10%29.aspx Microsoft Office] API provides support for accessing its documents through external scripts and programs.
====Language Support====
==Conclusion==
Not all APIs are created equal! Some office suites have been built around their APIs, while others put them in as afterthoughts. A well-defined API can be used by a large number of different programming languages, allows many different file formats to be modified, and provides many ways to manipulate those files.
==References==
# [http://www.openoffice.org OpenOffice.org API]
# [http://www.google.com Google Docs]
# [http://www.microsoft.com Microsoft Word]

CSC/ECE 517 Fall 2010/ch7 7b JB

2010-12-02T06:16:30Z

Jsberry:

=Information Expert Pattern=

==Introduction==

Information Expert Pattern is a principle for assigning responsibility in object-oriented design. The fundamental idea is to identify the class with the most information (expertise) and assign responsibility to it.

==GRASP==

In object-oriented design, the overall problems of assigning responsibility are dealt with by GRASP[http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29], or General Responsibility Assignment Software Patterns (or Principles). GRASP has nine principles, of which Information Expert is one. The others are:
#Creator [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29#Creator]
#Low Coupling [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29#Low_Coupling]
#High Cohesion [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29#High_Cohesion]
#Controller [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29#Controller]
#Polymorphysm [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29#Polymorphism]
#Pure Fabrication [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29#Pure_Fabrication]
#Indirection [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29#Indirection]
#Protected Variations [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29#Protected_Variations]

==Process==

Using this approach, the programmer would:
# Identify a responsibility
# Determine what information is needed to fulfill it,
# Locate where that information is stored
# Identify which class contains the largest subset of the required data
# Assign responsibility to that class
# Assign the responsible class to recursively apply the Information Expert Pattern for acquiring any data still missing.

==References==
# [http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29 Wikipedia's GRASP article]
# [http://cs.armstrong.edu/hsu/Course/CSCI3321/PracticalSoftwareEngineering/html/ch10s04.html Information Expert Pattern overview with diagrams]
# [http://programmersnotes.info/2009/03/28/creator-and-information-expert-grasp-design-pattern-series/#expert Creator and Information Expert Principles with sample code]

CSC/ECE 517 Fall 2010/ch7 S36 JB

2010-12-02T06:03:25Z

Jsberry:

=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.

==The Office Suites==
There are many different office suites. Below we review a few of the more popular ones that can be easily found today.
===OpenOffice===
[http://www.openoffice.org OpenOffice] is a free office suite provided as [http://en.wikipedia.org/wiki/Open_source_software Open-source Software] (OSS) by [http://www.oracle.com Oracle] (previously by [http://www.sun.com Sun Microsystems] and before that by Star Division as Star Office). It is available for many different operating systems on many different platforms.
====API====
Through the [http://wiki.services.openoffice.org/wiki/Documentation/BASIC_Guide/API_Intro OpenOffice API], a user can manipulate files created by OpenOffice using the language of their choice. OpenOffice uses the [http://udk.openoffice.org/common/man/uno.html Universal Network Objects] (UNO) interface to provide this functionality.
====Language Support====
===Google Docs===
[http://www.google.com Google Docs] 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.
====API====
According to the [http://code.google.com/apis/documents/docs/developers_guide.html Google Docs Developer's Guide], "The Google Documents List Data API allows client applications to request a list of a user's documents, query the content of a user's documents, upload/download documents, modify the sharing permissions, view the revision history, and file documents within folders."
====Language Support====
===Microsoft Word===
[http://www.microsoft.com Microsoft] 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.
====API====
The [http://msdn.microsoft.com/en-us/library/aa165081%28office.10%29.aspx Microsoft Office] API provides support for accessing its documents through external scripts and programs.
====Language Support====
==Conclusion==
==References==
# [http://www.openoffice.org OpenOffice.org API]
# [http://www.google.com Google Docs]
# [http://www.microsoft.com Microsoft Word]

CSC/ECE 517 Fall 2010/ch7 S36 JB

2010-12-02T05:41:29Z

Jsberry: /* API */

=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.

==The Office Suites==
There are many different office suites. Below we review a few of the more popular ones that can be easily found today.
===OpenOffice===
[http://www.openoffice.org OpenOffice] is a free office suite provided as [http://en.wikipedia.org/wiki/Open_source_software Open-source Software] (OSS) by [http://www.oracle.com Oracle] (previously by [http://www.sun.com Sun Microsystems] and before that by Star Division as Star Office). It is available for many different operating systems on many different platforms.
====API====
Through the [http://wiki.services.openoffice.org/wiki/Documentation/BASIC_Guide/API_Intro OpenOffice API], a user has access to manipulate files created by OpenOffice using the language of their choice. OpenOffice uses the [http://udk.openoffice.org/common/man/uno.html Universal Network Objects] (UNO) interface for this.

====Language Support====
===Google Docs===
[http://www.google.com Google Docs] 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.
====API====
The API for Google Docs, like for OpenOffice, is well thought out and supported. It allows for external modification and control of the suite software by programs written in various languages.
====Language Support====
===Microsoft Word===
[http://www.microsoft.com Microsoft] 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.
====API====
Microsoft's API stinks!
====Language Support====
==Conclusion==
==References==
# [http://www.openoffice.org OpenOffice.org API]
# [http://www.google.com Google Docs]
# [http://www.microsoft.com Microsoft Word]

CSC/ECE 517 Fall 2010/ch7 S36 JB

2010-12-02T05:41:01Z

Jsberry:

=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.

==The Office Suites==
There are many different office suites. Below we review a few of the more popular ones that can be easily found today.
===OpenOffice===
[http://www.openoffice.org OpenOffice] is a free office suite provided as [http://en.wikipedia.org/wiki/Open_source_software Open-source Software] (OSS) by [http://www.oracle.com Oracle] (previously by [http://www.sun.com Sun Microsystems] and before that by Star Division as Star Office). It is available for many different operating systems on many different platforms.
====API====
Through the [http://wiki.services.openoffice.org/wiki/Documentation/BASIC_Guide/API_Intro OpenOffice API], a user has access to manipulate files created by OpenOffice using the language of their choice. OpenOffice uses the [http://udk.openoffice.org/common/man/uno.html Universal Network Objects] (UNO) interface for this.
====Language Support====
===Google Docs===
[http://www.google.com Google Docs] 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.
====API====
The API for Google Docs, like for OpenOffice, is well thought out and supported. It allows for external modification and control of the suite software by programs written in various languages.
====Language Support====
===Microsoft Word===
[http://www.microsoft.com Microsoft] 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.
====API====
Microsoft's API stinks!
====Language Support====
==Conclusion==
==References==
# [http://www.openoffice.org OpenOffice.org API]
# [http://www.google.com Google Docs]
# [http://www.microsoft.com Microsoft Word]

CSC/ECE 517 Fall 2010/ch7 S36 JB

2010-12-02T05:25:34Z

Jsberry:

=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.

==The Office Suites==
There are many different office suites. Below we review a few of the more popular ones that can be easily found today.
===OpenOffice===
[http://www.openoffice.org OpenOffice 1] is a free office suite provided as [http://en.wikipedia.org/wiki/Open_source_software Open-source Software] (OSS) by [http://www.oracle.com Oracle] (previously by [http://www.sun.com Sun Microsystems] and before that by Star Division as Star Office). It is available for many different operating systems on many different platforms.
====API====
The API for OpenOffice allows for external programs in various programming languages to provide support for functions not available in the suite. This API is well defined and supported by the OpenOffice.org project.
===Google Docs===
[http://www.google.com 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.
====API====
The API for Google Docs, like for OpenOffice, is well thought out and supported. It allows for external modification and control of the suite software by programs written in various languages.
===Microsoft Word===
[http://www.microsoft.com 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.
====API====
Microsoft's API stinks!
==Conclusion==
==References==
# [http://www.openoffice.org OpenOffice.org API]
# [http://www.google.com Google Docs]
# [http://www.microsoft.com Microsoft Word]

CSC/ECE 517 Fall 2010/ch7 7b JB

2010-12-02T04:55:52Z

Jsberry:

=Information Expert Pattern=

CSC/ECE 517 Fall 2010/ch7 S36 JB

2010-12-02T04:53:33Z

Jsberry:

CSC/ECE 517 Fall 2010/ch7 S36 JB

2010-12-02T04:10:44Z

Jsberry:

=O-O packages for implementing office suite APIs=
==Introduction==
==Office Suites==
===OpenOffice===
[http://www.openoffice.org OpenOffice 1] is a free office suite based on Star Office.
===Google Docs===
[http://www.google.com 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===
[http://www.microsoft.com 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.
==Conclusion==
==References==
# [http://www.openoffice.org OpenOffice.org API]
# [http://www.google.com Google Docs]
# [http://www.microsoft.com Microsoft Word]