Posted: Thu Apr 13, 2006 5:11 am Post subject: a question about openoffice/neooffice 2.0 debugging
I try sometimes to use Oo 2.0 mac x11 to see how it work and I was trying to import some of my works to Oo 2.0 to be ready for the neooffice 2.0
Well, I find a *lot* of problems (often bugs), in Oo 2.0 and I'm asking to myself: if I see a bug in Oo 2.0 mac x11, I'll see it in neooffice 2.0 too? Patrick will debug those kind of bugs?
Moving from neooffice to openoffice x11 2.0 is actually a insanity: control's form disappers; there is no way to import queries; dragging 'n drop from calc to base, datas are stored in wrong field (!); rescaling and moving open/save window cause window goes out of screen deleting the piece of the window out of screen; several crash accessing data... et ceterae.
Now, from a user point of view I can not fill bugs for neooffice AND for a real instable openoffice 2.0, I can use only one of those programs and I can report bugs only for one of those. But actually Oo 2.0 is too instable, so I don't understand how, when, and with whom can I cooperate for the debugging.
No flame inside!
f. _________________ eadem sed non eodem modo facere
Then, some of the "bugs" you mention may in fact not be bugs. Since OOo (X11) is not really a "native" Mac OS X application, there are a lot of things that won't work like they do in NeoOffice. For example, OOo doesn't use Mac fonts, so you'll find that there will be differences between document opened with Neo and the same docs opened in OOo (for example, more text will fit on the same page in OOo, sometimes modifiying the way your documents look. Neo alos uspport native drag-and-drop, whereas OOo won't (and yet people keep asking us why we use and/or support NeoOffice instead of OpenOffice.org).
Patrick won't fix bugs in the underlying OpenOffice.org 2.0 code, but anything related to the UI or Mac support (fonts, drag-and-drop, etc.) will be NeoOffice-specific (for the most part).
I would recommend submitting your findings to the mac@porting list. if they are issues unknown, bugs as well. most of these things are part of the oo.o code and not fixed by patrick.
Thanks for the answer. I think I have the last version, where can I read the build number? I do not undertsand how to subscribe mailing list, in the Oo mac x11 site I only see a page with the link to send an empty message to the list.
About the bugs and problems, after more deep test using Oo 2.0 for windows and testing it again with neooffice, I can say those problems and bugs are less I feel in my yesterday's (unlucky) test.
f. _________________ eadem sed non eodem modo facere
Thanks for the answer. I think I have the last version, where can I read the build number? I do not undertsand how to subscribe mailing list, in the Oo mac x11 site I only see a page with the link to send an empty message to the list.
That link does not send an empty message to the list, but rather the list administrator. This will subscribe you to the MacOSX OpenOffice.org mailing list.
fabriziovenerandi wrote:
About the bugs and problems, after more deep test using Oo 2.0 for windows and testing it again with neooffice, I can say those problems and bugs are less I feel in my yesterday's (unlucky) test.
You can also post them to the OpenOffice X11 Testing forum here. It is read by the major people for the X11 project. If you find a problem that affects all of the versions, MacOSX X11 and Windows, then please join the Quality Assurance (QA) mailing list.
just want to add to what James said, if you (you being anyone reading this, not just f.) want to report things, but don't want to join the mailing list, just use the X11 fora below. If anything, I will make sure to pass the word on myself.
Thanks for all the answers.
Today I installed Oo 2.0 for windows and I found all the bugs I found except one are openoffice 2.0 bug, and not openoffice mac x11 bugs. I apologize for my yesterday's message.
After the test I think Oo 2.0 is too young for me to move my work on it. It is too instable and many things are not working in base section.
The other problem is that give feedback for Oo 2.0 takes me a lot of time: I have to found the bug on Oo 2.0 x11, test in on neooffice, switch to another machine to test on windows version, make screenshots and write in english a message that try to explain the problem.
I can not use all this time at work, and I have no time at home.
f. _________________ eadem sed non eodem modo facere
=) indeed it may take a bit of time, but here is the good part, you don't have to do it yourself.
when you find these things, just post them, there are others (like me) who will help!
And there are those of us that 'straddle the fence' and work on both projects. If there is a problem with NeoOffice that ends up being a problem in OpenOffice, you get two things:
1. Confirmation that the problem does exist in NeoOffice
2. That the problem is OpenOffice.org related and not a problem in
NeoOffice.
If we can confirm that the error exists in more than one platform, this is better.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum
