Hi there,
I am new here, so please be nice to me. I am trying to get my feet wet with the programmatic 
creation of ODT text documents (after having used Open/LibreOffice in the past). So, first of all, 
which version should I be using? I am intending to use the for production level code. There seems 
to be:
 - 0.8.8 (this one still has the Simple API it seems...
 - 0.9.0-RC1 (...which has the aforementioned deprecated)
 - 1.0.0-beta 
I guess, I should avoid using the Simple API, right? I should be using the ODFDOM API directly? So, 
is 0.9.0-RC1 stable enough?
I started using the publicly hosted java docs here: https://odftoolkit.org/api/odfdom/index.html. 
What version are they for? They are telling me the OdfTextDocument has been deprecated in favour of 
"org.odftoolkit.simple.TextDocument in Simple API", but then again that has been deprecated, right?
Assuming 0.9.0 is the way to go, are there any good tutorials out there for creation of 
TextDocuments with the ODFDOM API.
Sorry for my newbie questions. I hope to be productive and more useful soon.
Thank you,
Malte.
-- 
To unsubscribe e-mail to: dev+unsubscribe@odftoolkit.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.odftoolkit.org/dev/
Privacy Policy: https://www.documentfoundation.org/privacy
Context
- [dev] Which Version and API to Use · Malte Stien
 
   
 
  Privacy Policy |
  
Impressum (Legal Info) |
  
Copyright information: Unless otherwise specified, all text and images
  on this website are licensed under the
  
Creative Commons Attribution-Share Alike 3.0 License.
  This does not include the source code of LibreOffice, which is
  licensed under the Mozilla Public License (
MPLv2).
  "LibreOffice" and "The Document Foundation" are
  registered trademarks of their corresponding registered owners or are
  in actual use as trademarks in one or more countries. Their respective
  logos and icons are also subject to international copyright laws. Use
  thereof is explained in our 
trademark policy.