To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=112141
------- Additional comments from [email protected] Fri Jul 16 13:24:42 +0000 2010 ------- @tanstaffl cornouws is absolutely right: further comments on the importance of this issue are not helpful. @ALL We needn't emotionalize this any further (actually not it all). We've complained more than adequately - to the point of incredibility. Repeatedly venting anger and even hostility reduces the serious discussion of this issue to a cheap chat-room. Please refrain from swearing, name-calling or expressing violence towards developers. Do that somewhere else, if you must, but NOT HERE. We must move forward on this issue. What does that mean? It means this: 1) This issue has been set from Priority 3 (P3) to Priority 2 (P2). What that does, among other things, is REQUIRING that this issue be resolved for the next release. Not fixing it is unacceptable. "Issues with this priority must be fixed before the target release (see Target milestone), which usually is the next major release, and should be dealt with as soon as possible. Not fixing them for the target release is not acceptable." (See http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority for more info on Priorities.) @corounws: You mentioned that you "do not see a big change that this will be finalised before 3.3.0." Is this still the case when this has P2? If so, why? 2) @corounws: What needs to be done to assign this issue a "Target Milestone"? It is indeed troubling that this has not been set for this issue! And what does "Assigned to: requirements (requirements)" mean? This also does not sound promising. We would expect to see a username or an issue owner here and not, as in this case, a plural noun. Please advise! 2) cornouws' comment (Thu Jul 15 20:55:40 +0000 2010) has evidently been helpful to some of us (i.e., working together to create a temporary solution), but it is probably beyond the skills of the discussion participants (including my own) to integrate new icons into the OOo source code and recompile or even to create an extension (which is also no piece of cake!). What has been offered so far (i.e. colored shell file icons that can be integrated into the user's OS) is modestly helpful. That is exemplary of the kind "moving forward" we need to do, so thanks to prowlerxpla, jakobkramer and ticotexas for these! [Honorable mention goes to kongnan (°±°)] !!! And at the time of writing morobus just submitted a new soffice.exe !!! That's the spirit! 3) Until this issue is resolved, use OOo 3.2.0 or Go-OO 3.2.0. unless there is some fix or feature in 3.2.1 that is worth sacrificing the colored icons. syzygy successfully deleted 3.2.1 and installed Go-OO 3.2. to return to the old colored icons. If you do that, let us know by posting here! (I had read the release notes and saw the new icons before doing an update. Since there are no fixes, security patches or enhancements in 3.2.1 that are important for me, I decided not to update from 3.2.0 to 3.2.1. I then deleted OOo 3.2.0 and tried Go-OO 3.2.0., which uses only a bit more than half as much memory than OOo does on Win XP. ----- Another contribution just came in from vvzh, making this entire comment seem nearly superfluous... mb --------------------------------------------------------------------- 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]
