To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=58159
------- Additional comments from [EMAIL PROTECTED] Fri Nov 25 12:55:10 -0800 2005 ------- Terminology is OK in English, but may produce difficulties in translations. E.g. in German, my knee-jerk translation for both "plot" and "chart" would be "Diagramm". I.e. we'd end up with a terminology like 1) Chart background (plus chart floor for 3D) 2) Chart 3) Chart window Hmm... it's not *that* bad. It's actually better than what we have right now, so we should note this down as a fallback consensus if future discussion isn't conclusive. "Chart window" is definitely good. People know that a window is a container for stuff and decorations and handles, just a wrapper around the really interesting stuff, and that's exactly the characteristics of area #3. Even better, this frees up the "background" terminology for area #1. **************** I'm still a bit unhappy about #2. Actually I'd like it best if it simply went away. It doesn't contribute anything to the UI: it doesn't have a background color (that's alreay provided by #1 resp #3), it doesn't give relevant resize handles (those of #3 already implicitly move those of #2 with them), it isn't even visible unless clicked (which may then confuse the user: "I clicked a free space on the chart window, why does this area #2 intercept my click?"). I'm not sure whether scripts want to access it. Or if they even *can* access it. However, if it's a programmers-only subobject, terminology can be chosen using an entirely different mindset. E.g. it could be called a "frame" (programmers are used to things being invisible, even if terminology suggests visibility). Or "data hull" (i.e. the "hull" around all the "data" subobjects of Chart). Anyway. The more I think about it, the more I feel comfortable with eliminating #2 from the GUI. Making it unclickable, having tab order skip it, and generally making it unselectable and GUI-unenumerable, that should do the trick. Maybe Chart programmers will even want to eliminate it from the internal data structures. That would probably be much more work initially, but more maintainable in the long run. HTH, Jo --------------------------------------------------------------------- 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]
