Am Sat, 10 Apr 2010 14:24:49 -0400 schrieb Terrence Enger <[email protected]>:
> On Fri, 2010-04-09 at 21:19 +0200, Björn Michaelsen wrote: > > Am Fri, 09 Apr 2010 15:12:00 -0400 > > schrieb Terrence Enger <[email protected]>: > > > > > Is there anything that will capture a record of what I did to get > > > into an "interesting" situation? It has happened more than once > > > that I have been trying to reproduced an assertion--but writing > > > down the steps as I go along, so as to produce a good bug > > > report--when I fat-finger something (but I am not sure exactly > > > what) which sends me to a different assertion. > > > > This: > > > > > http://wiki.services.openoffice.org/wiki/User_Experience/OpenOffice.org_User_Feedback_Program > > > > could be of some help to figure out what you fat-fingered. ;) > > However, I fear it is still a bit to "high-level" to be useful in > > general. But it might give you a hint on what just happened in some > > situations. > > > > I have never seen the "help optimize the quality ..." window > presented, and my Tools > Options > OpenOffice.org lacks category > Improvement Program. Output from "configure --help" does not contain > the string "improve". Is there something else I need to do to get > this? Oh, I am so sorry. Yes, there is something that needs to be done to activate it. The feedback program is only activated in official sun builds. Only there there are the files: > ./basis3.2/share/registry/modules/org/openoffice/Office/Jobs/Jobs-oooimprovement.xcu > ./basis3.2/share/registry/modules/org/openoffice/Office/Logging/Logging-oooimprovement.xcu in the installation. In the source tree you will find the files at: > ./extensions/source/oooimprovement/Jobs.xcu > ./extensions/source/oooimprovement/Logging.xcu Im sorry, if I caused confusion. > Actually, I find many things that tend to spread out my attention: new > assertions, new techniques, new (to me) parts of OO. But I think that > I will only be able to contribute usefully if I can get "deeper" > instead of "wider", if you know what I mean. I am in need of general > guidance. Yes, OOo is huge and assertions take you all over the place. It might be useful to just concentrate on set of modules (from one application) and ignore everything else in the beginning. And even then it helps to limit oneself to the lowhanging fruits for starters. BR, Bjoern --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
