Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On Tue, Jan 11, 2011 at 4:36 PM, Tom Tasche <tomtasche@gmail.com> wrote:

Hello,

My name is Tom.
I'm the developer of OpenOffice Document Reader for Android.
Hello, it is nice to get you here :)


It's correct that my app is a frontend of JOpenDocument
, but not the one you mean. ;)
This one is the one I'm using:
https://github.com/andiwand/JOpenDocument
It's written by a colleague.
It translates OpenDocuments to HTML
, so we can display this very easily on any device.
I am sorry for the "sweet" mistake I've make.

The next version should be a (simple) ODF editor on Android.

I am thinking of two approaches

1. Use an old brach of OOo - so that the memory footprint - shoul
    be as small as possible using Android NDK.

# Question: what is the oldest OOo version that supports ODF v1.0?

2. Extend the framework JOpenDocument, make it able to edit
    ODF files.

I can't do the coding anymore but if you can wait, I will make it
on Google Summer of Code this year - as a mentor :)


-- 
Best Regards,
Nguyen Hung Vu [aka: NVH] ( in Vietnamese: Nguyễn Vũ Hưng )
vuhung16plus{remove}@gmail.dot.com , YIM: vuhung16 , Skype: vuhung16plus

-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Archive: http://listarchives.documentfoundation.org/www/discuss/
*** All posts to this list are publicly archived for eternity ***

Context


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.