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

List:       koffice-devel
Subject:    Re: KWord to OOWriter filter (also call for developers)
From:       Nicolas Goutte <nicolasg () snafu ! de>
Date:       2004-01-29 20:19:53
Message-ID: 200401292119.53122.nicolasg () snafu ! de
[Download RAW message or body]

On Wednesday 28 January 2004 08:13, Raphael Langerhorst wrote:
> On Monday 26 January 2004 10:36, David Faure wrote:
> > [...]
> > Do you want to do the same kind of work with the OOImpress<->KPresenter
> > converters? Or maybe OOCalc<->KSpread?
> > (I believe the former is easier since so much is in common with the
> > OOWriter<->KWord filters).
>
> I'll have a look at both and then see which one I will work on. For
> timeline: I *might* have more time after 10th of February or so. I think I
> will also work on KSpread a bit in general - bug fixes, small improvements,

Good thanks.

> ...
>
> > BTW it is very possible that kotext will *completely* change once
> > Qt4 is out - or once KPainter is ready, whichever road we take, so I
> > don't see any purpose in documenting that part.
>
> Do you know when QT4 will be out?

The rough plan seems to be that Beta are available in Summer 2004. The problem 
is also to know when KDE 4 will start. Then we will have to see when KOffice 
will start to use Qt4/KDE4.

In any case, the next KOffice release (whatever it would be called 1.4 or 2.0) 
will be on Qt4/KDE4.

>

Have a nice day!

> On Monday 26 January 2004 22:00, Nicolas Goutte wrote:
> > On Monday 26 January 2004 06:32, Raphael Langerhorst wrote:
> > [...]
> >
> > > b) Since I'm still totally new to the KOffice source code I would first
> > > like to read an introduction for developers - and since AFAIK something
> > > of this kind (in the order of 30 to 100 pages) is not available I would
> > > suggest I start with it - a kind of developer cookbook. By writing such
> > > a document as I go on analyzing the code, other (to be) developers
> > > would also benefit (and be more attracted...). And when this has made
> > > some progress then I feel better about working on the source itself :)
> >
> > Yes, please, that would be a great idea and the doucment(s) could be
> > placed in the development pages of KOffice.
> > [...]
> > For the details, there are partially already a few documents of those
> > kind, like for example koffice/kword/HACKING or there are also the
> > interaction between classes in the apidocs in
> > http://www.koffice.org/developer
>
> Such docs (HACKING, DESIGN) are only in KWord as far as I have found out
> yet. Something like this would also be useful for other apps. Depending on
> which filter I will work on I might also write such docs for the app.
>
> For the "cookbook": I'll start with it, as soon as time permits - so
> probably in February. I will "include" all developer docs that are
> currently available and make one big cookbook with them (and of course
> adding lot's of stuff that's not covered by the current docs).
>
> ANYONE having good documentation for developers for KOffice which is not
> accessible through www.koffice.org - please send these to me.
>
> greetings,
> Raphael
>
> > [...]
>
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@mail.kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel

_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]