Michel sorry I did not read that email thread, will take a look at it.
Charles To keep this simple and without shame of repeating myself: >> The developers cannot implement a complete redesign all at once. Therefore >> you need to push changes one by one. Little by little. In order to do this >> you need to write specification for each of the UI feature. What has been >> written so far here and on Mirek's blog needs to be much, much more >> detailed. >> > Oh My God, I purposed that we make a ROAD MAP. A thing that is a STEP BY STEP instruction on how to START implantation of a new UI. parden my CAPTIZED words im am getting tired of people telling me that we can not do this UI Stuff in on blow. I KNOW THAT. what I was asking is, was that link [1], a LINK to the devs "Road Map". and if it was, I said that it looks like all they have planed for the next year is bug fixes, code freeze(which they do not say what code they will be working on), and l10n improvements(which they do not explain what that means.) once we understand where the dev team is planing on heading, I perpose that we stear them onto our road. and just to remind you that we can not do this in one blow, just encase you forgot. so until then I along with many others think that we should continue our talks about Citrus, deside on some things, and start on making some specifications. because who the knows there just mite be a dev that finds our specification and says, hay I could do that it mite take me a [this amount of time], ill start this now. we have a lot of devs, all working on many different things. there is no reason that a group of them could not step up and start working on some of this. I had heard some time ago that the devs want to get started on this project. > To complement Charles answer, may I suggest to re-use the wiki pages > created by Christoph Noack to make proposals ? > You can see them in the whiteboard section : > https://wiki.**documentfoundation.org/Design/**Whiteboard<https://wiki.documentfoundation.org/Design/Whiteboard> thank you for showing me this. that was helpful. And an important point : please create mockups in wireframe. > Otherwise, the theme/aesthetic changes may disturb the UX analysis. [1] [1] http://uxopenofficeorg.**blogspot.com/2010/05/picture-** > is-worth-thousand-words.html<http://uxopenofficeorg.blogspot.com/2010/05/picture-is-worth-thousand-words.html> why wireframe, I know that a lot of UI are made in that but why? > > for example, all ux proposals by Canonical are built with balsamiq : > http://www.markshuttleworth.**com/archives/383<http://www.markshuttleworth.com/archives/383> > http://www.markshuttleworth.**com/archives/333<http://www.markshuttleworth.com/archives/333> [1] http://wiki.documentfoundation.org/ReleasePlan -- Unsubscribe instructions: E-mail to [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/design/ All messages sent to this list will be publicly archived and cannot be deleted
