> On Tue, 2010-01-26 at 14:24 +0200, K S wrote: >> I would like to develop for OpenOffice too. I have already done the first >> stage - get the source and build. What is next?
On 26/01/2010 21:17, Fabio A. Miranda wrote: > Go to: qa.openoffice.org and start by fixing as much bugs as possible. in principle, that would be a good general direction. but not all bugs are alike; some are easy to fix, even for someone who does not know much about the code base, while others are of the sort that requires someone with lots of experience with the code to be able to really fix it without introducing lots of nasty new problems (almost anything having to do with writer's redlining falls into that category). only experience will tell them apart. so i would suggest to decide what general area you would be interested in working on (calc, writer, impress, VCL, UNO, ...), and subscribe to the relevant development mailing list. there you can inquire what open tasks a new developer could solve without too much frustration. also, read some chapters in the developer guide: http://wiki.services.openoffice.org/wiki/Documentation/DevGuide the first chapters describe the UNO component model, and some aspects of general OOo architecture. whatever you do, you will likely come in contact with UNO code, so it is important to know what all those uno::Reference and queryInterface thingies do. one thing that we are definitely lacking in many areas is regression tests. writing complex test cases that drive the OOo applications from java via UNO API is not too difficult, but unfortunately does not seem to be as popular an activity as one would like. regards, michael -- PCMCIA - People Can't Memorize Computer Industry Acronyms --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
