|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | Superfluous request of JRE in Tools > Macros | ||
|---|---|---|---|
| Product: | General | Reporter: | bmarcelly <marcelly.bernard> |
| Component: | scripting | Assignee: | joachim.lingner |
| Status: | CLOSED DUPLICATE | QA Contact: | issues@framework <issues> |
| Severity: | Trivial | ||
| Priority: | P3 | CC: | flibby05, issues, joachim.lingner, rvojta, thomas.benisch, tony.galmiche.ooo |
| Version: | 680m87 | Keywords: | oooqa |
| Target Milestone: | OOo 2.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Latest Confirmation in: | --- |
| Developer Difficulty: | --- | ||
|
Description
bmarcelly
2005-04-05 09:41:52 UTC
Test with 1.9m91 - Same error messages with Tools > Macros > Run Macros... - All correct, no error messages with Tools > Macros > Organize Macros - here is another case (could be present in earlier versions) : Customize Toolbars > Add commands > Click on "OpenOffice.org Macros" in left side of the panel. You get 6 consecutive error messages, then you can select a Basic macro. Just to complete the picture... - Writer : insert a picture, then click Picture button on the Picture toolbar. Click on the Macro tab of the panel. You have to answer 15 times No, then you can assign a Basic macro. - Writer : menu Format > Character. Click on the Hyperlink tab of the panel. You have to answer 15 times No, then you can assign a Basic macro. Tested on 1.9m91. Same for Linux, lot of warnings when JRE is disabled. CAN REPRODUCE with Win NT OS and m95 release. It looks like that this Issue is already fixed. I tried this with m97 and ooo-build (m100) and it works perfectly. No more warnings ... No, rvojta. I just tried with 1.9.100 on Win XP with JRE disabled. Same warning messages on Tools > Macros > Run macros... Same warning messages when Customizing toolbar to add a macro Same warning messages whith Writer > insert a picture > click Picture button on the Picture toolbar > Click on the Macro tab of the panel. (tests are not exhaustive) Granted, no more messages for Tools > Macros > Organize Macros > OpenOffice.org Basic.. . Hmm, you're right ... I tried again and it doesn't work, dialog back ... The "Run Macro" and "Organize Macros" menu entries use the scripting framework which is partly implemented in Java. Without it only Basic would work. If you want the same functionality and do without Java then you need to reimplement the respective Java services in C++. But if you are just annoyed by the messagebox popping up again and again then this is a different matter for which there is already issue 37020. bmarcelly please decide what exactly is the issue here. In OOo 1.1 it is not necessary to have the JRE to run OOo Basic macros, or attach Basic macros to a picture, or to a Toolbar button, or to an hyperlink. In OOo 1.9 it is still not necessary to have the JRE to do all this BUT the user will be bothered by numerous stupid messages. Even one warning message would not be acceptable, because in fact JRE is not necessary even with the current design. Is it so difficult to simply squeeze these messages and continue? The same useless messages appear if the user wants to run a Python macro. It is not a problem of switching off the JRE option, it is that a lot of users simply don't have the JRE and don't want to have it (they have old PC with few memory or they can't download JRE or they dislike it). The fact that, after numerous warning messages, you are nevertheless able to do what you want without JRE, could be assimilated to obtrusive popup advertisements from Sun marketing. I prefer to consider this as faulty design. Even with JRE, the first time you open Tools > Macros > Run Macros the panel show after a delay inexistent in OOo 1.1. This is because Java has to be needlessly loaded. So the bottomline is : it should be possible to run Basic or Python macros without JRE and without any JRE warning message. Just like OOo 1.1. mh->jl: as agreed, we need to reduce ammount of box to one per user action . *** This issue has been marked as a duplicate of 37020 *** closing because this is a duplicate issue |