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

List:       kde-devel
Subject:    Re: K abiword port
From:       Mosfet <mosfet () jorsm ! com>
Date:       1999-05-24 16:14:01
[Download RAW message or body]

Assuming we use the same beta release cycle we used for KDE1.0, perhaps we can
simply sync KOffice1.0 with the KDE2.0 release. Then when we provide the
KDE2 betas KOffice would be distributed along with it just like kdenetwork and
kdeutils.

From using KOffice on and off for quite awhile, I think it would be stable
enough to make a 1.0 release along with KDE2.0. Of course, the KOffice
developers would have to agree with it and I am sure there are tons of stuff
they still want to implement, but it certainly seems stable and has enough
features for a 1.0 by then...

On Sun, 23 May 1999, Alex Zepeda wrote:
> On Mon, 24 May 1999, Matthias Ettrich wrote:
> 
> > Offtopic: With abiword and gnumeric there are now two overhyped gtk
> > projects that both have a far superior counterpart in the KDE office
> > suite. We are sort of unbeatable when it comes to coding, our
> > marketing however, seems to need vastly improvements :-(
> 
> Perhaps once things stop moving, we could do a binary release of the
> KOffice bits.  I know I'm itching to do one for FreeBSD anyways, but
> things seem to be moving so quicly (trying to keep track of Qt and the
> constantly changing mico versions, etc, etc).
> 
> Once we can do a preview binary release (something hailed as being more
> important than a daily snapshot) somewhat like M3 was for Mozilla, and
> give it a snazzy nickname (KO#1? Knock Out 1? ;) ), we can also hype this
> to all the appropiate announcment groups. Perhaps we should aim for mid
> summer.
> 
> I know for a fact that there's a growing market for a decent WP that works
> with FreeBSD.  ApplixWare and WordPerfect both run, but Applix has been
> dicking around for over a year about a native port.
> 
> - alex
--
Daniel M. Duley - Unix developer & sys admin.
mosfet@kde.org
mosfet@jorsm.com

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