I'm just a humble end user, and frankly I have little-to-no knowledge of
software development but I was wondering whether there is a clear
separation between frontend and backend with LibreOffice. Such that it
would make it easy to essentially 'slot-in' a replacement GUI.
As I say, I'm not familiar with software development in general much
less the specifics of OOo/LibO but it seems to the that one of the
better ways to encourage innovation is to make it easy for people to
'hack' on individual modules and in particular the GUI (which is in dire
need of modernisation and optimisation in my humble opinion). If
'hacking' a new GUI onto OOo/Lib (a'la IBM Lotus Symphony) at the moment
is non-trivial it will hinder innovation in the form of specialist forks
(which could be very useful for the mother project) and/or experimental
UI (which are clearly intended to showcase innovative ideas to see if
they could or should be merged into the mother project).
I just thought I'd bring this up in light of all the discussion
regarding UI reform. Of course I could be way off base here, and if I am
please do set me straight; if I need some edumacating regarding the
state of OOo/LibO do edumacatify me!
P.S. The quote in my signature was chosen at random, rather appropriate
though don't you think?
"There is no patent. Could you patent the sun?"
-- Dr. Jonas Stalk, on being asked who owned the patent for his polio vaccine
Unsubscribe instructions: Email to firstname.lastname@example.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
*** All posts to this list are publicly archived ***
- [tdf-discuss] Clear separation between frontend and backend? · Lee Hyde
Impressum (Legal Info)
: 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