Re: Re: [libreoffice-design] The future of design suggestions
Am Montag, 20. Juni 2011, 22:43:26 schrieb Bernhard Dippold: We should try to keep as many resources as possible in the LibreOffice/TDF infrastructure. [...] With our Visual Elements page http://wiki.documentfoundation.org/Visual_Elements we already use images linked to other wiki pages than the image files, so this might be a starting point... +1 Best, Björn -- Voluntary Open Source Usability: http://www.OpenUsability.org Commercial Open Source Usability: http://www.OpenSource-Usability-Labs.com -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org 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
Re: Re: [libreoffice-design] Survey - Current Issues
Dear Bjoren and all, The survey system looks great and friendly! However, I'm a bit confused. Is the aim of this survey primarily to test the survey-system or is the major aim to come up with some initial directions for future design? Thanks for the work and additional appreciation for clarifying its goals. Best, dror -- View this message in context: http://nabble.documentfoundation.org/Survey-Current-Issues-tp3084300p3092805.html Sent from the Design mailing list archive at Nabble.com. -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org 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
[libreoffice-design] Re: The future of design suggestions
Hi Bjorn, I do share your concerns, but would like to present a somewhat even more radical position. As I understand it, you advocate for an evidence-based decision-making for design questions. Anyone can come up with his/her design alternative. Eventually all the alternatives will be tested by actual users, in one survey or another, and may the most popular alternative win! I would like to ask why not have a preliminary set of surveys, to identify the needs and likes of actual users and of potential users, and then come up with design alternatives that address these likes and needs. What do you say? dror -- View this message in context: http://nabble.documentfoundation.org/The-future-of-design-suggestions-tp3085560p3092867.html Sent from the Design mailing list archive at Nabble.com. -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org 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
Re: [libreoffice-design] The future of design suggestions
Hi All. On 22/06/11 9:09 AM, Bernhard Dippold wrote: Hi Björn, all Björn Balazs schrieb: Hi all, I am a little unsatisfied with the amount of individual threads going into the direction of: We need a new interface for LibreOffice - and it needs to look linke this For me they show the high interest of our team members in the UI design area. But you're totally right: We need to integrate the different proposals in general directions for UI improvements. This is a Free Software Project. As a design team, we will not need to convince ourselves about this need to change the GUI (we all agree on that), we will need to convince the people actually doing (and financing) it - the developers and the companies paying them. Even if a large group of developers are paid by companies, there is another group coding on their own. What we need are at least a few developers interested in UI design. If we can convince them, our ideas will become code and finally find their way into the product. But if we can convince more than just a few developers by showing the needs our users to the entire community, this would get more developers interested and involved... [... we should never argue about personal opinions ...] So, how can we make this more productive? Ideas are good, visualisations are even better. So let us find a way to not comment on these, but to collect them with the goal of easy comparision with eachother. A gallary of ideas and visualisations of the future LibO. A gallery is great - but I'd rather think of a gallery of single UI improvements (with visualizations from different mockups) than of a gallery of the different mockups. If several mockups contain sidepanes, similar context menus or context sensitive tools, these should be combined as features, based on user data (already existing or new to be reached for) and expert statements, decided on their positive/negative impacts and recommended for implementation based on a specification containing all the necessary information for the developers. We should then try to extract the dimensions these ideas differ on. Knowing these we can then again use user-centric methodologies to have the users decide about what they like. Of course user feedback is the most important quality measurement for UI modifications. But based on the user's likings it stays to us to decide which feature should be implemented in which way: There are more than design aspects to consider (marketing, present user base, documentation, coding effort, interdependency with other areas of the product ...), users can't have in mind. With this data we will have much less trouble to convince the code-sponsors to go into a certain direction. That's true - real user data are a very good argument to convince marketing and development ... So - the main point I am argueing for is a gallery of interface ideas. Easy to compare and on one spot. What do you think about this? +1 I'd start with a gallery of the already presented mockups (perhaps with a short description of their features) and then go through this gallery and collect the single features for another gallery of UI elements / positions / ideas as a basic tool for our overall concept. I don't know if a gallery or a table would fit our needs better. While a gallery is easier to create and maintain, a table allows to add more fields than just one caption below each image. With a gallery we probably need to go to the gallery entry's wiki pages to get the necessary information. A table (containing mid-size images in one of their columns) would allow to add the features contained in the mockup, the rationale for each specific design element (if existing) and many more information. On the other hand it's harder to write than just to the gallery. Best regards Bernhard I also think it is important to be able to provide the whole package, complete solution, (all details) in an overall structured way and not haphazard. For a developer to pick it up and commit many hours all questions need to be answered in a specification. i.e. how will every menu in every LO component function. Discussion here is centered on writer and trying to conserve height but calc is mentioned as preferring wide to tall space. May be a framework can be created, like a table, with the various LO components (writer, calc, etc.) across and the various UI elements down. When all the cells are filled and how the elements work, inter-reaction is seen and agreement is made then developers can be considered. The developers may then need to refine this due to code or function needs (you can't do that because... but may be like this) Then when all in agreement the coding can be implemented. steve -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive:
Re: Re: [libreoffice-design] Survey - Current Issues
Hello everyone, Sorry for not being online for a while. I have just done the survey. ~ King Duck On Tue, Jun 21, 2011 at 4:26 PM, drorlev dror.s...@gmail.com wrote: Dear Bjoren and all, The survey system looks great and friendly! However, I'm a bit confused. Is the aim of this survey primarily to test the survey-system or is the major aim to come up with some initial directions for future design? Thanks for the work and additional appreciation for clarifying its goals. Best, dror -- View this message in context: http://nabble.documentfoundation.org/Survey-Current-Issues-tp3084300p3092805.html Sent from the Design mailing list archive at Nabble.com. -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org 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 -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org 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
Re: [libreoffice-design] New Design and experience
Xi, I can't see your mockup. Could you upload it somewhere else? ~ Maggie On Mon, Jun 13, 2011 at 10:19 PM, Xi Embalsado newecrea...@hotmail.comwrote: Hey! Can you evaluate my mock-up? http://cid-b8d257bea212e4aa.office.live.com/self.aspx/Public%20Stuff/LibreOffice%20Mock%20Up.odg Please comment. -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org 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 -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org 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
