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


Hi Enrico,

        Dropping VCL and moving to something else is a gargantuan task. It is
worth discussing -only- if we can do it completely, and the target
toolkit meets all the platform, licensing, maturity and feature
requirements we have. As far as I know as of today, no non-VCL toolkit
does this. A further pre-condition would be having the man-decade of
resource available to finish and test a complete transition to said new
toolkit. Then - finally, if we have that man-decade it's not clear that
this would be a priority - we have plenty of big problems around the
place.

        If you want to do something constructive in this area - then moving
away from VCL's horrific positional widget set is something that starts
to reduce our toolkit API surface, improves our visual look, and allows
more flexibility for native widget choice in the future - checkout:

        http://wiki.documentfoundation.org/Development/WidgetLayout

        And get stuck in ! :-) we have a feature-freeze in ~2 weeks - the more
commonly-used dialogs we can get ported to .ui files before then the
better we'll look for 4.0 :-)

        In the meantime discussing at length things that are not going to
happen serves little useful purpose than creating noise ( it seems to me
).

        Thanks !

                Michael.

-- 
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot


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.