To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=92926
------- Additional comments from ro...@openoffice.org Wed Feb 16 10:57:21 +0000
2011 -------
This should be a priority "P1", a showstopper-bug all along:
The scripting framework of OOo is of strategic, tactical and operational
importance, like it or not! Not having it function properly on MacOSX *cripples*
OOo bad time on that platform!
It is only because of the possibilities to write macros/scripts that also
allow non-professional programmers ("end-user programmers") to become able to
drive/program OOo. Employing this infrastructure also locks such
users/businesses into the OOo environment.
Plus only macros/scripts allow professional OOo developers to easily create
applications, useful functionalities for their customers in an easy way
(development and deployment alike)! Doing so, they get locked into OOo as well.
Not being able to edit existing macros at all on MacOSX because of this
(stupid) error, renders that part inaccessible and as a result totally useless
to business users of OOo on MacOSX!
Not having such a showstopper error fixed is therefore not understandable
for me as this hints that those who allot resources to fixing issues have no
clues about the impact and importance of the scripting framework on users and
businesses!
What are the reasons that the OOo developers ignore this unbelievable error
for so long? Why hasn't it been solved long ago once and forever ?
---
Whoever starts to work with Java on MacOSX using JNI will immediately be drawn
to this very MacOSX issue of the CFRunLoop in the main thread and the JVM to
have to be loaded in a separate thread if awt gets excercised. Apple has been
very open and informative about this very issue (see links below), since 2005!
In OOo it is a base feature, that awt/swing must work. Therefore I am totally
stunned that this unbelievable defect has not been fixed long ago! It not only
affects the scripting framework, but any Java code that employs awt/swing.
Here a few links to (quite old!) Mac-documentation about this:
<http://developer.apple.com/library/mac/#technotes/tn2005/tn2147.html>
<http://developer.apple.com/library/mac/#samplecode/simpleJavaLauncher/Introduction/Intro.html>
<http://developer.apple.com/library/mac/#documentation/Java/Conceptual/Java14Development/07-NativePlatformIntegration/NativePlatformIntegration.html>
<http://developer.apple.com/library/mac/#documentation/Java/Conceptual/Java14Development/04-JavaUIToolkits/JavaUIToolkits.html#//apple_ref/doc/uid/TP40001901-SW1>
Oh, once started on a separate thread it is possible to attach to the JVM from
other threads as well, AFAICT.
[BTW: judging from the OpenJDK-wiki OpenJDK will exhibit the very same behaviour
as the Apple ports of Java. So the problem won't go away, if someone would be
speculating in that direction. Plus it seems, that the Apple changes to Java in
the awt/swing area are being taken over as well by OpenJDK.]
---
*Again, I consider this a showstopper error which should stop branching OOo
3.4, until it is fixed!*
How could I increase the priority of this issue to "P1"?
---------------------------------------------------------------------
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: issues-unsubscr...@porting.openoffice.org
For additional commands, e-mail: issues-h...@porting.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
