Le Jeudi 21 Juillet 2005 08:32, Jürgen Schmidt a écrit :
> Hi,

Hi Jürgen,

First of all, thanks for your reply ! It helped-me not to panic when an error 
occured during the compile phase and to focus my mind only on the important 
points while compiling !

After this experience, I have quite a few hints on how I would have gained 
time. Hope it can help to improve the learning experience with OpenOffice.

1 - Adding some tutorials 

> i suggest that you take a look into the SDK examples and read the First
> Steps and Professional UNO chapter of the Developers Guide. 

I had already read the Dev's Guide, which is quite huge, but that not answers 
to all the newbies questions. 

a - Hello world Tutorial from scratch for C++

I found not much documentation about the building process. There is no 
tutorial explaining how to develop a  C++ project with OpenOffice from 
scratch.

It explains the coding part, but the not the practical aspects such as, which 
directories to include in my project (the ), which Shell vriables need to be 
set, how to write a Makefile for OpenOffice...

It would really be nice to have such a tutorial. It would give more confidence 
for new developers.

b - Minimal project archive

It would be nice to give in the SDK a "minimal" component project which would 
include exactly what is needed to compile it, so that if you take the 
directory and move it away from the SDK, it could still compile by launching 
a configure and trying not to refer to the SDK. It could look like :

my_project
        |_ Makefile
        |_ my_project.cxx
        |_ main.cxx
        |_ include
                |_ ...
        |_ setsdkenv
        |_ settings
        |_ ...

In such a way, starting a new project woul be much more straightforward.

I could take some time to write the documentation I just described for Linux 
if you like.

Would it be of any help for you ? If writen, would it be possible to include 
it in the SDK ?


Cheers,
Pierre-André
-- 
StarXpert - www.starxpert.fr
e-mail : [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to