Re: [api-dev] OpenOffice.org port to Qt
_Replacing_ VCL with Qt would be a very huge project. Doing a Qt Plugin for VCL, similar like we have one for GNOME, should be possible with a reasonable amount of time. The GSL mailing list is a better place for such questions/discussions. Malte. Alexandro Colorado wrote, On 07/07/09 09:47: Hi just want to throw this out since I got approached by the KDE people at the Gran Canarias Desktop summit (guadec + akademy http://www.grancanariadesktopsummit.org/) about the factuality of migrating OOo to the Qt toolkit. Although the chances were slim I did feel obligated to upstream the question ad look at this as both a challenge and a request. Technically speaking is this possible at all, and how many effort would it take. I know that OOo has been doing some refactoring of some components to enhance the performance and also make the code easier to interact with. However is the visual layer abstracted from the application logic enough to consider replacing the toolkit? They ideas they presented is that avoiding the maintenance of our own toolkit we can open the door to free some resources to take care of more important things. Also that the Qt toolkit is a more modern and with better performance toolkit than what they have seen in OOo. Qt is also very portable as it has been ported to several architectures even mobile devices. So before knocking this idea, I would like to maybe learn more about how OOo native toolkit works within OOo. - To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
Re: [api-dev] OpenOffice.org port to Qt
Hi, Malte Timmermann wrote: _Replacing_ VCL with Qt would be a very huge project. Agreed. One that we at some point will want to begin however - not necessarily to Qt of course. Actually this point is coming up all the time. Everybody (me included) would like to get rid of vcl as most of the toolkit. Just what exactly to use instead is unclear. Also clear is that at least for a time both would have to live together as this is not something to be done in one big step. Doing a Qt Plugin for VCL, similar like we have one for GNOME, should be possible with a reasonable amount of time. Incidentally we have one already. And the updated version for KDE4 is in the works. Kind regards, pl -- Sanity is just a bad excuse for a lack of imagination. -- Author unknown Registered Office: Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten Commercial register of the Local Court of Munich: HRB 161028 Managing Directors: Thomas Schröder, Wolfgang Engels, Wolf Frenkel Chairman of the Supervisory Board: Martin Häring - To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
[api-dev] OpenOffice.org port to Qt
Hi just want to throw this out since I got approached by the KDE people at the Gran Canarias Desktop summit (guadec + akademy http://www.grancanariadesktopsummit.org/) about the factuality of migrating OOo to the Qt toolkit. Although the chances were slim I did feel obligated to upstream the question ad look at this as both a challenge and a request. Technically speaking is this possible at all, and how many effort would it take. I know that OOo has been doing some refactoring of some components to enhance the performance and also make the code easier to interact with. However is the visual layer abstracted from the application logic enough to consider replacing the toolkit? They ideas they presented is that avoiding the maintenance of our own toolkit we can open the door to free some resources to take care of more important things. Also that the Qt toolkit is a more modern and with better performance toolkit than what they have seen in OOo. Qt is also very portable as it has been ported to several architectures even mobile devices. So before knocking this idea, I would like to maybe learn more about how OOo native toolkit works within OOo. -- Alexandro Colorado OpenOffice.org Espantilde;ol IM: j...@jabber.org - To unsubscribe, e-mail: dev-unsubscr...@api.openoffice.org For additional commands, e-mail: dev-h...@api.openoffice.org
