Hello Joesf,
The Simple API was a fork from ODFDOM by IBM, that was donated afterward
together with Oracles (former Sun) ODFDOM to Apache. Simple API was later
abandoned by them when they canceled as well their work on Apache
OpenOffice.
I am not too happy with some design decisions they made (e.g. their list
handling) and there is some duplicated code from ODFDOM still part of the
Simple API.
As OpenSource is all about fixing what is itching you, to me is important
to improve the source code generation from parts of ODFDOM (esp. styling
and consistent design for a high-level user API) so Simple API would become
fully redundant
But as long this is not further progressed, there is no real alternative to
the Simple API and I would not deprecate the Simple API. Still I personally
only use ODFDOM [image: {#emotions_dlg.wink}]
>From September on I will start again working on mapping the ODF XML grammar
into the Tinkerpop Graph, simplifying the graph and generating source code
from it.
Aside from this, there is this quite annoying task on my desk to merge my
collaboration feature branch into the ODF Toolkit.
As it comes to collaboration with multiple participants exchanging
documents is as if software developers would collaborate their work by
zipping source code repositories and dispatching those - which actually
exactly what the world is doing in the past decades for office documents.
I am currently in Warschau and talking with CKSource to suggest they should
consider using this document change concept to load ODF changes (as a list
in JSON) into their new CKEditor 5. As soon there is a prototype I will
post it to the list and keep you informed.
Cheers,
Svante
PS:
<commercial>As I am a freelancer and consultant for ODF, you may contact me
any time, e.g. via LinkedIn, to assist you in your work, as others already
have done already. We might even think about generated run-time model
different to Java for mobile and browser.. ;-)</commercial>
Am Do., 23. Aug. 2018 um 15:40 Uhr schrieb Josef Härtl (JIRA) <
[email protected]>:
> Josef Härtl created ODFTOOLKIT-476:
> --------------------------------------
>
> Summary: Infinite-Loop and NPE adding a row to a table with
> merged cells
> Key: ODFTOOLKIT-476
> URL: https://issues.apache.org/jira/browse/ODFTOOLKIT-476
> Project: ODF Toolkit
> Issue Type: Bug
> Components: simple api
> Affects Versions: 0.6.2-incubating
> Reporter: Josef Härtl
> Attachments: EndlessLoop.java, EndlessLoop.odt, NPE.java, NPE.odt
>
> We're facing problems when adding a row (using odf-simple) to a table that
> contains merged cells.
>
> More specifially, the problem occurs as soon there is a horizontally
> merged cell that is followed by a vertically merged one. Then, inserting
> another row at the end of the table results in an infinite loop.
>
> An example would be (the A's and B's should be joined)
>
>
> || ||A||A||B|| || ||
> | | | |B| | |
>
> The problem stops if there is another (un-merged) row below the vertical
> merged cells.
>
> Adding a column in between A and B, however, results in a
> NullPointerException.
>
>
>
>
>
> I've created and attached 2 minimal samples illustrating the problem. Just
> place the odt into resources and run.
>
>
>
> Some words on our environment:
> * Java 8 (for now)
> * odfdom version 0.8.11 and simple-odf 0.8.2, also known as
> "0.6.2-incubating".
>
> I will gladly provide more input if required.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)
>
