Hi,
and kde user would have gtk widget when using LO ?
Why not ? There are so many gtk-applications running fine in KDE.
IMHO (not an KDE-user so didn't check it), the l+f will be just
like Qt.
Why would you consider that kde and gtk are the same 'platform' and
Mac and Windows are not from a UI perspective ?
I'm not just looking at the UI only, but the whole operating system.
To be more correct, replace "kde" by "qt".
On *nix, we've got a pretty clean separation between operating system
(kernel+userland tools), display system (wg. X11 or DirectFB, etc),
widget toolkits (qt, gtk, wxwin, ...) and (optional) user desktop
environments (gnome, kde, xfce, ...). OTOH, Windows doesn't have that
clean separation - it's pretty much one big bundle. (MacOSX is somewhere
in the middle).
The really fine thing on *nix is that it's completely up to the
individual application which widget toolkit to choose, and applications
normally dont depend on specific desktop environments (well, mostly ;-o).
My idea was, consolidating to one crossplatform widget toolkit for
*nix as the first step, which should be pretty easy. Later also
consolidate the other platforms (not sure how complex that would be).
By the way: anybody working on porting the gtk or qt vcl to win32 or mac ?
cu
--
Mit freundlichen Grüßen / Kind regards
Enrico Weigelt
VNC - Virtual Network Consult GmbH
Head Of Development
Pariser Platz 4a, D-10117 Berlin
Tel.: +49 (30) 3464615-20
Fax: +49 (30) 3464615-59
enrico.weigelt@vnc.biz; www.vnc.de
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.