Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing
|Summary:||Modernize Help look & feel|
|Component:||ui||Assignee:||AOO issues mailing list <issues>|
|Status:||ACCEPTED ---||QA Contact:|
|Priority:||P3||CC:||frank.thomas.peters, issues, mseidel|
|Version:||OOo 3.3 RC8|
|Target Milestone:||AOO Later|
|Issue Type:||ENHANCEMENT||Latest Confirmation in:||---|
Description aqualung2010 2010-12-23 01:20:13 UTC
System font in Windows 7 is Segoe UI. W7 GUI style guide provides for thin borders around frames in Help windows and no "3 D" shadowing. In OOo, Help font is Helvetica and borders around frames are "3 D" shadowed, giving Help a "legacy" look and feel.
Comment 1 Uwe Fischer 2011-01-03 11:53:52 UTC
There is more to this enhancement request than just filing an issue ;-) Please have a look at the Doc team's dashboard at http://wiki.services.openoffice.org/wiki/Documentation/Dashboard Possibly also discuss this on one of the mailing lists, e.g. the documentation authors list email@example.com or the user experience list firstname.lastname@example.org or email@example.com Currently the Help Viewer is still limited to HTML 3.2 standard. This needs to be improved for a very long time now.
Comment 2 Uwe Fischer 2011-01-03 11:56:25 UTC
Comment 3 aqualung2010 2011-01-04 07:04:32 UTC
To: "ufi" I first mentioned this issue on the OpenOffice user forum but was told that developers do not read the forum so I came here to make a report. Sorry if I did not follow proper protocol, I went out of my way to search the database first and read the instructions. My purpose in coming here was to alert developers to this particular concern. If you are already aware of it and agree that modernization is desirable, then so much the better. Thank you for replying and please keep up the good work.
Comment 4 Uwe Fischer 2011-01-04 08:10:23 UTC
@aqualung2010: An issue is the right method to get enhancements started. Of course developers are aware that the Help Viewer needs many improvements, but without an issue no coding will start. On the other hand, there are hundreds or even thousands of enhancement requests and only few resources to work on them. So more effort is needed to get things done.
Comment 5 aqualung2010 2011-01-04 16:21:23 UTC
Dear Mr. Fischer, Forgive me if the following comment does not belong here, and I will have absolutely no hard feelings if you delete. Seems to me, you are saying that it isn't enough to file an issue, if you want an enhancement to make it into code you have to fight for it by being a pest on various mailing list and in various discussions. In English, this is known as "the squeaky wheel gets the grease". There are a number of problems with this. For one, I notice that my other issue (116212) was actually first raised here more than four and a half years ago... and still is not fixed. This suggests to me that OpenOffice on the whole is underfunded and therefore understaffed. Pushing an enhancement from the outside then is likely to become an exercise in frustration and aggravation. The solution would be to fix the underlying problem, namely to beef up resources; but I don't know how realistic a prospect that is.
Comment 6 Uwe Fischer 2011-01-05 07:29:43 UTC
As this issue contains some general remarks, allow me to add one very general comment, too: Open Source code has the advantage that everyone can start to fix bugs and enhance features. This does not necessarily mean to write code by yourself, or to be a pest to others. It means that there is a much bigger chance to get things done if you succeed in elating many others, convincing them that this one problem is worth some efforts, etc. The more people agree that this is something that should be done, the more possible it is that work will really start. There is still no guarantee, but I think you know what I mean. And no, there are no programmers sitting around and waiting for any issues to be submitted so that they can finally start coding. If this issue is to be fixed it necessarily means that other issues must wait to get fixed. Issues can be "low hanging fruits" that can be fixed easily (even that needs some time for developers and QA and others), or they must be fixed (think about security issues), or there must be "a business case" (someone will pay for the efforts), or you can find someone who wants to improve own programming skills and start this project because it will look good in the CV, or other reasons.