Curtis,
I, and I think I can also speak for Andreas, appreciate that you are going to support us. So, we are looking forward to receiving your patches and documentation etc. :-). If you need help, don't hesitate to contact us.
Kay
Curtis Clauson wrote:
Andreas Bregas wrote:
I'm the responsible engineer for Star/OOo Basic. My focus clearly is MSVB compatibility. Your specification project sounds interesting. Could you please give some more details about your target. There are already some OOo Basic related resources as the OOo Office online help and Andrew's great macro book (see http://www.pitonyak.org/ AndrewMacro.sxw). How do you see the role of your specification in this context?
Please refer to this newsgroup thread for the full background of this task: news://news.gmane.org:119/[EMAIL PROTECTED]
The bullets are:
* There is no OOo Basic script language specification available to script developers or potential implementers.
* There is no up-to-date or comprehensive OOo Basic script language guide for script developers. The OOo help files are out-of-date, incomplete, and error-ridden. The only resources available on the OOo web site are sporadic, out-of-date, and incomplete.
* Mr. Pitonyak's book, while a wonderful resource for advanced usage, is a commercial product and therefore unacceptable as the only documentation of OOo Basic.
I've been gradually ripping into the OOo Basic implementation to create this specification. I'm hoping it will be accepted as a live document on the OOo Basic project website, and act as the definitive source for OOo Basic implementers and developers. It's just taking awhile since I have to reverse engineer everything, and what little commentary there is has to be translated from German.
Once done, I intend to create an up-to-date and comprehensive OOo Basic Developers Guide and updated help file pages. The documentation currently available to OOo users is out-of-date, incomplete, and full of errors. It does not provide the information a script developer needs to create effective OOo scripts, and is a constant source of frustration.
Since I'm deep into the implementation anyway, and it turns out to be an ancient procedural parser/generator/runtime architecture, and I've found a number of bugs and language inconsistencies, I wanted to know from what source this language was intended to be derived, if it was the ANSI Full Basic specification or some unknown Sun document, before I started creating patches or rewriting code.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
