Hi John, On 11/8/05, John Hardy <[EMAIL PROTECTED]> wrote: > > How did you know that it could get fixed in a few minutes if you > > haven't read the code (or you are not going to)? Just curious. > > > > > > > It is such a simple problem that I don't have to read the code: The code > that displays the font size in the Toolbar window is either limited to > ZERO decimal places by mistake (a simple-to-fix formatting issue), or it > displays the integer portion only by mistake (a simple-to-fix formatting > issue), or something like that. This cannot possibly be hard to fix. Can > you explain why you think it might take longer than a few minutes? It > would be instructive to me. It may have taken a long time to write the > code in the first place, but fixing a number-formatting issue in > existing code should be a quick fix for the person who wrote it and > knows where to look.
But you are just speculating that this is the case. Even if what you say here is true, which it isn't based on the comments that follow from other developers, find the right location in the code base will take at least more than just a few minutes. Even if you are quite familar with the code, pinpointing exactly where the problem lies is moderately time-consuming (maybe upwards of 10-30 minutes?) There are issues in the past that I thought were a simple fix, before I started working on fixing them. Sometimes, even if the bug seems so simple that you think an experienced developer can fix it in a few minutes, it may turn out to be quite complicated. I can give you this issue http://qa.openoffice.org/issues/show_bug.cgi?id=25368 as an example of appearing simple, but not so simple to fix. > I have done some limited Pascal programming, but nothing anywhere near > the scale of OO. I have downloaded the source code and tried to find a > few things, but it seems complicated and convoluted (to the > inexperienced, such as myself). I was quite inexperienced with C++ when I started messing with the code some years ago, and I had no experience working with a codebase as huge as OO.o's. I gained experience mostly by trying to fix bugs. So, my point was, sometime you'll be surprised how much you can handle, even if you don't have much prior experience dealing with such a huge codebase. Of course it will take a long time to fix a simple bug at first, but you'll do better as you do more. > But those two issues remain unfixed. Sorry, but I don't understand why. > It may seem like I am *demanding* that someone fix the problems, but it > is more an expression of my amazement that something so simple has NOT > been fixed. You may not have been demanding, but use of CAPS in a mailing list may be (sometimes incorrectly) taken as a demand. Also, to me this issue seems like a low priority bug because it doesn't eat or alter your document, nor does it crash the applicaton. It's just a simple annoyance. I'm sure it is high priority for you, but when there are literally thousands of bugs to get squashed, a method must be developed to properly prioritize them. Kohei -- Kohei Yoshida OpenOffice.org Calc contributor http://kohei.us/ooo/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
