To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=64717





------- Additional comments from [EMAIL PROTECTED] Wed May 17 05:32:10 -0700 
2006 -------
ab wrote:
> b) Copying / Storing all informations to the user layer isnt realy a bug.
> Not in my implementation nor in your patch. No discussion about it .-)

Andreas - Honestly! ;-) - the corollary of not cutting & pasting -code- all over
the place is that -duplicating state- is *really* bad programmatic practice. I
find it hard to understand that you don't see that as a design flaw.

The archetypal problem with duplicating state is keeping it consistent: consider
the (outlandish & perhaps unimaginable) case that OO.o 2.0.0's accelerator
configuration scheme was not perfect. This would mean that people would want to
configure it: that would then freeze a snapshot of that (imperfect) setup for
all time [ until a 'version upgrade' threw all their changes away ;-].

ie. this design screws us (as maintainers) wrt. changing & improving keybindings
over time & migrating them to better & more intuitive patterns wholesale.

Inasmuch that it does that [ which unless I'm mistake it does ], it's a
-serious- problem, certainly for my customers [ who tend to complain about many
of the accelerators not being where they expect them ;-].

If we can move to a design that doesn't have this flaw, while at the same time
removing all the rampant & unmaintainable state duplication in the source tree
this is a good step.

Currently we duplicate the complete state per-language [source-tree] and
per-user-that-changed-anything - we want to move this to ~no duplicated state in
the source tree, and no duplicated state per-user: surely that is a good thing?

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to