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

List:       koffice
Subject:    Re: koffice <-> kdebase
From:       Stephan Kulow <coolo () kde ! org>
Date:       1999-06-24 22:34:01
[Download RAW message or body]

Michael Koch wrote:
> 
> Am Don, 24 Jun 1999 schrieb Simon Hausmann:
> > Hi,
> >
> > I'm currently hacking KoHTML II and since it extensively uses the HTML
> > viewing component from Konqueror it needs an installed konqueror
> > (kdebase) in order to compile at least (because of konqueror.idl) .
> >
> > So I wonder whether it is ok for the KOffice package to depend on kdebase
> > (like other packages like kdegraphics or kdenetwork) or whether I should
> > add a copy of konqueror.idl to kohtml?
> >
> > The disadvantage of this would be that I have to keep the copy in kohtml
> > always in sync with the original konqueror.idl in kdebase.
> >
> > Suggestions?
> 
> Why donīt put the html viewing part in kdelibs ? I think that many apps can use
> this. Every OP-app should be able to view HTML without basing on konquerer.
> I know that this bloats kdelibs very much, but I think this is much better the
> depending on kdebase. If a user wants to run koffice without using kde at all
> he only needs to install kdelibs, not kdebase.
> 
> An other option is to create a new module called kdeparts or whatever, that
> includes very often used parts like HTML-viewer, Postscript-viewer for
> printing, editor, etc. BUT all users who want to use kdebase or koffice needs
> to install it. Better put the parts into kdelibs.
> 
No. Kdelibs and kdebase belong together. For example you'll always need
khelpcenter
to make the about boxes work. 

Greetings, Stephan

-- 
KDEDIR is dead, long lives KDEDIRS - the winner takes it all

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