Apache OpenOffice Wiki - User contributions [en]

Penny1

2007-01-17T11:24:18Z

Jiangc: Penny1 moved to UNO registery and Bootstrapping: revert

#REDIRECT [[UNO registery and Bootstrapping]]

UNO registery and Bootstrapping

2007-01-17T11:24:18Z

Jiangc: Penny1 moved to UNO registery and Bootstrapping: revert

OpenOffice.org can be extended : you can add features in OooBasic, in C++, in Java, in Python ... These added features are called Add-Ons, components, Add-ins (discussed in chapter 13.1) and we can wonder how Openoffice.org knows something about the corresponding code ? The tools involved in this chapter are regview, regcomp, regmerge and idlc.
== Why UNO registry ? ==
It is common for programmer to develop a program and link it with a static library. If the library is a dynamic one the linking problem is let to Operating System : this OS have to know if the library is already loaded and if not where it lies. Let us be more concrete with an example.

[[Image:LibraryExample.png]]

In the example above in Figure above our program example.cxx calls something in mylib.so or mylib.dll (the arrow means an interaction). This is done in a very simple way if both are compiled with same language : under Linux we use a -Lmylib.so when compiling example.cxx (more [[Constructing_Components#A_very_simple_Counter|here]]). Then when you launch example binary executable when it needs what is in mylib.so it asks OS to load it. The case is a little more complicated if mylib.so is compiled with an other language than C++ : you have to learn how to pass parameters in C++ to reach the content of mylib.so. This is feasible changing a little example.cxx code.
But what happens if you have a binary executable program and you want to give him new features with a dynamic library ? This can be done with OpenOffice.org as already mentioned.

What kind of problems OpenOffice has then to carry out ?
First of all, it is impossible for Openoffice.org to know in advance what is the name of the library (it's a name you choose). Then OpenOffice.org must provide a mechanism to know its name : this is one of the goals of registry.
Is the name of the dynamic library enough ? No, if you imagine you can extend with two or more libraries : it is important to know that foo1 procedure/method comes from foo_lib1 library and foo2 from foo_lib2... In OpenOffice.org this is generalized saying such an interface comes from such a library ... There is a lot of other problems to resolve before making it working properly. For example a problem with the name of procedure/methods : if you write it in C or in C++ the exported names will differ.
And the parameters, how do you pass them ? Imagine OOoCalc call something in mylib.so : it is unimaginable to ask OOocalc users to write something describing how parameters are passed in their OOoCalc formula ! OpenOffice has to know how pass a parameter in your library. This is done with what is called implementation environment. This done with specifying that every dynamic library has to export :

<code>[cpp]
//Listing 1 How to get the Implementation Environnement in a dynamic library
// C++
extern "C"
void SAL_CALL component_getImplementationEnvironment(
const sal_Char ** ppEnvTypeName,
uno_Environment ** ppEnv )
</code>
The passing parameters way is fixed by extern C. This is not a decoration but an obligation. If not present a ["component_getImplementationEnvironment" could not be found] error will be thrown when you try to registry (with regmerge for instance).

Registery uses rdb files in a binary file format. Binaries format are difficult to read by human and then a tool is provided to give the information in human readable form (see regview in further [[UNO_registery_and_Bootstrapping#The_Bootstrap |section]]).

An advise : at first you can skip the rest of this chapter particularly if you are not interested in [[Constructing_Components|components]]. But not only components use registry : the [[UNO_automation_with_a_binary_%28executable%29|UNO/automation]] uses registry in a different way.

= How to use UNO registeries =
Documentation for registries already exist at : [http://udk.openoffice.org/common/man/tutorial/uno_registries.html uno registeries]. More information at : [http://www.ooomacros.org/dev.php ooomacros] where these tools are available :
* Add On Tool
Author: Bernard Marcelly
* Add On Installer
Author: Didier Lachièze, with code from Danny Brewer, Bernard Marcelly and Andrew Brown
* Basic Library Installer
Author: Danny Brewer, with code from Andrew Brown & Didier Lachièze

In my opinion, the simpler way to registery is to modify the file unorc (under linux) or uno.ini (under Windows). You have to put the file your_library.uno.rdb in <OOo>/program directory, and editing/modifying the file <OOo>/program/unorc (under linux) adding (last line your_library.uno.rdb) :

<pre>
#unorc or uno.ini
[Bootstrap]
UNO_SHARED_PACKAGES=${$SYSBINDIR/bootstraprc:BaseInstallation}/share/uno_packages
UNO_SHARED_PACKAGES_CACHE=$UNO_SHARED_PACKAGES/cache
UNO_USER_PACKAGES=${$SYSBINDIR/bootstraprc:UserInstallation}/user/uno_packages
UNO_USER_PACKAGES_CACHE=$UNO_USER_PACKAGES/cache
UNO_TYPES=$SYSBINDIR/types.rdb ?$UNO_SHARED_PACKAGES_CACHE/types.rdb ?$UNO_USER_PACKAGES_CACHE/types.rdb
UNO_SERVICES= ?$UNO_USER_PACKAGES_CACHE/services.rdb ?$UNO_SHARED_PACKAGES_CACHE/services.rdb $SYSBINDIR/services.rdb ?$SYSBINDIR/your_library.uno.rdb
</pre>

Don't forget to register the location of your_library.uno.so in the your_library.uno.rdb. This is done with regcomp tool :
<pre>
regcomp -Register -r your_library.uno.rdb -c <somewhere>/your_library.uno.so
</pre>

An other way is to use pkgchk or the recent unopkg for Ooo2.0x.

= The Bootstrap =

Bootstrapping can be defined in saying it's the way to obtain a service manager. We present two different examples of bootstraping.
== C++ UNO bootstrapping via defaultBootstrap_InitialComponentContext() ==
We have have already described this bootstrap method because it concerns the classical SDK example we started with in chapter 4 (see <OpenOffice.org1.1_SDK>/examples/DevelopersGuide/ProfUNO/CppBinding).
We provide here two different views to explain how it works.
First we recall with the Figure below how we program it. It's easy to see the first C++ instruction is
<code>[cpp]
//C++
defaultBootstrap_InitialComponentContext();
</code>
But when drawing details from the figure we cannot infer how it works and particularly with registery. It's only because Figure below is a C++/Java programmer point of view.

[[Image:ch4Fig1bootstrap.png]]

To see what happens during the beginning of bootstrap, we go and see the binary in <OpenOffice.org1.1_SDK>/LINUXexample.out/bin
where binaries are constructed by default makefiles. We see three files :
* office_connect the binary executable
* office_connectrc : file with this content :
<pre>
UNO_TYPES=$SYSBINDIR/office_connect.rdb
UNO_SERVICES=$SYSBINDIR/office_connect.rdb
</pre>
* office_connect.rdb

The files construction will perhaps help us to understand beter. We give again the make dependency of office_connect in Figure 1.4 which shows us how office_connect.rdb is constructed :
* a regmerge starting from types.rdb
* a regcomp to register somes classics uno.so files.
And now to learn how office_connect.rdb is used we have to search in makefile how the binary is launched :
the line
<pre>
%.run: $(OUT_BIN)/%$(EXE_EXT)
cd $(subst /,$(PS),$(OUT_BIN)) && $(basename $@)
</pre>
is expanded as
<pre>
cd ../../../../LINUXexample.out/bin && office_connect
</pre>
which shows no reference to office_connect.rdb. Then we have to probe how it works.
* the office_connectrc is automaticly loaded. One way to test that is to rename this file which gives as result
<pre>
make: *** [office_connect.run] Erreur 134
</pre>
* renaming only office_connect.rdb gives the same error :
<pre>
make: *** [office_connect.run] Erreur 134
</pre>
* renaming office_connect.rdb as office_connect2.rdb and changing office_connectrc content, as seen below, works well.
<pre>
UNO_TYPES=$SYSBINDIR/office_connect2.rdb
UNO_SERVICES=$SYSBINDIR/office_connect2.rdb
</pre>
'''Conclusion''' : we have found how it works : when you launch a binary it automaticaly load office_connectrc and put the file office_connect2.rdb in the good place.

== C++ UNO bootstrapping via Bootstrap_InitialComponentContext() ==
The documentLoader example (see <OpenOffice.org1.1_SDK>/examples/cpp/DocumentLoader)
uses an other way to bootstrap. We want to describe it now. As usualy we first begin with program framework in the Figure below.

[[Image:SecondBootstrap.png]]

In this second case we clearly see that DocumentLoader.rdb file is involved and loaded. The only difference is with registry. We find again a rdb file but not a rc file. The consequence is the presence of a regcomp command specific to regitery the binary/executable file.

This example will not work if OpenOffice.org is not running. In this example, the interaction between OpenOffice.org and some.bin is through the network. In other words, the programs can run on different computers. You must run OpenOffice.org in such a way it waits for an UNO connection (here only from localhost) :
<pre>
<Ooo>/program/soffice "-accept=socket,host=localhost,port=8100;urp;StarOffice.ServiceManager"
</pre>

= Playing with regview =

{{Stub}}

= How can we registry in C++ ? =
It is easy to find an example with registry. As first example we can take the [[Counter_Example|counter example]]. Why it's an interesting example is only because it's a two files example : counter.cxx and countermain.cxx. Counter.cxx is compiled in counter.uno.so (counter.uno.dll in windows plateforms) and a counter.uno.rdb file is created. As shown above this file is for registry.

But what is new is, registry will be performed by the second program : countermain.cxx. And then reading this file gives us the possibility to view how this is done in C++ (see the below)
<code>[cpp]
//Listing 2 Countermain.cxx example
// C++
....

// register my counter component
Reference< XImplementationRegistration > xImplReg(
xMgr->createInstanceWithContext(OUString::createFromAscii(
"com.sun.star.registry.ImplementationRegistration"), xContext), UNO_QUERY);
OSL_ENSURE( xImplReg.is(),
"### cannot get service instance of \"com.sun.star.registry.ImplementationRegistration\"!" );

if (xImplReg.is())
{
xImplReg->registerImplementation(
OUString::createFromAscii("com.sun.star.loader.SharedLibrary"),
// loader for component
#ifdef UNX
#ifdef MACOSX
OUString::createFromAscii("counter.uno.dylib"), // component location
#else
OUString::createFromAscii("counter.uno.so"), // component location
#endif
#else
OUString::createFromAscii("counter.uno.dll"), // component location
#endif
Reference< XSimpleRegistry >() // registry omitted,
// defaulting to service manager registry used
);
</code>
An other look into countermain.cxx file is showing the bootsrap is achieved like in the DocumentLoader example and then provide the XComponentContext (xContext) and XMultiComponentFactory (xMgr) useful for registry.
We cannot continue without wondering what is XImplementationRegistration interface ? We gives again the corresponding IDL file :
<pre>
// IDL
module com { module sun { module star { module registry {
interface XImplementationRegistration: com::sun::star::uno::XInterface
{
void registerImplementation( [in] string aImplementationLoader,
[in] string aLocation,
[in] com::sun::star::registry::XSimpleRegistry xReg )
raises( com::sun::star::registry::CannotRegisterImplementationException );
boolean revokeImplementation( [in] string aLocation,
[in] com::sun::star::registry::XSimpleRegistry xReg );
sequence<string> getImplementations( [in] string aImplementationLoader,
[in] string aLocation );
sequence<string> checkInstantiation( [in] string implementationName );

};
}; }; }; };
</pre>
We see new methods and among others one we want to test: getImplementations. We then add this code in the countermain.cxx
<code>[cpp]
//Listing 3 The countermain.cxx example modified
// C++
Sequence <OUString> OUStrs =xImplReg->getImplementations(
OUString::createFromAscii("com.sun.star.loader.SharedLibrary"),
OUString::createFromAscii("counter.uno.so"));
for (int i=0;i<OUStrs.getLength();i++){
OString toPrintOut = OUStringToOString(OUStrs[i],RTL_TEXTENCODING_ASCII_US);
printf("-- %s\n",toPrintOut.pData->buffer);
}
</code>
which prints out :
<pre>
< MyCounterImpl ctor called >
42,43,42
-- com.sun.star.comp.example.cpp.Counter
< MyCounterImpl dtor called >
</pre>

This means : if I use SharedLibrary service to load counter.uno.so, I will have the implementation name « com.sun.star.comp.example.cpp.Counter ». This information is stored in registery as Developpers Guide states. In our example :
<pre>
[smoutou@p3 counter]$ regview ../../../LINUXexample.out/bin/counter.uno.rdb /IMPLEMENTATIONS
</pre>

gives the result :
<pre>
Listing 5 Content of the key /IMPLEMENTATION
Registry "file:///home/smoutou/OpenOffice.org1.1_SDK/LINUXexample.out/bin/counter.uno.rdb":

/IMPLEMENTATIONS
/ com.sun.star.comp.example.cpp.Counter
/ UNO
/ ACTIVATOR
Value: Type = RG_VALUETYPE_STRING
Size = 34
Data = "com.sun.star.loader.SharedLibrary"

/ SERVICES
/ foo.Counter
/ LOCATION
Value: Type = RG_VALUETYPE_STRING
Size = 15
Data = "counter.uno.so"
</pre>
where we see the association between « com.sun.star.comp.example.cpp.Counter » name and a dynamic library (under Linux) « counter.uno.so »

It is possible to get the service name :
<pre>
Listing 6 Retrieving the Service Name
[smoutou@p3 counter]$ regview ../../../LINUXexample.out/bin/counter.uno.rdb /IMPLEMENTATIONS/com.sun.star.comp.example.cpp.Counter/UNO/SERVICES
Registry "file:///home/smoutou/OpenOffice.org1.1_SDK/LINUXexample.out/bin/counter.uno.rdb":

/IMPLEMENTATIONS/com.sun.star.comp.example.cpp.Counter/UNO/SERVICES
/ foo.Counter
[smoutou@p3 counter]$
</pre>

Here the result is « foo.Counter ».
We want to retrieve the information of Listing 6 but with C++ programming. Again you can modify the countermain.cxx example (just after the last line given in Listing 2) as shown below :
<code>[cpp]
//Listing 7 Retrieving the Service Name in C++
// C++
Sequence <OUString> OUStrs =xImplReg->getImplementations(
OUString::createFromAscii("com.sun.star.loader.SharedLibrary"),
OUString::createFromAscii("counter.uno.so"));
for (int i=0;i<OUStrs.getLength();i++){
OString toPrintOut = OUStringToOString(OUStrs[i],RTL_TEXTENCODING_ASCII_US);
printf("-- %s\n",toPrintOut.pData->buffer);
}
OUStrs = xImplReg->checkInstantiation(
OUString::createFromAscii("foo.Counter"));
printf("****\n");
for (int i=0;i<OUStrs.getLength();i++){
OString toPrintOut = OUStringToOString(OUStrs[i],RTL_TEXTENCODING_ASCII_US);
printf("** %s\n",toPrintOut.pData->buffer);
}

Reference< XSimpleRegistry > xSimpleReg(
xMgr->createInstanceWithContext(OUString::createFromAscii("com.sun.star.registry.SimpleRegistry"), xContext), UNO_QUERY);
if(xSimpleReg.is())printf("OK XSimpleRegistry\n");

xSimpleReg->open(OUString::createFromAscii(
"file:///home/smoutou/OpenOffice.org1.1_SDK/LINUXexample.out/bin/counter.uno.rdb"),
false,false);
// How to retrieve all the keys :
Reference< XRegistryKey > xRegKey= xSimpleReg->getRootKey();
if(xRegKey.is())printf("OK XRegistryKey\n");
OUStrs = xRegKey->getKeyNames();
printf("++++ \n");
for (int i=0;i<OUStrs.getLength();i++){
OString toPrintOut = OUStringToOString(OUStrs[i],RTL_TEXTENCODING_ASCII_US);
printf("+++ %s\n",toPrintOut.pData->buffer);
// prints out : /UCR /IMPLEMENTATIONS /SERVICES
}
// How to get a sub-key
xRegKey=xRegKey->openKey(
OUString::createFromAscii("/IMPLEMENTATIONS/com.sun.star.comp.example.cpp.Counter/UNO/SERVICES"));
OUStrs = xRegKey->getKeyNames();
printf("$$$$ \n");
for (int i=0;i<OUStrs.getLength();i++){
OString toPrintOut = OUStringToOString(OUStrs[i],RTL_TEXTENCODING_ASCII_US);
printf("$$$ %s\n",toPrintOut.pData->buffer);
// prints out :
// /IMPLEMENTATIONS/com.sun.star.comp.example.cpp.Counter/UNO/SERVICES/foo/Counter

}

xRegKey->closeKey();
xSimpleReg->close();
</code>
which prints out
<pre>
-- com.sun.star.comp.example.cpp.Counter
****
OK XSimpleRegistry
OK XRegistryKey
++++
+++ /UCR
+++ /IMPLEMENTATIONS
+++ /SERVICES
$$$$
$$$ /IMPLEMENTATIONS/com.sun.star.comp.example.cpp.Counter/UNO/SERVICES/foo.Counter
</pre>

= Registry tools in C++ =

== Introduction ==

I want to retrieve and decode Binary information My choice is Xinterface for a test. I wonder if it's possible to retrieve all the information given by regview tool :

<pre>
[smoutou@p3 counter]$ regview ../../../LINUXexample.out/bin/counter.uno.rdb /UCR/com/sun/star/uno/XInterface
Registry "file:///home/smoutou/OpenOffice.org1.1_SDK/LINUXexample.out/bin/counter.uno.rdb":

/UCR/com/sun/star/uno/XInterface
Value: Type = RG_VALUETYPE_BINARY
Size = 326
Data = minor version: 0
major version: 1
type: 'interface'
uik: { 0x00000000-0x0000-0x0000-0x00000000-0x00000000 }
name: 'com/sun/star/uno/XInterface'
super name: ''
Doku: ""
IDL source file: "/home/gb/rpm/BUILD/oo_1.1rc4_src/udkapi/com/sun/star/uno/XInterface.idl"
number of fields: 0
number of methods: 3
method #0: any queryInterface([in] type aType)
Doku: ""
method #1: [oneway] void acquire()
Doku: ""
method #2: [oneway] void release()
Doku: ""
number of references: 0

[smoutou@p3 counter]$
</pre>

== C++ Code to recover Information in a Binary Sequence ==

See the listing below to learn how we can recover binary information in registery.

<code>[cpp]
//Listing 8 Retrieving Information in a Binary Sequence
// C++
....
Reference< XSimpleRegistry > xSimpleReg(
xMgr->createInstanceWithContext(OUString::createFromAscii(
"com.sun.star.registry.SimpleRegistry"), xContext), UNO_QUERY);
OSL_ENSURE(xSimpleReg.is(),"NOK XSimpleRegistry\n");

xSimpleReg->open(OUString::createFromAscii(
"file:///home/smoutou/OpenOffice.org1.1_SDK/LINUXexample.out/bin/counter.uno.rdb"),
false,false);
// How to retrieve all the keys :
Reference< XRegistryKey > xRegKey= xSimpleReg->getRootKey();
OSL_ENSURE(xRegKey.is(),"NOK XRegistryKey\n");
// How to get a sub-key
xRegKey=xRegKey->openKey(
OUString::createFromAscii("/UCR/com/sun/star/uno/XInterface"));

printf("//// \n");
OUString OUStr;
OString toPrintOut;
Sequence< sal_Int8 > seqByte;
// still a lot to do in this switch :
switch (xRegKey->getValueType()){
case RegistryValueType_LONG : printf("long\n");break;
case RegistryValueType_ASCII : printf("ascii\n");
OUStr = xRegKey->getAsciiValue();
toPrintOut = OUStringToOString(OUStr,RTL_TEXTENCODING_ASCII_US);
printf("/// %s\n",toPrintOut.pData->buffer);
break;
case RegistryValueType_STRING : printf("string\n");break;
case RegistryValueType_BINARY : printf("RG_VALUETYPE_BINARY\n");
seqByte = xRegKey->getBinaryValue();
printDEBUGMODE(seqByte);
break;
case RegistryValueType_LONGLIST : printf("long list\n");break;
case RegistryValueType_ASCIILIST : printf("ascii list\n");break;
case RegistryValueType_STRINGLIST : printf("string list\n");break;
case RegistryValueType_NOT_DEFINED : printf("not defined\n");break;
}
....
// with the procedure
void printDEBUGMODE(Sequence < sal_Int8 > seqBytes){
sal_Int8 Hexa[16]={'0','1','2','3','4','5','6','7','8','9','A','B','C','D','E','F'};
int lin,col;
sal_Int8 line[80];
sal_Int32 len;
len=seqBytes.getLength();
// print the lenght in decimal and with 4 hexadecimal digits (C notation 0x....)
printf("length : %d Ox%X%X%X%X\n",len,len>>12&0x000F,len>>8&0x000F,len>>4&0x000F,len&0x000F);
len = (len/16)*16; // retire le modulo 16
for(lin=0;lin<len;lin=lin+16){
for(col=0;col<16;col++){
line[3*col]=Hexa[seqBytes[lin+col]>>4];
line[3*col+1]=Hexa[seqBytes[lin+col]&0x0F];
line[3*col+2]=' ';
if ((seqBytes[lin+col]<128)&&(seqBytes[lin+col]>20)) line[50+col]=seqBytes[lin+col];
else line[50+col]='.';
} /* end of for */
line[66]=0; /* end of string...*/
line[48]=' ';line[49]=' ';
for (int i=0;i<66;i++)
printf("%c",static_cast< char >(line[i]));
printf("\n");
} /* end of for */
// the last line is more complicated because not complete
for (lin=len;lin<seqBytes.getLength();lin++){
col=lin-len;
line[3*col]=Hexa[seqBytes[lin]>>4];
line[3*col+1]=Hexa[seqBytes[lin]&0x0F];
line[3*col+2]=' ';
if ((seqBytes[lin]<128)&&(seqBytes[lin]>20)) line[50+col]=seqBytes[lin];
else line[50+col]='.';
}
for (++col;col<16;col++){
line[3*col]=' ';line[3*col+1]=' ';line[3*col+2]=' ';line[50+col]=' ';
}
line[66]=0; /* end of string...*/
line[48]=' ';line[49]=' ';
for (int i=0;i<66;i++)
printf("%c",static_cast< char >(line[i]));
printf("\n");
}
</code>
A carrefully look at the listing above shows we transform the sequence of bytes in a format which recalls the old DOS debug tool.
<pre>
////
RG_VALUETYPE_BINARY
length : 326 Ox0146
12 34 56 78 00 00 01 46 00 00 00 01 00 06 00 00 .4Vx...F........
00 01 00 01 00 02 00 00 00 03 00 00 00 0B 00 00 ................
00 22 00 0C 63 6F 6D 2F 73 75 6E 2F 73 74 61 72 ."..com/sun/star
2F 75 6E 6F 2F 58 49 6E 74 65 72 66 61 63 65 00 /uno/XInterface.
00 00 00 16 00 0D 00 00 00 00 00 00 00 00 00 00 ...............
00 00 00 00 00 00 00 00 00 4E 00 0C 2F 68 6F 6D .........N../hom
65 2F 67 62 2F 72 70 6D 2F 42 55 49 4C 44 2F 6F e/gb/rpm/BUILD/o
6F 5F 31 2E 31 72 63 34 5F 73 72 63 2F 75 64 6B o_1.1rc4_src/udk
61 70 69 2F 63 6F 6D 2F 73 75 6E 2F 73 74 61 72 api/com/sun/star
2F 75 6E 6F 2F 58 49 6E 74 65 72 66 61 63 65 2E /uno/XInterface.
69 64 6C 00 00 00 00 15 00 0C 71 75 65 72 79 49 idl......queryI
6E 74 65 72 66 61 63 65 00 00 00 00 0A 00 0C 61 nterface.......a
6E 79 00 00 00 00 0B 00 0C 74 79 70 65 00 00 00 ny.......type...
00 0C 00 0C 61 54 79 70 65 00 00 00 00 0E 00 0C ....aType.......
61 63 71 75 69 72 65 00 00 00 00 0B 00 0C 76 6F acquire.......vo
69 64 00 00 00 00 0E 00 0C 72 65 6C 65 61 73 65 id.......release
00 00 00 00 0B 00 0C 76 6F 69 64 00 00 00 00 03 .......void.....
00 05 00 03 00 14 00 03 00 04 00 05 00 00 00 01 ................
00 06 00 01 00 07 00 00 00 0E 00 01 00 08 00 09 ................
00 00 00 00 00 00 00 0E 00 01 00 0A 00 0B 00 00 ................
00 00 00 00 00 00 ......

[smoutou@p3 counter]$
</pre>

We see it's possible to understand how these bytes are constituted to hold the information we look for, but it will take a while to investigate further.
I prefere have a look into source code and find : « OOB680_m5/registry/source/reflcnst.hxx »

== Examining the OOo source code ==

For instance before every name we see a « 00 0C » It's effecftively defined in reflcnst.hxx file as :
<code>[cpp]
//Listing 9 reflcnst.hxx File (extract)
// C++
...
enum CPInfoTag
{
CP_TAG_INVALID = RT_TYPE_NONE,
CP_TAG_CONST_BOOL = RT_TYPE_BOOL,
CP_TAG_CONST_BYTE = RT_TYPE_BYTE,
CP_TAG_CONST_INT16 = RT_TYPE_INT16,
CP_TAG_CONST_UINT16 = RT_TYPE_UINT16,
CP_TAG_CONST_INT32 = RT_TYPE_INT32,
CP_TAG_CONST_UINT32 = RT_TYPE_UINT32,
CP_TAG_CONST_INT64 = RT_TYPE_INT64,
CP_TAG_CONST_UINT64 = RT_TYPE_UINT64,
CP_TAG_CONST_FLOAT = RT_TYPE_FLOAT,
CP_TAG_CONST_DOUBLE = RT_TYPE_DOUBLE,
CP_TAG_CONST_STRING = RT_TYPE_STRING,
CP_TAG_UTF8_NAME,
CP_TAG_UIK
};
....
</code>

which learns us this is an info tag of type CP_TAG_UTF8_NAME. If we want to decode header we use this extract :
<code>[cpp]
//Listing 10 reflcnst.hxx File (extract)
// C++
extern const sal_uInt32 magic;
extern const sal_uInt16 minorVersion;
extern const sal_uInt16 majorVersion;

#define OFFSET_MAGIC 0
#define OFFSET_SIZE (OFFSET_MAGIC + sizeof(magic))
#define OFFSET_MINOR_VERSION (OFFSET_SIZE + sizeof(sal_uInt32))
#define OFFSET_MAJOR_VERSION (OFFSET_MINOR_VERSION + sizeof(minorVersion))
#define OFFSET_N_ENTRIES (OFFSET_MAJOR_VERSION + sizeof(sal_uInt16))
#define OFFSET_TYPE_SOURCE (OFFSET_N_ENTRIES + sizeof(sal_uInt16))
#define OFFSET_TYPE_CLASS (OFFSET_TYPE_SOURCE + sizeof(sal_uInt16))
#define OFFSET_THIS_TYPE (OFFSET_TYPE_CLASS + sizeof(sal_uInt16))
#define OFFSET_UIK (OFFSET_THIS_TYPE + sizeof(sal_uInt16))
#define OFFSET_DOKU (OFFSET_UIK + sizeof(sal_uInt16))
#define OFFSET_FILENAME (OFFSET_DOKU + sizeof(sal_uInt16))

#define OFFSET_N_SUPERTYPES (OFFSET_FILENAME + sizeof(sal_uInt16))
#define OFFSET_SUPERTYPES (OFFSET_N_SUPERTYPES + sizeof(sal_uInt16))

#define OFFSET_CP_SIZE (OFFSET_SUPERTYPES + sizeof(sal_uInt16))
#define OFFSET_CP (OFFSET_CP_SIZE + sizeof(sal_uInt16))
</code>

which allows to explain our header :
{| border cellspacing="0" width="550"
|- style = "background:#b3e2d1;text-align:center"
| |Field name||Value
|- style="text-align:center"
| MAGIC||12 34 56 78
|- style="text-align:center"
| SIZE||00 00 01 46
|- style="text-align:center"
| MINOR_VERSION||00 00
|- style="text-align:center"
| MAJOR_VERSION||00 01
|- style="text-align:center"
| N_ENTRIES||00 06
|- style="text-align:center"
| TYPE_SOURCE||00 00
|- style="text-align:center"
| TYPE_CLASS||00 01
|- style="text-align:center"
| THIS_TYPE||00 01
|- style="text-align:center"
| UIK||00 02
|- style="text-align:center"
| DOKU||00 00
|- style="text-align:center"
| FILENAME||00 03
|- style="text-align:center"
| N_SUPERTYPES||00 00
|- style="text-align:center"
| SUPERTYPES||00 0B
|- style="text-align:center"
| CP_SIZE||00 00
|- style="text-align:center"
| CP||00 22
|}

And so on... Is it important to go further ? Not at all, it was only to « play » a little. In fact we can directly recover this information with CoreReflection service (I am not absolutely sure of that). We give in the next section an overview in Ooobasic of this service.

= How do we see the registries in OOoBasic ? =

OooBasic allow many things and in particular to explore registry. [http://www.oooforum.org/forum/viewtopic.php?t=8737 Danny Brewer's code] shows us how to work around ? We have a look at his code :
<code>[oobas]
REM ***** BASIC *****
Sub Main
oReflection = createUnoService( "com.sun.star.reflection.CoreReflection" )
oInfo = oReflection.forName( "nom.dannybrewer.test.XDannysCalcFunctions1" )
aMethods = oInfo.getMethods()
For i = 0 To UBound( aMethods )
oMethod = aMethods( i )
Print oMethod.getName()
Next
End Sub
</code>
We then create an idl file :
<pre>
// IDL
#include <com/sun/star/uno/XInterface.idl>
#include <com/sun/star/lang/XInitialization.idl>

module my_module
{

interface XSomething : com::sun::star::uno::XInterface
{
long getCount();
void setCount( [in] long nCount );
long increment();
long decrement();
};

service MyService
{
interface XSomething;
};
};
</pre>

With this IDL file, we create a rdb file and register this rdb file. Now OpenOffice.org works as if we have an add-on even if we have not written its code. We cannot launch this add-on (without its code !) but we can see it.
We then modify the above Danny's program :
<code>[oobas]
REM Listing 11
REM ***** BASIC *****
'From Danny : http://www.oooforum.org/forum/viewtopic.php?t=8737
Sub Main
oReflection = createUnoService( "com.sun.star.reflection.CoreReflection" )
oInfo = oReflection.forName( "my_module.XSomething" )
aMethods = oInfo.getMethods()
'XRay.XRay oInfo
print UBound( aMethods )+1 & " methods : ****"
For i = 0 To UBound( aMethods )
oMethod = aMethods( i )
Print oMethod.getName()
Next

aTypes = oInfo.getTypes()
print UBound( aTypes )+1 & " types : ****"
For i = 0 To UBound( aTypes )
oType = aTypes( i )
Print "Types : " + oType.getName()
Next

aInterfaces = oInfo.getInterfaces()
print UBound( aInterfaces )+1 & " interfaces : ****"
For i = 0 To UBound( aInterfaces )
oInterface = aInterfaces( i )
Print "Interfaces : " + oInterface.getName()
Next
End Sub
</code>
launching this modified program produces :
<pre>
7 methods : ****
queryInterface acquire release getCount setCount increment decrement
3 types : ****
Types : com.sun.star.reflection.XIdlClass
Types : com.sun.star.lang.XTypeProvider
Types : com.sun.star.uno.XWeak
0 Interfaces : ****
</pre>
We can see among others the four methods given in the IDL file.
To go further in C++ see [[XIDLReflection_Interface| XdlRefection Interface]]

{{Template:Home_Page}}

= See Also =

*[[Tutorial_UNO_Library|UNO tutorial]]
*[[Tutorial_UNO_IDL|UNO IDL]]
* [[Uno/Article/Types%26Reflection]]
* [http://perso.wanadoo.fr/moutou/MyUNODoc_HTML/UNOCppAPI11.html UNO registry and bootstrapping] (Chapter 11 from UNO/C++ document)
* Writing a Program to Control OpenOffice.org, by Franco Pingiori — [http://www.linuxjournal.com/article/8550 Part 1] and [http://www.linuxjournal.com/article/8608 Part 2], Linux Journal

[[Category:Development]]
[[Category:Cpp]]
[[Category:Uno]]
[[Category:Tutorial]]
[[Category:MacOSX]]

Penny

2007-01-17T11:23:11Z

Jiangc: Penny moved to Main Page: revert

#REDIRECT [[Main Page]]

DomainDeveloper

2006-12-29T06:01:02Z

Jiangc: /* Developers */

A mapping of names to OOo accounts.

Abbrev.:

* PL : Project Lead
* CL : Project Co-Lead
* CC : Community Council Member
* ESC : Engineering Steering Committee Member
* CVS : has write access to the OOo CVS repository

----

=== Developers ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse;"
|-
! Name || CVS || @openoffice.org || [[IRC Communication]] || Notes || Affiliation
|-
| || || || || ||
|-
| Volker Ahrendt|| X || va||||||Sun Microsystems
|-
| Kai Ahrens|| X || ka || Kai_Ahrens ||PL Graphic Applications||Sun Microsystems
|-
| Gene Anaya|| || ganaya||||||
|-
| Joost Andrae|| X || ja||ja||CL qa, release testing en-US builds and releasing builds||Sun Microsystems
|-
| Eric Bachard|| X || ericb||ericb2||Mac OSX/Linux PPC ports/CL porting||French OOo project
|-
| Kai Backman|| || kaib ||KaiB||||
|-
| Sascha Ballach|| X || sab||||||
|-
| Jayant Balraj Madavi|| || jayant_madavi||aZEN_JM||Connectivity / Database||Novell, Inc.
|-
| Jörg Barfurth|| X || jb||JoergB||Configuration Util||Sun Microsystems
|-
| Mathias Bauer|| X || mba||||PL Framework, XML||Sun Microsystems
|-
| Thorsten Behrens|| X || thb||thorsten||vcl/impress/toolkit visionary||Sun Microsystems
|-
| Thomas Benisch|| X || tbe||||Scripting framework||Sun Microsystems
|-
| Stefan Bergmann|| X || sb||||CL UDK, tools&UCB hacker||Sun Microsystems
|-
| Andreas Bille|| X || abi||||||Sun Microsystems
|-
| Éric Bischoff|| X || ebischoff||ebischoff||KDE A/B driver||Bureau Cornavin
|-
| Nick Blievers|| X || nick||||IRIX||
|-
| Daniel Boelzle|| X || dbo||||UNO core/bridges/packages||Sun Microsystems
|-
| Oliver Bolte|| X || obo||||RE||Sun Microsystems
|-
| Rafaella Braconi|| || coni||||CL l10n, globalization program manager||Sun Microsystems
|-
| Michael Brauer|| X || mib||||PL XML||Sun Microsystems
|-
| Oliver Braun|| X || obr||obr||System Integration/Accessibility Hacker||Sun Microsystems
|-
| Andreas Bregas|| X || ab||||StarBasic||Sun Microsystems
|-
| Jörg Brunsmann|| || jbrunsmann||||UDK||
|-
| Jörg Budischewski|| || jbu||PyUNO hacker||||Sun Microsystems
|-
| Peter Burow|| X || pb||UI||||Sun Microsystems
|-
| Aidan Butler|| || aidan||||XML filters||
|-
| Giuseppe Castagno || X || beppec56 || beppec56_ or beppe_c || PDF output
|-
| Scott Carr|| || kcarr||kcarr||Documentation||Progbits
|-
| Colin Charles|| || drbyte||bytee||Malaysian native-lang project||bytebot.net
|-
| Behrend Cornelius|| X || bc||||Wizards||Sun Microsystems
|-
| Michael Cziebalski|| || mci||||||
|-
| [[User:pdefilippis|Pierre de Filippis]]|| X || pdefilippis||aliscafo||Mac OSX native porting||
|-
| Andrew Dent|| X ||ace_dent||ace_dent||ui/custom_images||
|-
| Naren Devaiah|| || ||ndev||Performance||Intel Corporation
|-
| Nitin Dongre|| || ||nitin_BITS||||Novell, Inc.(intern)
|-
| Radek Doulik|| || radekdoulik||rodo_||Canvas hacker||Novell, Inc.
|-
| Carsten Driesner|| X || cd||||Framework||Sun Microsystems
|-
| Herbert Duerr|| X || hdu||hdu_hh||GSL||Sun Microsystems
|-
| Oliver Düsterhoff|| X || od||Writer||||Sun Microsystems
|-
| Bernd Eilers|| X || bei||rfc821||EIS||Sun Microsystems
|-
| René Engelhard|| X || rene||_rene_||config_office, Debian packager||Debian
|-
| Andre Fischer|| X || af||||Impress||Sun Microsystems
|-
| Uwe Fischer || || ufi || || || Sun Microsystems
|-
| Ken Foskey|| || waratah||waratah||config_office/dmake man||slug.org.au
|-
| Duncan Foster|| || dfoster||||||
|-
| David Fraser|| || davidfraser||davidfraser||South African translations, multilingual builds||translate.org.za
|-
| Nils Fuhrmann|| || nf||||Localization||Sun Microsystems
|-
| Martin Gallwey|| X || mtg||marty_||XML/Writer/packaging||
|-
| Pierre-Andre Galmes || || pagalmes || pagalmes || Chart2 ||
|-
| Tony Galmiche|| X || tonygalmiche||||CL FR native-lang project||
|-
| Sunil Gandhi|| || ||tyro||||NOSIP
|-
| Sophie Gautier|| X || sgauti|| sophi ||PL FR native-lang project, CC ||.
|-
| Vladimir Glazounov|| X || vg||||RE||Sun Microsystems
|-
| Laurent Godard || X || laurentgodard || lgodard || CC, PL Extensions, Fr Native-lang Project || inDesko/Nuxeo
|-
| Jody Goldberg|| X || jodygoldberg||jody||[[Calc]] spreadsheet-ness||Novell, Inc.
|-
| Dirk Grobler|| X || dg||||Database Access||Sun Microsystems
|-
| Bettina Haberer|| || bh||||RFEOwner||Sun Microsystems
|-
| Ingrid Halama|| X || iha||||Chart||Sun Microsystems
|-
| Chris Halls|| X || haggai||haggai||Debian packager&misc. hacker||Credativ Ltd., Debian
|-
| Gregor Hartmann|| X || gh|| Lachs ||Testtool||Sun Microsystems
|-
| Bustamam Harun|| || bustamam||||Malaysian stuff||
|-
| Kevin Hendricks|| X || khendricks||||PL Lingucomponent, PowerPC||
|-
| Con Hennessy|| || cphennessy||cph2 or cph_||hacker & former council person||OpenApp
|-
| Ivo Hinkelmann|| X || ihi||ivo||l10n tooling/general/RE||Sun Microsystems
|-
| Eric Hoch|| X || maveric||mav_eric||Mac Porting||
|-
| [[User:Lutz_Hoeger|Lutz Hoeger]]|| || lho||lutzh||[[User Experience]]||Sun Microsystems
|-
| Jan Holešovský|| X || kendy||kendy||KDE integration||Novell, Inc.
|-
| Martin Hollmichel|| X || mh||Ratte/Nesshof||Build Maestro, PL External, Tools, Porting, CC||Sun Microsystems
|-
| Karl Hong|| X || khong||||i18n, CJK expert||Sun Microsystems
|-
| Matthias Huetsch|| X || mhu||||Performance/strategy, PL UCB, CC, ESC||Sun Microsystems
|-
| Michael Hönnig|| X || mi||||PL API||
|-
| [[User:icobgr|Hristo Hristov]] || || icobgr || icobgr || PL Bulgarian native-lang project ||
|-
| Sven Jacobi|| X || sj||||Escherwizard||Sun Microsystems
|-
| Jörg Jahnke|| || jj||||Internal tooling||Sun Microsystems
|-
| Christian Jansen|| || cj ||||Menu and Toolbar?||Sun Microsystems
|-
| Ocke Janssen|| X || oj||Base||||Sun Microsystems
|-
| Pavel Janík|| X || pjanik||paveljanik||PL Czech native-lang project, CL l10n, CC, ESC, l10n builds||
|-
| Berry Jia|| X || berryjia||||||Sun Microsystems
|-
| Pascal Junck|| || pjunck||||||Sun Microsystems
|-
| Peter Junge|| X || pj|| peter13j|| OOo community contact for my Chinese Employer, QA||Beijing Redflag CH2000
|-
| Christian Junker|| || Cyb||christianju||API||Trees For Life
|-
| Hirano Kazunari|| || khirano||||Japanese||
|-
| Dhananjay Keskar|| X || dkeskar ||dkeskar||Performance,Buildbot,cat-herder||Intel Corporation
|-
| Robert Kinsella|| || rkinsella||||||Sun Microsystems
|-
| Volodymyr Khrystynych|| || volody||||XML Filter||
|-
| Matthias Klose|| || doko||doko||Ubuntu, gcc, python packager||Canonical, Inc.
|-
| Laszlo Kovacs|| || lkovacs||||Documentation||
|-
| Martin Kretzschmar|| X || mkretzschmar||martink||Gnome / Debian||Student
|-
| Will Lachance|| || wlach||wlach_||Word Perfect File Filters||Net Integration Technologies, Inc.
|-
| Thomas Lange|| X || tl||||||Sun Microsystems
|-
| Lars Langhans|| X || lla||||||Sun Microsystems
|-
| Hans-Joachim Lankenau|| X || hjs||ause||dmake makefile expert, RE||Sun Microsystems
|-
| Németh László|| X || nemeth||||PL lingucomponent||
|-
| Jakob Lechner|| X || jakob_lechner||||Writer||Fabalabs
|-
| Michael Leibowitz|| X || mikeleib ||mikeleib||performance||Intel Corporation
|-
| Wind Li|| X || windly||||Address books||
|-
| Ping Liao|| || pliao||||||
|-
| Tor Lillqvist|| X || tml||tml_||||Novell, Inc.
|-
| Joachim Lingner|| X || jl||||Java, CLI||Sun Microsystems
|-
| Christian Lippka|| X || cl||ChristianL||Graphic Applications||Sun Microsystems
|-
| Mindy Liu|| || mindyliu||||||
|-
| Dieter Loeschky|| X || ||||Localization||Sun Microsystems
|-
| Philipp Lohmann|| X || pl||pl_hh||VCL/X11 (GSL) hacker||Sun Microsystems
|-
| Jackson Low|| X || xxjack12xx||||Porting||
|-
| Patrick Luby|| || pluby||||Mac||
|-
| Prasad Madhav || X || pmadhav || pmadhav || Buildbot || Intern@Intel
|-
| Babak Mahbod|| || bmahbod||||||
|-
| Martin Maher|| || mmaher||||Writer & Filter chap||
|-
| Nakata Maho|| X || maho||_maho_||PL QA, FreeBSD guy||Independent
|-
| John Marmion|| X || jmarmion||||||
|-
| Andreas Martens|| X || ama||||PL Writer||Sun Microsystems
|-
| [[User:smsm1|Shaun McDonald]] || X || smsm1 || shaunmcdonald || Mac Port, buildbot MacPort1 || Student
|-
| Caolán McNamara|| X || cmc||caolan||CL Writer & Filter man||RedHat, Inc.
|-
| Michael Meeks|| X || mmeeks||michael_||ugly hack-er, ESC||Novell, Inc.
|-
| Frank Meies|| X || fme||||Writer||Sun Microsystems
|-
| Federico Mena-Quintero|| || federicomena||federico||perfectionist||Novell, Inc.
|-
| Michael Mi|| || mmi||||||
|-
| Björn Milcke|| X || bm||bm_||Chart||Sun Microsystems
|-
| Petr Mladek|| || pmladek||pmladek||SUSE RPMs, ooo-build releases||Novell, Inc.
|-
| Cyrille Moureaux|| X || cyrillem||Cyrille||||Sun Microsystems
|-
| [[User:Mmp|Matthias Müller-Prove]]|| || mmp|| mprove|| [[User Experience]] Engineer, http://ui.openoffice.org || Sun Microsystems
|-
| Niklas Nebel|| X || nn||||PL [[Calc]]||Sun Microsystems
|-
| Christoph Neumann|| X || cn||||API tests||Sun Microsystems
|-
| NicelKM|| X || mnicel||nicel||||Novell, Inc.
|-
| Bertram Nolte|| || bnolte||||||
|-
| Tomas O'Connor|| || toconnor||||Scripting Framework||
|-
| Lars Oppermann|| X || lo||||||Sun Microsystems
|-
| Rodrigo Parra Novo|| X || rodarvus||rodarvus||Gnumeric/Abiword OpenDocument Format support and port to Maemo||INdT (Instituto Nokia de Tecnologia)
|-
| Edward Peterlin|| X || OPENSTEP||||Mac||
|-
| Frank Peters|| X || fpe||||Documentation||Sun Microsystems
|-
| Christof Pintaske|| X || cp||||||Sun Microsystems
|-
| Ron Piterman|| || rpiterman||||||
|-
| Noel Power|| || npower||noelp||VBA Interop, Scripting||Novell, Inc.
|-
| Nikolai Pretzell|| X || np || ||Autodoc, code quality||Sun Microsystems
|-
| Volker Quetschke|| X || vq||vq||W32-tcsh/bash build environment and dmake Hacker, ESC||Gravity Waves
|-
| Tino Rachui|| X || tra||tinor||GSL/Unix Hacker||Sun Microsystems
|-
| [[User:Kr|Kay Ramme]]|| X || kr||||PL UDK||Sun Microsystems
|-
| [[User:ErAck|Eike Rathke]]|| X || er||erAck||CL [[Calc]], engine; CL i18n; stricken with number formatter||Sun Microsystems
|-
| Michael Rauch|| X || mrauch||||NetBSD||
|-
| Jens-Heiner Rechtien|| X || hr||blauwal||RE; OOo SCM (CVS, CWS tooling); Porting; Compilers||Sun Microsystems
|-
| Daniel Rentz|| X || dr||||[[Calc]] Excel filter, UI||Sun Microsystems
|-
| Florian Reuter|| X || flr||||Writer filters||Novell, Inc.
|-
| Georg Richter|| X || grichter||georg||Base, native MySQL driver||MySQL AB
|-
| G. Roderick Singleton|| || grsingleton||grsingleton||Documentation||pathtech.org
|-
| Hennes Rohling|| X || hro||||GSL & Util||Sun Microsystems
|-
| Bibek Sahu|| || Bibek||bibek||Impress pieces||Trees For Life
|-
| Andreas Schlüns|| X || as||||Framework||Sun Microsystems
|-
| Ingo Schmidt|| X || is||||(Native) Installation||Sun Microsystems
|-
| [[User:Jsc|Jürgen Schmidt]]|| X || jsc||jsc||PL API, CL Extensions, UNO, SDK||Sun Microsystems
|-
| Stephan Schäfer|| X || ssa||ssa||VCL||Sun Microsystems
|-
| Frank Schönheit|| X || fs||FrankS||Database Access, Forms||Sun Microsystems
|-
| Julian Seward || || sewardj || || valgrind ||
|-
| Darragh Sherwin|| || dsherwin||darragh||E-Legislation / E-GovSystems||Propylon
|-
| Raul Siddhartha|| || rsiddhartha||raul||GTK File Selector||Novell, Inc.
|-
| Sarah Smith|| || ssmith||||||
|-
| Rajesh Sola|| || rajeshsola||sola||misc.||NOSIP
|-
| Kai Sommerfeld|| X || kso||||manager & hacker||Sun Microsystems
|-
| Oliver Specht|| X || os||||PL UI||Sun Microsystems
|-
| Jörg Spindler|| || jspindler||||||
|-
| Fridrich Štrba|| X || fridrich_strba||Fridrich||Word Perfect Hacker||
|-
| Ulf Stroehler|| || us||||||Sun Microsystems
|-
| Muthu Subramanian|| || muthusuba||muthusuba||misc.||
|-
| Louis Suárez-Potts|| || louis||louis||Community Manager||Collab.net
|-
| Claus Sørensen|| || cs||c26n,cHBs,chbs||Danish Localization and Project Management Tool(oopm)||ProFOSS
|-
| Stefan Taxhet|| X || st||stx12||CC, interpersonal problem fixer||Sun Microsystems
|-
| Armin Theissen|| || armin||||||
|-
| Caio Tiago Oliveira|| X || asrail||asrail||CL QA||Independent
|-
| Jan Tietjens|| || tietjens||||||
|-
| Rüdiger Timm|| X || rt||||RE||Sun Microsystems
|-
| Malte Timmermann|| X || mt||||||Sun Microsystems
|-
| Gerhard Tonn|| || tonn||||s390||
|-
| Willem van Dorp|| || willem.vandorp||||||
|-
| Tom Verbeek|| X || tv||||Wizards, Art team||Sun Microsystems
|-
| Sander Vesik|| || svesik||||||
|-
| Daniel Vogelheim|| X || dvo||||XML||
|-
| Mikhail Voitenko|| X || mav||Framework||||Sun Microsystems
|-
| Robert Vojta|| X || rvojta||rvojta||VBA Interop||
|-
| Dirk Völzke|| X || dv||||Installation||Sun Microsystems
|-
| [[User:Sparcmoz|Jim Watson]]|| X || sparcmoz|| sparcmoz||GNU Linux sparc porter||clug.org.au
|-
| Armin Weiss|| X || aw||||||Sun Microsystems
|-
| Dan Williams|| X || fa||dcbw||Mac et. al. hacker||RedHat, Inc.
|-
| Stephan Wunderlich|| X || sw||||||
|-
| Kohei Yoshida|| X || kohei||kohei_||[[Calc]] hacker, Calc optimization solver developer||SlickEdit, Inc.
|-
| George Zahopoulos|| X || georgez||||||
|-
| Kurt Zenker|| X || kz||smoketester||RE||Sun Microsystems
|-
| Claudio F Filho|| || filhocf||filhocf||Brazilian portuguese Localization||BrOffice.org
|-
| Xiaoyang Yu|| || || ||Disk block reordering||Intel Corporation
|-
| Antonio Xu|| X || antoxu || antoxu || Async dialogs, PRC improvements || Intel Corporation
|-
| Rail Aliev || X || rail || rail || Ru and Tr NL Co-lead || Infra-Resource
|-
| Jeremy Zheng|| X || zhiming || Jeremy || Async dialogs, PRC improvements || Intel Corporation
|-
| [[User:Schmidtm|Matthias Schmidt]] || || schmidtm || schmidtm || Mac OSX Aqua Port || Sun Microsystems
|-
| Yuri Dario || || ydario || Paperino || OS/2 Port || Serenity Systems intl
|-
| Wei Zhao || || weiz || || Chinese Localization || Beijing Redflag CH2000
|-
| Liu Tao || || liutao || || PyUNO, Async dialogs|| Beijing Redflag CH2000
|-
| JiangChuang || || jiangc || || || Beijing Redflag CH2000
|-
|}

=== QA Engineers ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse;"
|-
! Name ||CVS||@openoffice.org || [[IRC Communication]] || Interested modules || Notes || Affiliation
|-
| Stefan Baltzer||||sba||||writer||||Sun Microsystems
|-
| Thorsten Bosbach||X||tbo||||framework, qa/qatesttool||QA Framework / Automation||Sun Microsystems
|-
| Oliver Craemer||X||oc||||[[Calc]]||QA Calc / Automation||Sun Microsystems
|-
| Helge Delfs||X||hde||||writer, qa/qatesttool||QA Writer / Automation||Sun Microsystems
|-
| Fredrik Haegg||X||fha||||draw, impress, qa/qatesttool||QA Graphics / Automation||Sun Microsystems
|-
| Hasan Ilter||||hi||||writer, printing, pdf export||||Sun Microsystems
|-
| Michael Rüß||||mru||||writer, word im/export||||Sun Microsystems
|-
| Éric Savary||||es||||writer, accessibility||||Sun Microsystems
|-
| [[User:jsi|Joerg Sievers]]||X||jsi||jogi||qa/qatesttool, [[Calc]]||Automation / QA Calc||Sun Microsystems
|-
| Joerg Skottke||X||jsk||skotti||framework, qa/qatesttool||QA Framework / Automation||Sun Microsystems
|-
| Marc Neumann||X||msc||||database, qa/qatesttool||QA Base / Automation||Sun Microsystems
|-
| Chris Lukasiak||||clu||||database||||Sun Microsystems
|-
| Frank Stecher||||fst||||[[Calc]]||||Sun Microsystems
|-
| Jack Warchold|||| jw||||writer, import/export filters||||Sun Microsystems
|-
| Uwe Luebbers||||ul||||framework||||Sun Microsystems
|-
| Thorsten Martens||||tm||||framework||||Sun Microsystems
|-
| Olaf Felka|||| of||||framework, installation||||Sun Microsystems
|-
| Thomas Klarhoefer||||kla||||chart||||Sun Microsystems
|-
| Wolfram Garten|||| wg||||draw, impress||||Sun Microsystems
|-
| Christian Guenther||||cgu||||draw, impress||||Sun Microsystems
|-
| [[User:Thorsten_Ziehm|Thorsten Ziehm]]||||| thorstenziehm||||||QA lead||Sun Microsystems
|-
|}

We are tracking pending JCAs in the document [[Pending JCAs]].

== Related Pages ==
* [[User Experience Community]]
* A map of OOo developers around the world is available at http://www.frappr.com/ooodev, please add yourself to the map if you're involved in OOo development. It's just fun to see who's where :-)

[[Category:Development]]