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 need.
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 way?
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 premature.
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.
Cheers,
Greg