Difference between revisions of "Writing Professional Components"

From Apache OpenOffice Wiki
Jump to: navigation, search
m (Created page with '{{Documentation/Caution|This chapter is under construction for a while because I don't master all the topics evocated here at the moment. ~~~~}} Writing components is not as easy…')
 
m (My own Inspector)
Line 3: Line 3:
 
=Java Inspector=
 
=Java Inspector=
 
=My own Inspector=
 
=My own Inspector=
 +
 +
I have already presented in this document [[Constructing_Helpers#Reflection_Helper|my own inspector]] but it wasn't a component. Then it was only valuable when writing binary executable, not component. In this section I will show how to transform it as a component. Because [[Object Inspector|Java Inspector]] is more advanced my component is only interesting when using old an inefficient computers. But for me it represents the only experience with writing a great component.
 +
{{Documentation|Caution|The code presented here is not safe. You can see many "FIXME" in the code. At the moment the version is labelled 0.4}}
 +
 +
This component is composed with two separate class (at the moment)
 +
 +
==The ReflectionHelper class==
 +
==The Component==
 +
 
=Transforming a component=
 
=Transforming a component=

Revision as of 12:34, 3 August 2009

Documentation caution.png This chapter is under construction for a while because I don't master all the topics evocated here at the moment. SergeMoutou 12:20, 3 August 2009 (UTC)

Writing components is not as easy as developping binary executable. When an exception occurs in your component a recovery process of your document begins. This process is too long to try some code and correct the errors. When designing a component, it would be a good idea to conceive it as a binary executable before to change it into a component. In this chapter we will discuss this idea and also the exceptions. But before starting we examine at first the inspection tools.

Java Inspector

My own Inspector

I have already presented in this document my own inspector but it wasn't a component. Then it was only valuable when writing binary executable, not component. In this section I will show how to transform it as a component. Because Java Inspector is more advanced my component is only interesting when using old an inefficient computers. But for me it represents the only experience with writing a great component. Template:Documentation

This component is composed with two separate class (at the moment)

The ReflectionHelper class

The Component

Transforming a component

Personal tools