To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=77257
------- Additional comments from [EMAIL PROTECTED] Wed Oct 8 12:07:17 +0000 2008 ------- > Now OOo will automatically take over the MSO file extensions in case no > application at all is registered for them and it will automatically not > take them over in case there is an application registered. > > I think that makes a lot of sense. I agree - to a point. And if you will read this Feature Request, you will see that this is exactly how I had envisioned this working - with the addition that, since OOo is CAPABLE of doing this evaluation, AND because it is capable of making the necessary registry changes, then it only makes sense that this functionality should be made available in such a way as to be EASILY MANAGED. Meaning, RECORD the CURRENT registry settings PRIOR to making the changes, and provide a simple mechanism for MANAGING these registry settings. > Removing configuration options where the application is able > to handle that itself reasonably is basically a good idea. I agree... > Especially if data is available that proofs that the configuration > setting is misunderstood by many users. Again I agree... > I also understand that "expert" users might want to configure > this by themselves differently. This is a valid request, though > IMHO not one with a high priority. I disagree - VEHEMENTLY. While I would agree if the functionality were not ALREADY THERE, removing EXISTING functionality - in essence, DUMBING DOWN an application - just because the WAY it is currently implemented is confusing to SOME users, is totally RIDICULOUS. > Perhaps someone can provide this as an extension? That would be perfectly acceptable, but the main problem that I have with this is THE FUNCTIONALITY ALREADY EXISTS. Why should someone else have to reinvent the wheel? Just to be clear... I don't have a problem with the fact that the ability to choose the file associations at install time was removed. I have a problem with the fact that NO MECHANISM WAS PROVIDED TO TAKE THE PLACE OF THIS LOSS OF FUNCTIONALITY. At a minimum, the devs THEMSELVES - specifically, the one(s) that arbitrarily and unilaterally decided to remove this CRITICAL functionality should do it NOW. IMMEDIATELY. Am I pissed? VERY. Why? BECAUSE WHOEVER DID THIS JUST CAUSED OUR BOSS TO DECIDE TO SWITCH TO MSO IF THIS IS NOT FIXED PRIOR TO OUR UPGRADING TO VERSION 3.0. So, if this isn't fixed, OOo just lost an 80+ installed base, just because some dev somewhere decided they knew better than the people actually USING OOo. --------------------------------------------------------------------- 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]
