View previous topic :: View next topic |
Author |
Message |
hphinrichs Blue Pill
Joined: May 22, 2006 Posts: 1
|
Posted: Mon May 22, 2006 12:36 am Post subject: NeoOffice 2.0 and Macro Security |
|
Hi,
I'm using NeoOffice 2.0 Alpha 3. If I try to change Macro Security nothing happens. (Tools->Options->Security-Macro Security). Pressing the button has no effect. This has been the case also in Alpha 2. Is this bug already known?
BTW: I'm very impressed by this "Alpha" Software!
Regards
Hans-Peter |
|
Back to top |
|
|
pluby The Architect
Joined: Jun 16, 2003 Posts: 11949
|
Posted: Mon May 22, 2006 11:04 am Post subject: |
|
I think that this button does not work because NeoOffice 2.0 Alpha PowerPC does not include support for the Mozilla address book and the OpenOffice.org code uses the Mozilla address book library to provide JavaScript and macro security.
More details are in bug 1453.
Patrick |
|
Back to top |
|
|
mbhoy Blue Pill
Joined: Jun 12, 2006 Posts: 2
|
Posted: Mon Jun 12, 2006 2:33 am Post subject: |
|
Hi, do any of you guys know if there is a plan to fix this?
Cheers,
mbhoy |
|
Back to top |
|
|
Samwise Captain Naiobi
Joined: Apr 25, 2006 Posts: 2315 Location: Montpellier, France
|
Posted: Mon Jun 12, 2006 4:50 am Post subject: |
|
Quote from bug 1453 :
JavaScript support is disabled in the NeoOffice 2.0.x builds because we build OpenOffice.org with the --disable-mozilla flag. Fixing this would require a complete rebuild NeoOffice so I am targeting this for Neo 2.0 Beta. |
|
Back to top |
|
|
OPENSTEP The One
Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
|
Posted: Mon Jun 12, 2006 6:04 pm Post subject: |
|
Right now I hope to begin working on integrating a Mozilla build as soon as I finish tackling native edit field widgets. It may take some time since NWF doesn't fully implement support for edit fields with inset borders.
ed |
|
Back to top |
|
|
OPENSTEP The One
Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
|
Posted: Mon Jun 12, 2006 6:07 pm Post subject: |
|
In the meantime, it most likely isn't a problem. If the Mozilla stuff isn't available (like in our 2.0 Alphas) the OOo code will flip back to the default security settings of prompting you each time something contains macros. From my understanding of the feature, this is the tightest level. What the Moz stuff enables is the ability to "trust" certain macro authors and thus not see the warnings when opening docs wiht macros and the like. E.g. it doesn't actually add "security" at all to the default setting.
I have not investigated this personally, so this is based on what I've heard from others. Please correct my statement above if it is wrong.
ed |
|
Back to top |
|
|
|