Both Qt and OOo have Java bindings. OOo allows writing extensions and Qt allows building UI using Java. Looks like the two are made for each other from a Java developer's standpoint. Exposing Qt as the standard UI toolkit for OOo should encourage 3rd party developers to extend the functionality of OOo. Some of those extensions could eventually become part of the core OOo distribution. Today's UNO APIs are a total mess. So this may be a chance to finally fix the community problems as well.
Just my 2 cents. Yegor On Fri, Jan 16, 2009 at 2:47 PM, Thorsten Behrens <[email protected]> wrote: > Éric Bischoff wrote: >> Nokia recently relicensed the Qt library under a triple license : GPL, LGPL, >> and commercial. >> >> Qt is cute, modern, C++, easy to program with, and multiplatform. Wouldn't it >> be the ideal replacement for VCL, now that LGPL is an option? >> > Hi Eric, > > why are you following up to my (unrelated) lib unloading mail?! > > Anyway, besides concerns others have voiced regarding text layout & > accessibility, changing the underlying toolkit of OOo in the way it > is proposed here is the most far-reaching change to the code base I > can conceive of, short of changing the implementation language from > c++ to managed c++ or somesuch. > > So that's nothing we should do on a whim - quite the contrary, we > should never ever again bind ourselves against the implementation of > one specific toolkit, but rather code against an abstract interface. > > Along that lines, see the work that's happening around dialog > auto-layouting and the awt toolkit > (http://marketing.openoffice.org/ooocon2008/programme/friday_1470.pdf) > > Of course, having qt then provide _one_ implementation of that > toolkit interface is quite the plan (as having a gtk, Win32 & Cocoa > one). And the license change definitely helps there. > > Cheers, > > -- Thorsten > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
