On Wed, 2005-05-11 at 11:16 -0700, Jack Mullaney wrote: > 1) Your doc sorely needs a 'getting started' kind of > section wherein you say what the parts of the app are, > what a person can do with each part, how they might > interact, and gives the definition of all top level > technical terms. -- The help looks good, but it looks > like its written for people who already know how it > works, as a sort of documentation. Some good top > level work needs to be added. -- I'd like to work on > that. >
I completely agree with that observation. Mainly a good documentation introducing to the technical stuff, giving an overview of all modules, filetypes, directory structure, architecture, etc. The learning curve for a new developer on OOo (my case) today is very long. It's particularly demotivating to see most of the code uncommented and/or commented in german. I think that a valuable effort to make the learning curve for the newbies smaller and to make the OOo as a whole more maintainable is a refactoring process. Maybe I'm saying obvious things and everybody already have the same feeling, but I have not seen much effort on these issues since I started listening to the mailing lists and browsing the OOo website and code. We need software engineers, not hackers. PS: I loved the "Coding Guidelines" document. PS2: I'm sorry if a said anything stupid. As I already mentioned, I'm just a newbie. Best regards, Daniel d'Andrada T. de Carvalho --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
