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

List:       koffice-devel
Subject:    Re: KPresenter's DTD
From:       Laurent Montel <lmontel () mandrakesoft ! com>
Date:       2002-04-05 17:03:42
[Download RAW message or body]

Le Thursday 04 April 2002 19:43, Harri Porten a écrit :
> Hi !

Hi,

>
> This is a plea to everybody hacking on KPresenter, especially it's XML
> file format.
>
> If you look at maindoc.xml of a typical .kpr file I notice different types
> of structures: some seem to be "objects", some lists (e.g. PAGENOTES) and
> some simple standalone elements  (e.g. PRESSSPEED).
> I'm completely aware that some of that design is simply due to historic
> reasons, i.e. the notion of a PAGE being not there from the beginning. So
> this is not a complaint about how things are right now.
> I think it would just be nice if in the future everybody extending the DTD
> would try to keep it in sync with KPresenter's logical data model. Notes
> and Titles are elements of a page and could therefore be sub-elements or
> attributes of PAGE. This is much more robust than relying on an indexing
> order build into
>
>  <PAGENOTES>
>   <Note note="" />
>   <Note note="" />
>   <Note note="" />
>   <Note note="" />
>   <Note note="" />
>   <Note note="" />
>   <Note note="" />
>   <Note note="" />
>   <Note note="" />
>   <Note note="" />
> </PAGENOTES>
>
> for example. Would even save space and cpu cycles on saving&loading.
>
> Another good example are .INI-style elements like
>
>  <INFINITLOOP value="0" />
>  <MANUALSWITCH value="1" />
>  <PRESSPEED value="1" />
>  <SHOWPRESENTATIONDURATION value="0" />
>
> For the programmer's and reader's sanity (sorry that I'm so old fashioned
> to read through such files;) an element like
>
> <PRESENTATION inifiniteloop="0" manualswitch="1" pressspeed="1"
> showduration="0">
>
> might be much more easy to handle.
>
> Again, as most of this format has already been released to users it's
> probably too late too change it. 

Perhaps create compatibility for kpresenter 1.1 file, and modify it for 
kpresenter1.2.

As kpresenter 1.2 is not compatible with 1.1 for text object perhaps it's a 
good idea to change it.

Regards.

>And it's also a very subjective thing of
> personal taste. Just wanted to share my thoughts.
>
> Thanks,
>
> Harri.
>
>
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@mail.kde.org
> http://mail.kde.org/mailman/listinfo/koffice-devel

_______________________________________________
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]