Difference between revisions of "Documentation/Bounties/SmartTag Chapter"

From Apache OpenOffice Wiki
Jump to: navigation, search
(add initial draft)
 
 
Line 5: Line 5:
 
The OpenOffice.org Developer's Guide is designed to be the main resource for developers to find technical background information related to UNO and the OpenOffice.org API.  
 
The OpenOffice.org Developer's Guide is designed to be the main resource for developers to find technical background information related to UNO and the OpenOffice.org API.  
  
The Developer's Guide chapter "[[Documentation/DevGuide/WritingUNO/Writing_UNO_Components|Writing UNO Components]]" provides a collection of information that is necessary or important to write well formed UNO components. Besides basic component knowledge the chapter contains several sub chapters describing specific service provider interfaces (SPI). Smart Tags are a well known concept (SPI) introduced with MS Office XP to add contextual information to Office documents. The SPI Smart Tags was introduces for OpenOffice org 2.2 but the relating documentation in the Dveloper's Guide is still missing.
+
The Developer's Guide chapter on [[Documentation/DevGuide/WritingUNO/Writing_UNO_Components|Writing UNO Components]] provides a collection of information that is necessary or important to write well-formed UNO components. Besides basic component knowledge the chapter contains several sub-chapters describing specific service provider interfaces (SPI). Smart Tags are a well known concept introduced with MS Office XP to add contextual information to Office documents. The SPI Smart Tags was introduces for OpenOffice org 2.2 but the relating documentation in the Dveloper's Guide is still missing.
 +
 
 
== Task ==
 
== Task ==
  
The task of this bounty is to create a new chapter "[[Documentation/DevGuide/WritingUNO/SmartTags/Smart_Tags|Smart Tags]]" and integrate, convert or transform the existing material from "[[Smart_Tags|Writer/Smart Tags]]" into this new chapter and apply the styles and formatting of the Developer's Guide. The final structure will be defined together with the bounty reviewers/mentors.  
+
The task of this bounty is to create a new chapter on [[Documentation/DevGuide/WritingUNO/SmartTags/Smart_Tags|Smart Tags]].  The bounty Owner should integrate or transform the existing material from [[Smart_Tags|Writer/Smart Tags]] into this new chapter, and apply the styles and formatting of the Developer's Guide. The final structure will be defined together with the bounty reviewers/mentors.  
  
 
== Knowledge requirements  ==
 
== Knowledge requirements  ==
  
The Owner of this bounty should have a deep knowledge of Smart Tags and the available features and UNO in general. Ideally the owner has practical experience with the development of Smart Tags.
+
The Owner of this bounty should have a deep knowledge of Smart Tags and the available features and UNO in general. Ideally the Owner has practical experience with the development of Smart Tags.
  
 
{{PDL1}}
 
{{PDL1}}
 
[[Category:Documentation/Bounties]]
 
[[Category:Documentation/Bounties]]

Latest revision as of 19:04, 1 June 2010


Summary

The OpenOffice.org Developer's Guide is designed to be the main resource for developers to find technical background information related to UNO and the OpenOffice.org API.

The Developer's Guide chapter on Writing UNO Components provides a collection of information that is necessary or important to write well-formed UNO components. Besides basic component knowledge the chapter contains several sub-chapters describing specific service provider interfaces (SPI). Smart Tags are a well known concept introduced with MS Office XP to add contextual information to Office documents. The SPI Smart Tags was introduces for OpenOffice org 2.2 but the relating documentation in the Dveloper's Guide is still missing.

Task

The task of this bounty is to create a new chapter on Smart Tags. The bounty Owner should integrate or transform the existing material from Writer/Smart Tags into this new chapter, and apply the styles and formatting of the Developer's Guide. The final structure will be defined together with the bounty reviewers/mentors.

Knowledge requirements

The Owner of this bounty should have a deep knowledge of Smart Tags and the available features and UNO in general. Ideally the Owner has practical experience with the development of Smart Tags.

Content on this page is licensed under the Public Documentation License (PDL).
Personal tools