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


On 13/10/10 01:34, Paul A Norman wrote:
I appreciate you doing this, and at the risk of hi-jacking this thread, perhaps we can also request 
that LibO developers put some thought into resolving the long list of counter-intuitive and 
unnecessarily complex ways of going about things that currently plague OOo from text wrapping in 
Impress to watermarks in Writer to the intransigence of bullets to be indented, etc.  These kinds 
of small incremental modifications would, I think, help make LibO more successful.
This would probably warrant a whole forum level of its own, and would
provide a valuable resource for developers. Ironing out a list of such
things from the very beginning woud definetly put the development
process into getting LiBO right uo "there", well ahead.


OOO has in a sense grown incrementally - with the consequence of some
things being added on top of things or grafted in, and is this new
venture going to provide the oppertunity to identify what those things
may be, and set things straight before more layers are added on top?

As a non-programmer, [1] I haven't a clue as to how to influence what happens in a piece of software that I rely on to handle the demands of my postgraduate studies course work as well as for my family's personal use. I +do+ know what works for me as a user however, and my partner is quite vocal in her dissatisfaction/ frustration with a given user operation or UI design issues, so between the two of us there are a number of niggles - not bugs, or at least, not that I can categorically define as such - that make OOo/ LibO feel clunky and awkward at times, & as a generally very user I would like to contribute in some small way.

A top-level forum for users to provide feature/ amendment requests & feedback to developers might be a pretty good thing to make LibO driven by a user base as the (certainly in my case!) grateful beneficiary of robust (i.e. stable, resource efficient & secure) code that stays out of the way of the user, does what the user wants it to do in a way that is either intuitive or self-evident to the user, and offers a clean and meaningful UI.

Not really asking for a lot then, am I?  :-)

Cheers

AG

[1] Altho' I've dabbled & while I find it fascinating by what can be accomplished with basic electronic on/ off switches, I stumble at object oriented programming & classes, etc., and have difficulty expressing concepts in code (Python, Scheme, bash, C, netLOGO - the common denominator is me!

--
To unsubscribe, e-mail to discuss+help@documentfoundation.org
All messages you send to this list will be publicly archived and cannot be deleted.
List archives are available at http://www.documentfoundation.org/lists/discuss/

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.