Apache OpenOffice (AOO) Bugzilla – Issue 26874
Change bindings of WebWizard so that scripting framework is used to call basic
Last modified: 2005-08-10 14:16:45 UTC
Need to change the bindings associated with WebWizard so that scripting framework will be used to execute the macro's associated with the bindings.
Created attachment 14039 [details] list of all Basic xdl files
BC: I gave myself the time to convert all macros to the new binding, I tested them and it looks like they all look fine. However I ran into several Basic problems that don't have anything to do with the binding but are related to problems that are not unusual in this phase of the product development (API bugs and changes in the OO registry ...). I will have a closer look at them when I have more time... I converted the event bindings within the dialog engine and found it worked great! BC->npower: As you suggested I send the converted xdl files as attachments to you first, to give you a chance to look at them before I check them in. The only problem occurred with the newsletter template because the attached macro wouldn't start, but this should not be your problem either. I heard there was a bug in the sfx team that caused this malfunction.
Commited bindings from bc -> adding desc of problems encountered during unit test, these have nothing to do with the bindings themselves but are existing issues. <snip> bc->np I took the opportunity to test the macros again because of the errors in the macros: Again I found out that the errors were not due to buggy event bindings but majorly because: FormWizard and Webwizad , euro converter-> typedetection problem with writer web files, changed registry paths, Import Wizard : Source code is not yet up to date with srx645 version. depot template: Seems like the url to yahoo has changed so internet update is not possible. Basically the errors in the formwizard and webwizzard do not harm anybody because both will be reimplemented in Java. </snip>
verified
Only a closed issue is a good issue. :-)
This task is integrated in a build for OOo2.0 but the 'target milestone' isn't set. To get a better overview about all integrated tasks, I change the field target milestone to 'OOo2.0'.
This issue is integrated into a build for OOo2.0, but the 'target milestone' isn't set. To have a better overview about all fixed and integrated tasks in OOo2.0, I set the field 'target milestone' to OOo2.0.