--Boundary-00=_8AW5BMf5GuNqwiV Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello Martin! On Monday 10 January 2005 16:39, Martin Ellis wrote: > Hello, > > Speaking of recruitment and documentation.... > > I was going to check out a copy of KWord (although this problem > doesn't seem to be specific to KWord), but I can't find any > documentation that says which modules from koffice I might want. Normally KOffice is built as a whole. Still, it is of course possible to skip components, like Boudewijn pointed out in his reply. If you want to do some development (which is very welcome), then you most likely want to get the source from CVS head (see further down). > > From http://www.koffice.org/developer/, I can follow the link to > General developer info, then to the generic KDE CVS instructions, > which of course don't help here. ... I just looked at http://www.koffice.org/developer/ The only pages that describe getting and compiling KOffice in particular is on http://wiki.kdenews.org ... which is currently down. You can find good information on how to obtain latest versions here: http://developer.kde.org/source/anoncvs.html I've written a small patch that adds the particular links to the general developers information page. If anyone with www cvs access could commit this please? > > Then there's a link to "Compiling KOffice Step By Step," but it's > broken. :o( See above, http://wiki.kdenews.org is down at the moment :( > > The Doxygen API also appears to be several months out of date, > while the main KDE API was updated yesterday (and has a nicer > Doxygen template). Presumably thats an automated task. > Could koffice steal the infrastructure for that? Automating this would be great, I vote for that ;) > > I know everyone has a lot to do, but I wonder if developers > wouldn't be a bit more forthcoming if it was a little easier to > dabble in the code...? Please keep pointing out what's wrong or should be improved to help new developers to get in. Such hints are very appreciated. KOffice in general can have a steep learning curve. If you start to investigate the sourcecode I would suggest to start in koffice/lib/, this holds the basic and shared infrastructure between the components and thus you can learn how the KOffice components integrate into each other. Also... (I planned to do this for many months but ... unfortunately don't have much time...) if you want to keep a short diary about what you learned, I guess this would also be helpful to other new developers. This could even end up in writing a developer book for KOffice, which I have losely in my mind as well as soon as I have the time left. And I guess this shouldn't be done before KOffice 2.0, but would be very interesting to do while KOffice 2.0 is being developed. Please keep asking if you need more information / help. > > Regards > Martin > _______________________________________________ > koffice-devel mailing list > koffice-devel@kde.org > https://mail.kde.org/mailman/listinfo/koffice-devel -- Raphael Langerhorst, JID: raphael@jabber.pilgerer.de G System, The Evolving Universe - http://www.g-system.at --Boundary-00=_8AW5BMf5GuNqwiV Content-Type: text/x-diff; charset="iso-8859-1"; name="koffice_www_sourcecode.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="koffice_www_sourcecode.patch" Index: index.php =================================================================== RCS file: /home/kde/www/areas/koffice/developer/generalinfo/index.php,v retrieving revision 1.9 diff -u -p -r1.9 index.php --- index.php 26 Jun 2004 14:16:54 -0000 1.9 +++ index.php 12 Jan 2005 17:27:06 -0000 @@ -13,6 +13,15 @@

This section provides information about developing in KDE, viewed from KOffice's point of view.

+

Getting the latest KOffice Sources

+ +

Patches