To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=99858





------- Additional comments from [email protected] Tue Mar 17 07:32:23 
+0000 2009 -------
I've developed a script extension in Javascript using the Extension Compiler. It
used to work just fine in Russian (so-called "Infra") OpenOffice.org 3.0.0. I
install the extensions from GUI (I didn't knew unopkg was available on Windows,
too).

However, during the development of extension, OOo 3.0.1 was released and
extension installation broke up again. Installation process went without errors,
the toolbar button in Writer was added successfully. But, the script itself
seems not to be copied/registered to the library, so pressing the button
produces the following error message:
"Cannot resolve script location for script = FreshEye.js"

The "branch" OOodev- Macros has a node "FreshEye_1.0.oxt" but the node is empty
- it doesn't expand, it has no macros ("Macro name" field is empty).

Then, I've used latest update of Extension Compiler with latest OOo310m5 build
for Windows. No luck, the same message - so I don't think the issue is solved in
3.1 branch, yet :-( Then I've tried to install with unopkg and this time it
worked fine with OOO310m5.

Reinstalled back Russian OOo 3.0.1. unopkg works, yet the same "Cannot resolve
script location for script = FreshEye.js" error is produced with toolbar button
was pressed! It worked only when installed with unopkg and then disable-enable
workaround in GUI extension manager (thanks to bmarcelly) for the workaround.

But, such long way of installation is cumbersome to end users.

---------------------------------------------------------------------
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: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to