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



 Yes, some qualitative feedback would be nice ... some hint: don't ask

for the features they miss, ask for what they wanted to do and where
they experienced problems. And, after finishing the interview, I suggest
that you ask what other office productivity suites they use - otherwise
its very hard to compare.


ok thanks for the hint. I know that they use M$ Word or they PDF it, drop
box it to the ipad,  then change it so that it looks good in pages.  but
there are more people to ask, so ill get back to you latter. I will meat
with some of them this Wednesday.

Why this approach? Because normal users always tend to answer they need
certain features, although they never use them ... it might sound
cold-hearted from my side, but here we need to protect them to fiddle
around with their choice :-) I once summarized that for OOo Renaissance:
http://wiki.services.openoffice.org/wiki/Renaissance/FAQ


makes since.


A mockup or a blog post is great to transport an idea - to get interest
by other people and to make sure that those people see the potential.
But for the implementation (which is more than development) you need to
involve a lot of people.


oh I know, I was just wondering whether his post was good enough for a
 specification.
once we make a real specification we can start refining it so that every
one agrees to it.

Besides the explanations in the link above, you'll finally need
accessibility, translation hints, QA details, "edge-cases" behavior,
potential migration issues, ...


what Kind of accessibility, translations as in different languages(e.g.
German). and please explain (QA details, "edge-cases" behavior,)


Back to the topic: A specification (or more relaxed: a whiteboard page)
for a rather complex feature serves as a hub that connects all the
different teams. André and I did a presentation on the LibO conference
explaining exactly that ... and you might be surprised what we need to
make sure that even tiny features work right from the start:

http://wiki.documentfoundation.org/cgi_img_auth.php/e/e6/2011-10-15v3_LibOCon_Non-Hacker-Tasks_Schnabel-Noack.pdf



Here is André's specification proposal:

http://wiki.documentfoundation.org/User:Andreschnabel/Spec_Calc_grid_lines_on_colored_background


thanks for the links.

Andrew, my proposal to you is to pick a smaller feature - maybe
unrelated to Citrus, so that it can be really implemented (maybe an Easy
Hack?). How about doing that together ... with all the people on this
list?


I was just giving an example still do not know what I will start with, but
when I do I will post it here so you guys can review it.

-- 
Unsubscribe instructions: E-mail to design+help@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

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.