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


On Sat, Nov 6, 2010 at 10:58 PM, RGB ES <rgb.mldc@gmail.com> wrote:
I was thinking on something similar. If it were possible to completely
separate "core" from UI it would be great. For example, someone who
knows Qt but nothing about GTK will be able to create a gui for MeeGo
without messing with core elements. Or someone else will be able to
build a gui for small monitors. Or another person will be able to
build something for "power users" in which you can only see style
stuff while just another person will contribute a kids & format
painter lovers interface.
To go on with this idea, I think it will be interesting to make the
core "toolkit independent" (i.e., pure C or C++, without GTK or any
stuff like that), so it will be possible to integrate LibO on any
platform "just" (yes, I know it is not easy, that's why I used
quotes... ;) ) by writing a proper UI.

LibO already has different frontends for GTK+, QT, native Win32 and
native Mac in the vcl module and they are independent as any change in
the code of one of those toolkits doesn't affect the others. It could
be done better for sure, but what you are mentioning is already
possible.

-- 
Jesús Corrius <jesus@softcatala.org>
Document Foundation founding member
Skype: jcorrius | Twitter: @jcorrius

--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***

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.