Daniel Kasak wrote:
Also, the basic editor / debugger leaves a lot to be desired. There's no
code-completion support, for example, which makes learning the language
and objects quite an uphill battle. In fact, you'd have to be pretty
keen to stick with it long enough to learn. I've done some small OOBasic
scripts, and I don't look forward to the next one I have to do ...
I know what you mean. I've written a few OOo macros but didn't get very
far. The OOo API is complex and the documentation for it is very hard to
read. I was about to say that things would be better if OOo used a known
language like Ruby or Python, but on a second thought, that wouldn't
help so much. The biggest problem is a complex API. It'd be better if
someone wrote a library to simplify common tasks. Ian Laurenson has a
wiki with such functions. Those would be a good start.
Cheers,
Daniel.
--
/\/`) http://oooauthors.org
/\/_/ http://opendocumentfellowship.org
/\/_/
\/_/ I am not over-weight, I am under-tall.
/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
