Hi Marc, > Seriously spoken it appears really hard to get the necessary knowledge > of the inner workings in the source and it's layers - not speaking of > extensions here where the API and services are to deal with. I wonder > how this hurdle could be lowered. I'm really not anxious regarding > foreign code (I did some hacking in other projects like qcad1's dxf > import or hdf5), but OO.o is a monster, isn't it?
well, the knowledge where to start could be provided :) For the concrete issue, I in fact think that a) there are only two places to adjust and b) you can even use the immediate UNO API there, which means you have a documentation of the API you use (which is ... not always the case with the internal C++ API). Anyway. Yes, the entry hurdles for hacking the C++ part of OOo are still pretty high. I know, but I do not know how to change this ... Except advertising, and giving support where possible. Usually, newcomers will find much more courtesy for their contributions than experienced developers would - means we're glad if you come up with *anything* which gets you started. Extensions are a different topic, though. I think here the way is to provide good documentation and good tools - unfortunately, I sometimes have the impression both isn't on high priority :( Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
