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

Without wishing to rain on anyone's parade or do unsavoury things to 
campfires, I think there's been a lot of great design thought here in 
isolation of a good, hard, implementation agnostic think about enumerating the 
real use cases. 

When I say use cases, I don't mean anything to do with how to build it, what 
looks pretty or cool but what REAL user goals need meeting, what tasks need 
doing and which actors are involved. Then perhaps a check with users of Word 
processors generally (i.e. not posters on this forum and not necessarily LibO 
users only) about how well the proposed use cases would address any actual 

Of course, some may prefer an agile approach, with epics, and user stories and 
acceptance tests, &c. but I don't think LibO development is organised that 

Until we've got some concrete, well written use cases validated with users, 
the batting back and forth of designs and insiders' preferences seems a little 

Incidentally, I don't think the use cases should be constrained by what the 
current navigator's capabilities are.

I'm happy to get the ball rolling on the use case goals, to start with but 
I'll wait to see what everyone thinks first.



Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.