Stephan Gromer wrote: > Ah, okay, my fear was that the Beta-release was primarily intended to seek > for overt bugs, whereas performance would no longer be a main topic.
Of course the main purpose for the Beta is to find bugs and problems we don't know already, and a Beta usually contains some "known issues" that are accepted by the developers for that release. We already knew that the performance of the Impress slide show is unacceptable, but for the reason mentioned we found it acceptable for a Beta. ;-) > PS.: BTW, will (python) UNO-bridge applications written for OOo 1.1.4 > run smoothly in 2.0? I am currently trying to get Bibus to work > (bibus-biblio.sourceforge.net) and it would be a relief to me to hear > that I don't have to go through all this again once 2.0 is out (but of > course I will if I have to ;) ) You have to differentiate between the OOo APIs you are using and the PyUNO runtime. The APIs are guaranteed to remain stable, so your code should run also with OOo2.0 (apart from bugs ;-) - where we hope there aren't that much in the final release). I can't tell you anything about the PyUNO runtime, this is the great work of a single voluntary developer, J�rg Budischewsky, and to my knowledge he doesn't read this list, but at least at times shows up on the [email protected] mailing list. Best regards, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
