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

List:       koffice-devel
Subject:    Re: [RFC] Unified pictures in file format (KWord/KPresenter)
From:       Thomas Zander <zander () planescape ! com>
Date:       2002-06-15 21:18:16
[Download RAW message or body]

On Sat, Jun 15, 2002 at 11:06:45PM +0200, Tomasz Grobelny wrote:
> On sob 15. czerwiec 2002 22:53, Thomas Zander wrote:
> >
> > The common format will not restrict you in putting information in the file.
> > On the contrairy.  You never loose the power of suite A verses Suite B due
> > to the file format. You however do loose the power of Frames (from KWord)
> > when opening the file in OpenOffice.
> >
> But the one who writes still has to make sure that it will look all right in 
> his partners WP. Especially when there is a need for a printout.

Hmm?
The common file is just that, a common file.
The reason for a common file format is that you can open 1 file in N different
WPs without losing information, and the WP will show what it can.

It is explicitly _not_ an export format for 1 package that should open on that
WP exactly like it shows in KWord.

Look at it more like HTML.  One part of the creation is adhering to standards,
and the other is that the browser has to listen to those standards as well.
The good part is that you don't have to care about the different concepts 
(x)html and a WP have, so it will actually be a lot easier then a good html
exporter ever will be.

> > You don't have to think about where the file is going, that is the whole
> > reason for this file type.  It contains all the information you get from
> > the source in a standard format.  The WP is going to decide what to use.
> >
> > Naturally you are right that embedding poses a problem, but one step at a
> > time please :)
> I don't think that it is worth discussing without having one line of code (or 
> do we have?).

No we don't but I still like your opinion on the subject, and I think its
good that people know what will, and what will not be possible with this so
you can make judgements on what will and what won't be worth your time. 

Don't want you to fear work is getting lost :)

Its true that no line of code has been written, but with a project such as
this I want to look at problems before coding and other people often have 
interresting things to say I never thought of ;) 

-- 
Thomas Zander                                           zander@planescape.com
                                                 We are what we pretend to be

[Attachment #3 (application/pgp-signature)]
_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/koffice-devel

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