Hi Ingrid,
unfortunately I was misunderstood a little bit. I'll explain in a moment.
Ingrid Halama wrote:
It was your suggestion to just create low level shapes and store them.
The problem with these low level shapes (that could be stored quite
easily) is that they do not contain any information about logic
coordinates in a chart coordinate system.
It was not my intention to create *low level shapes*. My intention was
to create a *high level graphical language* that would be interpreted to
some low level *OOo objects and classes*, NOT to low-level graphical
shapes. ;-) That's a small but decisive difference. It is the virtual
machine who would transpose the graphical commands to OOo objects.
Maybe the best example to what I mean is a web browser. We write a web
page as some html-tags, a high level language, and the web-browser
interprets it as what it will be ultimately displayed. You can even run
java-script and change the content on the fly.
I acknowledge, that this is not necessary easy to implement, BUT:
- free graphical languages already exist
- programs using them have been written
- and there are significant advantages to this approach (you open the
door wide open to the community to write their own charting scripts/
algorithms)
The only good point against it until now, was the changing data issue
raised by Bjorn. But I will have an in depth thinking on this problem,
too. It springs to my mind, that the javascript concept used in
web-pages wouldn't be a bad idea, after all (to store later changes).
But give me some more time.
Kind regards,
Leonard Mada
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
