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

List:       koffice
Subject:    Re: KOffice objects (fwd)
From:       Simon Hausmann <tronical () gmx ! net>
Date:       1999-04-08 17:12:22
[Download RAW message or body]


On Tue, 6 Apr 1999, Cristian Tibirna wrote:

> 
> ---------- Forwarded message ----------
> Date: Thu, 01 Apr 1999 17:37:09 -0600
> From: Stephan Richter <root@light.mem.ixl.com>
> Reply-To: SRichter@ixl.com
> To: webmaster@kde.org
> Subject: KOffice objects
> 
> To whom it may concern:
> 
>     I just started learning Qt/KDE programming, and I would like to
> develop a "little" application to draw
> organic compounds. These compounds can be saved or exported.
> Part of the idea is, to implement them into KOffice. (I think it would
> be cool to just add an organic compound to a kword document. Since I am
> a chemistry major, I am really interested in such a feature.)
> 
>     Here my question: How does your object model work? What do I have to
> know? Do you have a general KDocumentObject?

You might also have a look at shaman (shaman module in CVS) . Beside some
other stuff it contains a KOffice template. Just run it with shaman and
you'll get a full-featured KOffice Application, similar to Kurt Granroth's
famous KAppTemplate.

Although it's a little bit out-of-date it should still work.
(but be warned: this autoconf/automake stuff there is highly-out-of-date,
meaning it is not supposed to work properly anymore ;) . But with some
little Makefile adaptions it shouldn't be hard to integrate it into an
existing KOffice CVS tree on your local harddisk to make everything
compile/work ) .

Greetings,
 Simon
 
> "Mit vielen Gruessen nach Deutschland",
> 
> stephan
> 
> --
> Stephan Richter
> CBU - student, sys admin; iXL - programmer
> 
> 
> 
> 

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