Hi Pierre, 2005/7/25, Pierre-André <[EMAIL PROTECTED]>: >[...] > 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...
Mhh yeah, have you read the Coding Guidelines? They are over at tools.openoffice.org and give some tips about hacking. Furthermore there is the inofficial Ximian's Hacker's Guide (http://ooo.ximian.com) but that won't probably fit your needs. > > It would really be nice to have such a tutorial. It would give more confidence > for new developers. +1 > 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. +1 > > I could take some time to write the documentation I just described for Linux > if you like. Any contributions are appreciated very much, I just don't know if it can make it in the Developer's Guide, because that is a Sun official document and you probably have to at least signed the JCA form (a license agreement with Sun). But as about documents that can be put up at the api website I am pretty sure there are no big limitations to this. Also if you want to start such a project, it's good to add a task or enhancement report at IssueZilla for it and you can upload the revisions of the document there. Those are my thoughts, thanks. -- Best Regards Christian Junker --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
