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


Lee Hyde wrote:
Greetings All,

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).
By specialist forks, does that mean like a special version for lawyers that does pleading forms, or a special version for screenwriters that has special enhancement for doing scripts, that sort of thing?
--
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.