Hi Tor,
On Thu, 2011-05-05 at 23:59 -0600, Tor Lillqvist wrote:
Or 2) Adapt the LibreOffice build mechanism to work with
cross-compilation.
..
gbuild work hopefully should make it easier. Interestingly, enabling
cross-compilation will benefit LO builds for Windows hugely...
Right - so, as one precursor we really want to help with moving
~everything to gnumake so we only have to do the heavy lifting in one
place. Of course, that has a great knock-on effect of improving our
build speed, and as a side-effect having a great synergy with our
end-goal of moving to cross-compiling the Windows builds.
What is interesting in this discussion here and earlier on the
"discuss" list is that nobody seems to ponder how the user interface
of (a subset of) LibreOffice running on a tablet/touch device should
look and work. Surely designing that is equally hard as overcoming
technical build hurdles or restructuring what gets built.
This is of course an excellent point :-) However, it is clear that with
lots of complementary, baby-steps in the right direction, we will get
somewhere useful in the end.
Or do you really expect people to want to use the normal LibreOffice
GUI with hierarchical menus and other stuff from a desktop style GUI
on a touch device?
Not in the end-game; but as a demo to generate lots of interest, and
attract more developers to help re-work the chrome: I think this would
be a wonderful first-step.
ATB,
Michael.
--
michael.meeks@novell.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.