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

List:       koffice
Subject:    Re: users book about KOffice
From:       Raphael Langerhorst <raphael-langerhorst () gmx ! at>
Date:       2004-01-29 12:12:10
Message-ID: 200401291312.10265.raphael-langerhorst () gmx ! at
[Download RAW message or body]

Hello!

I quite agree with John that a book can be written parallel to the development 
of the application. Especially if the people writing the book are involved in 
the development. Then it would be possible to publish the book very soon 
after the new version of the application appears - and then you have a book 
covering the current version.

And the more mature an application gets the less it changes in its basic form. 
So the book would be usable for two years or more - depending on how much 
user visible changes are made to the app.

Of course if you wait until the app gets out and THEN write a book, it would 
be of less use.

A reason for me to have a (new) book about KOffice would be the file format 
move to OOo - which means great compatibility - and the fact that KOffice is 
ready for real use and has only here and there a rough edge. So if the book 
is started now it will probably be ready with the next version of KOffice 
which then already has native OOo file format (it is planned for KPresenter 
<-> OOo Impress, KWord <-> OOo Writer and KSpread <-> OOo Calc). Besides a 
lot of other improvements of course.


greetings,
Raphael


On Wednesday 28 January 2004 19:39, John Mark Walker wrote:
> On Wed, 28 Jan 2004, Eugene Nine wrote:
> > How long is the current time from writeing a book to the publish time,
> > IIRC it used to be measured in months.  With Koffice and Kde changes are
> > happening fairly quick, wouldn't it be difficult to keep a book up to
> > date with the current kde/koffice?
> >
> > Eugene Nine
>
> It depends on which point of view is used for the book. From a user's
> point of view, there will probably be quite a few changes between now and
> KOffice 2.0. If the book were to be a user's guide, then I would want it
> to cover new features for 2.0, or whatever the next rev will be called.
>
> From the developer's point of view, unless KParts undergoes a radical
> change in the next couple of years, then I don't see too much changing. My
> understanding was that the API's were pretty solid by now. Please correct
> me if that is indeed wrong.
>
> Either way, as long as you can publish the book soon after the software
> release, it should be good for at least a couple of years. After all, how
> long did it take to release 1.3 after releasing 1.2? And how much of the
> user or developer experience has actually changed in that time?
>
> -JM
____________________________________
koffice mailing list
koffice@mail.kde.org
To unsubscribe please visit:
https://mail.kde.org/mailman/listinfo/koffice
[prev in list] [next in list] [prev in thread] [next in thread]