[libreoffice-design] Re: [Libreoffice-qa] Bug Submission Assistant : status report
Hi, Even though Aleksandar completed his contract work ( http://99designs.com/web-design/contests/bug-submission-web-form-design-wanted-libreoffice-95945 ) as shown at http://wiki.documentfoundation.org/Bug_Submission_Assistant_-_ToDo#Web_design he kindly agreed to discuss on this list about your request. I'll let him speak for himself now :-) Welcome Aleksandar. On 09/16/2011 11:33 PM, Loic Dachary wrote: On 09/16/2011 11:11 PM, Christoph Noack wrote: Rationale: Bugs aren't funny, but for our website it would help to have a visual anchor that tells the user bug this way, please. Furthermore, a hiqh quality graphic lets us appear more professional ... although it is still the same product (note: users tend to be more forgiving, if the product - the BSA - is a pleasure to use) Request: Create an graphic that can be used to refer to bug reporting for a) in the product LibreOffice, b) the bug submitting assistant, c) the feedback selection website. If the detail level is mid and the file type vector (SVG), then we can adapt and tweak it afterwards. Visual Design Hints: * Primary: Consider the Tango Desktop Icons styleguides * Secondary: Consider the LibreOffice branding guidelines Proposal: I don't have any proposal for a metaphor ... :-\ Examples: * If I remember correctly, Ubuntu uses a black exclamation mark on an orange explosion callout sign. * Bugzilla uses/used: http://www.brightcreative.com/i/projects/bugzilla-lg.gif * I once created a cracked note to symbolize the work in progress when we've worked on the Writer comments feature: http://wiki.services.openoffice.org/wiki/Notes2_Development_Releases Hi, I sent this to see. Let's hope he can make provide something within the next 24h (project deadline). I will not block the completion if he does not. I think your description is very detailed and will allow him to fully understand the idea. Cheers -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org 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
[libreoffice-design] Re: [Libreoffice-qa] Bug Submission Assistant : status report
Hi Aleksandar, Loic, all! Am Samstag, den 17.09.2011, 17:20 +0200 schrieb Loic Dachary: Hi, Even though Aleksandar completed his contract work ( http://99designs.com/web-design/contests/bug-submission-web-form-design-wanted-libreoffice-95945 ) as shown at http://wiki.documentfoundation.org/Bug_Submission_Assistant_-_ToDo#Web_design he kindly agreed to discuss on this list about your request. I'll let him speak for himself now :-) Welcome Aleksandar. Yes, a very warm welcome from my side as well - welcome to LibreOffice! Before I start, I'd like to thank you for providing the BSA artwork and having the patience to listen to our questions and comments concerning the branding stuff. Especially, since we finally need to put everything in one place ... :-) Since Loic CCed the Design Mailing list, let's shed a bit light on that. The LibreOffice Design team consists of volunteers who work on User Experience (e.g. Usability) and Visual Design topics. Personally, I'm more the interaction design guy ... so your support was highly appreciated (thanks to Loic for organizing that). If you want to get in touch with us, here is the still drafty Design Team wiki page - there you'll also find information for subscribing to our mailing list (if you like): http://wiki.documentfoundation.org/Design That's all from my side ... Cheers, Christoph On 09/16/2011 11:33 PM, Loic Dachary wrote: On 09/16/2011 11:11 PM, Christoph Noack wrote: Rationale: Bugs aren't funny, but for our website it would help to have a visual anchor that tells the user bug this way, please. Furthermore, a hiqh quality graphic lets us appear more professional ... although it is still the same product (note: users tend to be more forgiving, if the product - the BSA - is a pleasure to use) Request: Create an graphic that can be used to refer to bug reporting for a) in the product LibreOffice, b) the bug submitting assistant, c) the feedback selection website. If the detail level is mid and the file type vector (SVG), then we can adapt and tweak it afterwards. Visual Design Hints: * Primary: Consider the Tango Desktop Icons styleguides * Secondary: Consider the LibreOffice branding guidelines Proposal: I don't have any proposal for a metaphor ... :-\ Examples: * If I remember correctly, Ubuntu uses a black exclamation mark on an orange explosion callout sign. * Bugzilla uses/used: http://www.brightcreative.com/i/projects/bugzilla-lg.gif * I once created a cracked note to symbolize the work in progress when we've worked on the Writer comments feature: http://wiki.services.openoffice.org/wiki/Notes2_Development_Releases [...] -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org 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
Re: [libreoffice-design] Re: [Libreoffice-qa] Bug Submission Assistant : status report
Hi Loic, all! Am Freitag, den 16.09.2011, 00:07 +0200 schrieb Loic Dachary: Hi, As an additional note - do we get the source code to work on further refinements / changes after the challenge is over? I will provide the deliverables as a layered XCF file and it will be under GPLv3+ as the code. That's great - XCF and SVG files is something we can easily work with (whilst SVG provides a bit more flexibility). * See: My favorite so far ... Oh, See already has made an update - excellent progress and very close of what I had in mind :-) http://wiki.documentfoundation.org/cgi_img_auth.php/7/75/BSAsee01.jpeg [...] * but: * The text BugText does not fit into our branding scheme Has been corrected. The current font decision resides here: http://wiki.documentfoundation.org/Marketing/Branding#Fonts * Furthermore, the textured background for Submit and the header is a bit different to what we use ... if possible, a green on (different) green motif should be used for large areas Already fixed. The motif examples might have helped here... http://wiki.documentfoundation.org/cgi_img_auth.php/7/7b/ROUGH_postcard_PRESENTED.jpg http://wiki.documentfoundation.org/cgi_img_auth.php/b/b3/ScatterInContext_bunch.jpg * the dashed lines do not fit and adds visual noise * the Submit button is something good - red/orange is a warning color (in most countries), e.g. blue would fit better Also fixed, looks very nice and is far better from the usability point-of-view; colors according: http://wiki.documentfoundation.org/Marketing/Branding#Colors Could you please add URLs (as precise as possible) explaining the relevant part of the branding scheme for the text or the required textured background ? I've noticed that they don't have time to research or read more than what is strictly necessary. I don't understand what you say about the dashed lines. Do you mean they don't fit the branding scheme and should be removed ? To be honest, we've never decided on the user of whatever lines ... so there is neither a best practice nor a guidelines. But, dashed lines are something that catch attention - good if that's required, less good if the surrounding elements do have priority (here, the line was just a divider). And for the sake of completeness - the branding page also covers a temporary description of the intended visual design: * Clean: The visual design is straight and clean. Reduced geometric elements are combined to visualize the intended message. * Balanced: The visual design avoids any extremes. For example, neither extreme coloring nor intensive surface shining effects are used. * Friendly: The visual design creates a smooth and joyful environment. For example, rounded corners and the fresh color palette are used. Nik, who puts lots of work into the motif and the website, added some time ago use lots of white. I communicated your remarks to see anyway but it would help for me to know more ;-) By the way, I don't know whether it is possible, but maybe the designers could add a large problem icon based on the Tango icons set (default in LibO)? http://tango.freedesktop.org/Tango_Icon_Theme_Guidelines Could you please phrase this a self contained request ? I'm sure see will agree to it if time allows. Okay, but only if it fits, since I don't have any clue how binding the 99designs work description is. Rationale: Bugs aren't funny, but for our website it would help to have a visual anchor that tells the user bug this way, please. Furthermore, a hiqh quality graphic lets us appear more professional ... although it is still the same product (note: users tend to be more forgiving, if the product - the BSA - is a pleasure to use) Request: Create an graphic that can be used to refer to bug reporting for a) in the product LibreOffice, b) the bug submitting assistant, c) the feedback selection website. If the detail level is mid and the file type vector (SVG), then we can adapt and tweak it afterwards. Visual Design Hints: * Primary: Consider the Tango Desktop Icons styleguides * Secondary: Consider the LibreOffice branding guidelines Proposal: I don't have any proposal for a metaphor ... :-\ Examples: * If I remember correctly, Ubuntu uses a black exclamation mark on an orange explosion callout sign. * Bugzilla uses/used: http://www.brightcreative.com/i/projects/bugzilla-lg.gif * I once created a cracked note to symbolize the work in progress when we've worked on the Writer comments feature: http://wiki.services.openoffice.org/wiki/Notes2_Development_Releases
[libreoffice-design] Re: [Libreoffice-qa] Bug Submission Assistant : status report
On 09/16/2011 11:11 PM, Christoph Noack wrote: Rationale: Bugs aren't funny, but for our website it would help to have a visual anchor that tells the user bug this way, please. Furthermore, a hiqh quality graphic lets us appear more professional ... although it is still the same product (note: users tend to be more forgiving, if the product - the BSA - is a pleasure to use) Request: Create an graphic that can be used to refer to bug reporting for a) in the product LibreOffice, b) the bug submitting assistant, c) the feedback selection website. If the detail level is mid and the file type vector (SVG), then we can adapt and tweak it afterwards. Visual Design Hints: * Primary: Consider the Tango Desktop Icons styleguides * Secondary: Consider the LibreOffice branding guidelines Proposal: I don't have any proposal for a metaphor ... :-\ Examples: * If I remember correctly, Ubuntu uses a black exclamation mark on an orange explosion callout sign. * Bugzilla uses/used: http://www.brightcreative.com/i/projects/bugzilla-lg.gif * I once created a cracked note to symbolize the work in progress when we've worked on the Writer comments feature: http://wiki.services.openoffice.org/wiki/Notes2_Development_Releases Hi, I sent this to see. Let's hope he can make provide something within the next 24h (project deadline). I will not block the completion if he does not. I think your description is very detailed and will allow him to fully understand the idea. Cheers -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org 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
Re: [libreoffice-design] Re: [Libreoffice-qa] Bug Submission Assistant : status report
Hi all, just wanted to share my first ideas regarding the icon for the bug-report pages. It's simply a LibreOffice icon with red borders and a little warning sign containing an exclamation mark. Its not based on the tango guidelines or the LO color-palette, only a draft. SVG: http://ubuntuone.com/0E5q1IRdAY6Zox59CCZp4N Hope this somehow helps the design process Greetings Alex Am 16.09.2011 23:11, schrieb Christoph Noack: Hi Loic, all! Am Freitag, den 16.09.2011, 00:07 +0200 schrieb Loic Dachary: Hi, As an additional note - do we get the source code to work on further refinements / changes after the challenge is over? I will provide the deliverables as a layered XCF file and it will be under GPLv3+ as the code. That's great - XCF and SVG files is something we can easily work with (whilst SVG provides a bit more flexibility). * See: My favorite so far ... Oh, See already has made an update - excellent progress and very close of what I had in mind :-) http://wiki.documentfoundation.org/cgi_img_auth.php/7/75/BSAsee01.jpeg [...] * but: * The text BugText does not fit into our branding scheme Has been corrected. The current font decision resides here: http://wiki.documentfoundation.org/Marketing/Branding#Fonts * Furthermore, the textured background for Submit and the header is a bit different to what we use ... if possible, a green on (different) green motif should be used for large areas Already fixed. The motif examples might have helped here... http://wiki.documentfoundation.org/cgi_img_auth.php/7/7b/ROUGH_postcard_PRESENTED.jpg http://wiki.documentfoundation.org/cgi_img_auth.php/b/b3/ScatterInContext_bunch.jpg * the dashed lines do not fit and adds visual noise * the Submit button is something good - red/orange is a warning color (in most countries), e.g. blue would fit better Also fixed, looks very nice and is far better from the usability point-of-view; colors according: http://wiki.documentfoundation.org/Marketing/Branding#Colors Could you please add URLs (as precise as possible) explaining the relevant part of the branding scheme for the text or the required textured background ? I've noticed that they don't have time to research or read more than what is strictly necessary. I don't understand what you say about the dashed lines. Do you mean they don't fit the branding scheme and should be removed ? To be honest, we've never decided on the user of whatever lines ... so there is neither a best practice nor a guidelines. But, dashed lines are something that catch attention - good if that's required, less good if the surrounding elements do have priority (here, the line was just a divider). And for the sake of completeness - the branding page also covers a temporary description of the intended visual design: * Clean: The visual design is straight and clean. Reduced geometric elements are combined to visualize the intended message. * Balanced: The visual design avoids any extremes. For example, neither extreme coloring nor intensive surface shining effects are used. * Friendly: The visual design creates a smooth and joyful environment. For example, rounded corners and the fresh color palette are used. Nik, who puts lots of work into the motif and the website, added some time ago use lots of white. I communicated your remarks to see anyway but it would help for me to know more ;-) By the way, I don't know whether it is possible, but maybe the designers could add a large problem icon based on the Tango icons set (default in LibO)? http://tango.freedesktop.org/Tango_Icon_Theme_Guidelines Could you please phrase this a self contained request ? I'm sure see will agree to it if time allows. Okay, but only if it fits, since I don't have any clue how binding the 99designs work description is. Rationale: Bugs aren't funny, but for our website it would help to have a visual anchor that tells the user bug this way, please. Furthermore, a hiqh quality graphic lets us appear more professional ... although it is still the same product (note: users tend to be more forgiving, if the product - the BSA - is a pleasure to use) Request: Create an graphic that can be used to refer to bug reporting for a) in the product LibreOffice, b) the bug submitting assistant, c) the feedback selection website. If the detail level is mid and the file type vector (SVG), then we can adapt and tweak it afterwards. Visual Design Hints: * Primary: Consider the Tango Desktop Icons styleguides * Secondary: Consider the LibreOffice branding guidelines Proposal: I don't have any proposal for a metaphor ... :-\ Examples:
[libreoffice-design] Re: [Libreoffice-qa] Bug Submission Assistant : status report
Hi Lic, hi all! CCing the Design Team ... please reply to the QA list. Am Donnerstag, den 15.09.2011, 22:12 +0200 schrieb Loic Dachary: Hi, Today was mostly about the web design. There are three candidates designs (http://99designs.com/web-design/contests/bug-submission-web-form-design-wanted-libreoffice-95945) that I just uploaded at http://wiki.documentfoundation.org/Bug_Submission_Assistant_-_ToDo#Deliverables I would really like your input. If nothing else a simple I better like this URL will suffice. Oh, thanks for the links ... we should really avoid to let the BSA look much better than LibreOffice itself ;-) To be serious, I'd like to judge on the basis of our branding guidelines and some usability findings - that makes choosing the right one a bit easier. When commenting on these proposals, please bear in mind that a) it's a contest and only one designer will be paid, b) the deadline of the contest is in 48 hours, c) the prize is USD$495 (thanks to Free Software Foundation France for funding this work). Very cool - I wasn't aware that FSF is so kind to fund this :-) As an additional note - do we get the source code to work on further refinements / changes after the challenge is over? When interacting with the web designers, I heavily relied on Christoph Noack interaction schematics ( http://wiki.documentfoundation.org/cgi_img_auth.php/d/df/BSAinteraction.png ) with one noticeable difference : I stick to a one page application instead of implementing the Next button allowing for multi pages, because the multi page interaction has not been defined yet. Hope to do that today ... at least a bit. My goal is to integrate the web design that will be available in two days so that the minimal version of the bug submission assistant is better looking than it currently is. My dream is that the web design produced will be useful for the evolution of the bug submission assistant. Okay, so here is what I think - basically each of the designs needs tweaking to really fit, but one fits more than the other: * Hitron: While quite similar to the LibreOffice UI, the texts are hard to read (accessibility) and the tree views are incorrect (usability). Furthermore, it doesn't really fit to the branding guidelines stating e.g. Friendly: The visual design creates a smooth and joyful environment. For example, rounded corners and the fresh color palette are used.. * Iva: I think it fits a bit better from the visual POV, although I've found some usability issues. For example, the captions (the green bubbles) might look like buttons for some - the closed design does not refer to the input fields. Furthermore, the grouping via the gray background is sometimes a bit strange (doesn't include that should be grouped). Furthermore, the information element (orange) in the lower right is too far away from the name/password input ... people might not notice it. * See: My favorite so far ... * because: * everything is grouped in a box ... easy to understand what belongs together * the understandability of the sequence steps (left side) is much better than in the last iteration * but: * The text BugText does not fit into our branding scheme * Furthermore, the textured background for Submit and the header is a bit different to what we use ... if possible, a green on (different) green motif should be used for large areas * the dashed lines do not fit and adds visual noise * the Submit button is something good - red/orange is a warning color (in most countries), e.g. blue would fit better We should See whether some of these things could be resolved ... then we get close to perfectionism ;-) By the way, I don't know whether it is possible, but maybe the designers could add a large problem icon based on the Tango icons set (default in LibO)? http://tango.freedesktop.org/Tango_Icon_Theme_Guidelines [...] Hope this helped a bit ... Cheers, Christoph -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org 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
