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

I dare to say my concern and use case.

I'm working with OpenOffice for a few years with two types of documents:
test specifications and test protocols. The first is a long-long-long
document of hierarchical structure. In my current spec there are  27
chapters of test case list  and from 3 to 13 test cases in each chapter.

The protocol is spreadsheet, listing all that.  

The test specification is subject to often revisions and updates, and every
time I have to check if the protocol is up-to-date with spec. It's important
for me to see all the contents tree expanded, I don't want to have to expand
each of 27 chapters manually every time.

So, when I didn't find "expand all tree" in LibreOffice, I had to go back to
OpenOffice :( (sob).

I don't want to think that my problem is "too corporative for FOSS
software", I think it's not that hard to give a user an option to preserve
old contents tree behavior or a button(s) "expand all" - "collapse all"
(FreeMind-style), or both. Of course, not every user has 27 chapters of from
3 to 13 test cases, but his document may be a book or what.

Thanks in advance :)

View this message in context:
Sent from the Design mailing list archive at

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.