<html><head></head><body><div id="fenix-user-content">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'NokiaPureTextLight';">Cool stuff, this is essentially what koreport does for kexi and plan reports. Access to the report internals and on* events.<br>
<br>-- <br>Sent from my Nokia N9</span></p></div><br><div id="fenix-reply-header"><p>On 15/11/2011 10:44 Sebastian Sauer wrote:<br></p></div><div id="fenix-quoted-body"><u></u>
<div bgcolor="#ffffff" text="#000000">
On 11/15/2011 04:05 AM, Sebastian Sauer wrote:
<blockquote type="cite">
On 11/14/2011 09:54 PM, Adam Pigg wrote:
<blockquote type="cite"> On a similar note, imagine the possibility of
embedding JS in a document, and defining a function such as
<div>function calligra_version() { return "2.6"; }</div>
<div><br>
</div>
<div>then, having some kind of user field that contained
'=calligra_version()' that would display the appropriate
content/</div>
</blockquote>
<br>
In my opinion we should lobby for that to become part of a future
ODF release.<br>
<br>
So far the only way to get such dynamic functionality in is using
macros. But macros suck and<br>
to my knowledge there functionality is not really specified in the
specs. Since this days we have<br>
so many different Javascript-implementations around + they allow
to sandbox (unlike python<br>
for exampl) + they are light and fast (unlike Java) and are
already a de facto standard in HTML<br>
it would make sense to gt Javascript into ODF as official
"scripting-language". The hard work<br>
would then be to define API/functionality exposed by the
applications so the Javascript can<br>
do something with the application.<br>
</blockquote>
<br>
I just created
<a href="http://community.kde.org/Calligra/Proposal_for_scripting_in_ODF" target="_blank">http://community.kde.org/Calligra/Proposal_for_scripting_in_ODF</a> for
that.<br>
<br>
</div>
</div><br></body></html>