[ODP-dev] What to do next?

[<no...@se...>]

Hi Folks,

I want to list some points that should be done before a new release of =
the
POC code. Anybody can try to solve this problems, so go ahead:

- Some classes have a constructor like __construct($dom) and others
__construct($dom, $root). But I don't think, that the second constructor =
is
always necessary. I believe we can remove the $root part or the $dom =
part
(because a DOMNode object should have the owner DOMDocument in the
ownerDocument attribute). It would be great if somebody could check this =
and
remove unnecessary code in all classes and constructors.

- Most classes use a 'commit'-structure, so thinks will not be written
directly in the document, but will be written on a call of the commit
method. But some are not. The reason for this is ... I don't know. But I
think we should get rid of this commit think in most cases. It doubles =
data
that is held in memory and this is not good. But be aware: A 'nearly =
empty'
AutomaticStyles or MasterStyles class should never be written, because =
it is
against the Open Document Schema. So this need a little bit testing and
reading the OpenDocument documentation and RelaxNG Schemata.

- New classes for other document types. We currently only support text
documents, but we should start with spreadsheets and images right now. =
This
is a new area so a very good point to start from.

I hope some of you will start coding, because Alex and I are currently =
not
able to do a lot on the project.

Thanks,

Norman