Bjoern Milcke wrote:
Hi Leonard,
I think I still do not quite understand what you want, apart from
plugging R into OOo, which I think is a good idea to customize OOo for
the scientific people out there. But if this works, where is the need in
re-writing the newly rewritten code again to use some scripting
language? Of course, we could have taken this approach on
re-implementation, but now it is simply too late. And we won't start
re-implementation again for sure.
The problem with scripted charts is that usually the generated charts
can not be changed interactively via a GUI, like resize objects with the
mouse or changing things via more or less standardized dialogs. This is
an absolute requirement for OOo, and the people we focus on are those
who want to create things in a WYSISYG-editor and not a
command-line-like interface.
Having both, a WYSISWG-interface and a scripting-language is quite
difficult. If you have a very mighty scripting-language and no
customizable UI (create your own dialog tabs to be integrated into
existing dialogs) for that doesn't make sense. And, as I said, users
generating documents via command-line are not the primary-focus users
for OOo.
So, why don't you try to get R inside OOo working. Then we would have
two different charting engines with different focus on usage: one for
creating colorful interactive charts for presentation and one for
creating static complex statistical charts.
Sounds like a good solution to me.
Regards,
Bjoern
Without reading the API documentation, why not just create a file
translater that can work with R or gnuplot files and then generate the
necessary code for the API. I know I would like this in the future.
Same idea as importing a Wordperfect or MS word document. Maybe this
could even be expanded to allow interactive actions.
Now to find some time to read the API.
--
Robin Laing
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
