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

List:       kde-commits
Subject:    RE: koffice/lib/kofficecore
From:       David Faure <David.Faure () cramersystems ! com>
Date:       2000-03-07 9:36:34
[Download RAW message or body]

> > Hmm, right (of course - since kchart can have no child 
> > parts it made sense there). 
> > 
> > Should I revert this fix and simply make kspread always 
> > save in a KTar ?
> > 
> > -> we could define that hasToWriteMultiPart() should NOT depend
> > on whether child objects are there or not, but ONLY on the 
> > application... Makes sense to me.
> > 
> > What do you think ?
> > 
> > (NOTE : this change doesn't prevent loading old files saved 
> > in raw XML, by the way. The loading code still detects that.)
> 
>    I don't think there were too many charts saved this way. The main
> usage of kchart is in kspread, but there it is a special 
> relationship. I would leave it as it is. 

Hmm, right (again).

I guess the question is rather: 
is there any KOffice app (or will there be?) that does NOT have
child documents, NEVER, and which would then prefer saving into
an XML file directly instead of an XML file inside a tar store.
(Having a tar file with always one file inside seems rather stupid).

Hmm, I can't see any right now. kchart was probably the only one,
and as you say, it's very seldom used standalone.

Do I miss another one ?

--
David Faure
faure@kde.org - KDE developer
david@mandrakesoft.com - Mandrake
david.faure@cramersystems.com - Cramer Systems

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