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

List:       koffice
Subject:    RE: Is kword ready ?
From:       "Pohlmann, Frank" <fpohlmann () ipo ! att ! com>
Date:       1999-09-01 9:17:38
[Download RAW message or body]


Hi folks,

maybe this is a very naive idea: given that there are so many KOffice apps,
it might be an idea to bundle SOME of the stable applications in a kind of
mini KOffice (e.g. KWord, KPresenter, KSpread, KIllustrator and KImage).

 Then make this version available as binaries, add an installation procedure
(!) and get on with development.

I used to run KOffice until I moved to England for a couple of months and it
ran just fine!!!! 

So don't get discouraged, you are doing great work and once your
Swiss-army-knife among Office suites is entering beta, you will be singing a
happier tune:-)

Frank

"Meanwhile, on Frank's cloud..."


> -----Original Message-----
> From: Sébastien Major [mailto:sebastie@cybercable.fr]
> Sent: Wednesday, September 01, 1999 1:22 AM
> To: koffice@max.tat.physik.uni-tuebingen.de; koffice@kde.org;
> linux-admin@vger.rutgers.edu
> Subject: Is kword ready ?
> 
> 
> Hi,
> 
> I just tested the "new" kde suite and specialy kword.
> When some team develop, some asumption are made like
> good compiling and graphic interface.
> If you plan to install koffice suite and if you suppose
> all the remaining is like kword, forget it.
> 
> The biggest trouble is probably with save and restore process.
> Yes, when a file is saved in kwd format (why didn't we call it 
> xml format ? :-( ), we are not sure to retrieve it at all.
> 
> Many bugs pertain, many options menu are not there but interfaced,
> surprising...
> 
> mico support is certainly as good thing as Microsoft's point of vue of
> competitor with kword, but let's back to "read the fucking manual,"
> please.
> 
> First, if a part of the project is more advanced than an other,
> fill holes instead of continuing with different programs : kimage,
> for example.
> 
> If the program is not good, don't let sources so easily to be obtain
> like
> it is ! Is Xfree access of sources badly managed ? Is XFree base 
> significaly changed since its base ?
> 
> I don't want to be mean but just signify that it's going too fast and
> nearly nobody will soon have a precise idea of dealing with
> some or some bug. Linux 2.0 has been completly finished before
> really taking a look at 2.2.
> 
> I spent those 3 days in compiling and testing. My first test 
> project was
> to try the look and feel of the entierly koffice suite.
> After many hours of compiling and correcting for it goes to the end of
> 'make all ; make check', I was raised to the fact that I would only be
> able to test one: arbitrarly kword.
> 
> KDE is highly slower than the previous version, well known 
> stable 1.1.1.
> Kword crash with no more message than the name of the function call or
> 'Aborted' or 'segmentation fault',...
> 
> I'm not sure that it would have been more constructive to detail
> all bugs I found instead of writing this e-mail, I just needed
> that as a therapy !:-)
> 
> Best regards.
> 


["Pohlmann, Frank.vcf" (application/octet-stream)]

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