Home of The Tiny Guide to

OpenOffice Project Renaissance Designs’s Project Renaissance, a bid to reinvent the application’s user interface with no preconceptions as restraint, is currently in the design phase. Slashdot reported on it in OpenOffice UI Design Proposals Published, and the proposals are collected in the OOo wiki here.

Johannes Eva and Jaron Baron have created two that I quite like, although I haven’t had the opportunity to look at all submissions yet.

4 Responses to “OpenOffice Project Renaissance Designs”

  1. The Wizard of Oz Says:
    August 29th, 2009 at 6:36 pm

    A great on line petition started to stop this unnecessary Renaissance project

    is you agree, you can sign here:

    once Renaissance is stopped, developers can concentrate their efforts in solving issues (things we really need)

  2. Benjamin Horst Says:
    September 10th, 2009 at 10:41 pm

    I don’t agree with the petition, and I do think the Renaissance project is necessary for the future of OpenOffice. Software has to evolve and user interfaces improve over time. I do not want OOo to mirror Microsoft’s Office UI, but I do want the project to experiment, test, and improve its own.

  3. The Wizard of Oz Says:
    September 15th, 2009 at 8:39 pm

    OORenaissance is not an improvement, but a step in the past of usability

    I guess you use very few features of OpenOffice (just write a letter or relation or something else)

    Only an user not using massively OpenOffice can say what are you saying. Heavy user has memorized menus, has learned shortcuts, he isvery productive

    now, in order to mimic Ribbon (to not say other), developers think to reinvent the whell (or better, the Ribbon). RESULTS?

    Heavy, learned, productive user is constrained to relearn in a very short time and meanwhile his productivity has dramatically decreased

    Oh, yes, a very big score fort a project, in fact, Ribbonification of OpenOffice only makes happy Micro$oft that can see a dangerous rival lose users forced to relearn things already learned

  4. M Dudley Says:
    September 28th, 2009 at 6:19 pm

    Personally, I think that anything that hurts Microsoft has to be a good thing, but I do agree with Benjamin on this.

    Software has to evolve and rise to the challenge of finding out what people want and how they want to use tools. This has to be more easily achieved using an open source project, rather than a corporate project.

    There will always be changes, the key is to help us see changes that help us – not the MS strategy