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


On 11/20/2010 2:30 AM, Ron Faile wrote:
>NoOP is right, I wrote the quoted text. Your explanation is well
>noted and I can see the reasoning behind it. The sooner we can change
>the interface and feel of LibreOffice then the better, as I for one
>don't want such a Oracle aligning feature as version numbers staring
>me in the face every time I start up my non-proprietary office suite
>
>On 11/20/10, NoOp <glgxg@sbcglobal.net> wrote:
>On 11/19/2010 06:22 PM, Michel Gagnon wrote:
>> Le 2010-11-19 19:35, NoOp a écrit :
>>> On 11/19/2010 03:26 PM, Sean White wrote:
>>>> As a concerned user, if LibreOffice is meant a independent office
>>>> project
>>>> derived from the OpenOffice code then why do we still use their version >>>> numbering system. Wouldn't it be better to start from 1 to reinforce in
>>>> peoples minds that we are a separate project.

Take a look at the UI improvements page, http://wiki.documentfoundation.org/Development/Default_UI_Improvements

I just uploaded a file (item 11) with some ideas that might set LibO apart. Namely a new menu structure. Would be interested in your comments.

Ron


--
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.