[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Understanding KWord sources
From:       David Faure <david () mandrakesoft ! com>
Date:       2001-12-07 1:44:32
[Download RAW message or body]

On Friday 07 December 2001 00:04, Klas Kalass wrote:
> Am Donnerstag, 6. Dezember 2001 23:26 schrieb Chris Howells:
> [...]
> > What I'd really like to know is what the "best" way of getting acquainted
> > with the sources of a new program that you want to hack on is. Sure, this
> > will vary between programs, and some will be more complicated than others
> > -- but surely there must be some kind of generic technique that can be
> > applied to all programs to get a better understanding of the sources?
> 
> What I usually do is to start with main() and try to understand how everything
> interacts until the Program is initialized and runs. Then I try to find out how
> things interact when there is user interaction.

Good luck, with that approach and KWord ;-)

In the case of KOffice it's a good idea to have a quick look at the architecture,
i.e. the classes offered by kofficecore.
Then have a look at kword/DESIGN - but there are many details in there now,
so only read the beginning, about the frameset/frames design.
Then you need to dig into the code: identify the main classes.... but with the
current KWord you also need to look at libkotext, that's where most of
the KWord functionality has been moved.

-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://perso.mandrakesoft.com/~david/ , http://www.konqueror.org/
KDE 3.0: Konquering the Desktops

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]