Hello Alexandro, The difference is that if you separate all that, then anyone has the freedom of making their own UI (e.g. QT, GTK, Multitouch, etc.)
If it's not separated, then everything has to be constantly ported or shared for new versions. Cheers! Jaime On Fri, Mar 4, 2011 at 12:16, Alexandro Colorado <[email protected]> wrote: > On Thu, Mar 3, 2011 at 7:52 PM, Chaosun <[email protected]> wrote: > > > If you going to get rid of all that, what is the difference of just making > an Android native office suite and borrow the code whenever seen fit. Don't > you think? > > > Well, I had a quite long chat with tml_ regarding the porting to Android > > issue. The truth is that we are planning to have a try. However the > workload > > is tremendous due to the loss of UI. Also to fit the platform, we need a > > complete redesign on UE. > > > > The possible works would be: > > > > 1. Get rid of all the UI related modules such as vcl, sfx2, framework and > > corresponding services etc. > > 2. A engine like LibreOffice, no UI, only provides APIs for further > > development. > > 3. Create a UI for multitouch devices > > Just name a few. no one is a easy work. Also, I'd like to hear from you. > > Please do advice! > > > > > > > Regards > > Chao > > -- > > Unsubscribe instructions: E-mail to [email protected] > > Archive: http://listarchives.documentfoundation.org/www/discuss/ > > *** All posts to this list are publicly archived for eternity *** > > > > > > > -- > *Alexandro Colorado* > *OpenOffice.org* Español > http://es.openoffice.org > > -- > Unsubscribe instructions: E-mail to [email protected] > Archive: http://listarchives.documentfoundation.org/www/discuss/ > *** All posts to this list are publicly archived for eternity *** > -- Unsubscribe instructions: E-mail to [email protected] Archive: http://listarchives.documentfoundation.org/www/discuss/ *** All posts to this list are publicly archived for eternity ***
