To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102542 Issue #|102542 Summary|Non-Basic Scripts should run both at user and share le |vel Component|framework Version|OOo 3.1 Platform|All URL|http://wiki.services.openoffice.org/wiki/Documentation |/DevGuide/Scripting/Scripting_Framework_URI_Specificat |ion OS/Version|All Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|FEATURE Priority|P3 Subcomponent|scripting Assigned to|ab Reported by|bmarcelly
------- Additional comments from [email protected] Fri Jun 5 13:11:00 +0000 2009 ------- The current URI specification for running a non-Basic script (JavaScript, BeanShell, Java, Python) is : vnd.sun.star.script:MACROREF?language=Language&location=[user|share|document] The consequence is that an extension containing a non-Basic script will contain URI's where the running level is fixed : either <user> or <shell>. These URI's are hard- written for example in the AddonUI.xcu file, or in the event tab of a dialog control. So if the extension designer wants its extension to be installed in user or shared levels, he/she must provide and maintain two variants of the same extension. Minimal request: Add another location, e.g. <office>, which means : search the script in the <user> layer, and if not found search in the <share> layer. Desirable request: If the URI contains <user>, search the script in the <user> layer, and if not found search in the <share> layer. This variant has the advantage of enhancing the usage of existing extensions. Then there is no need for a new location like <office>. If the URI contains <share> we could suppose that the intention of the designer is to restrict to <share> only. --------------------------------------------------------------------- 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]
