'Re: Calligra Words mission statement and roadmap (1st draft)'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       calligra-devel
Subject:    Re: Calligra Words mission statement and roadmap (1st draft)
From:       Sebastian Sauer <mail () dipe ! org>
Date:       2011-11-15 10:45:05
Message-ID: 4EC242B1.7040005 () dipe ! org
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

On 11/15/2011 04:05 AM, Sebastian Sauer wrote:
> On 11/14/2011 09:54 PM, Adam Pigg wrote:
>> On a similar note, imagine the possibility of embedding JS in a 
>> document, and defining a function such as
>> function calligra_version()  { return "2.6"; }
>>
>> then, having some kind of user field that contained 
>> '=calligra_version()' that would display the appropriate content/
>
> In my opinion we should lobby for that to become part of a future ODF 
> release.
>
> So far the only way to get such dynamic functionality in is using 
> macros. But macros suck and
> to my knowledge there functionality is not really specified in the 
> specs. Since this days we have
> so many different Javascript-implementations around + they allow to 
> sandbox (unlike python
> for exampl) + they are light and fast (unlike Java) and are already a 
> de facto standard in HTML
> it would make sense to gt Javascript into ODF as official 
> "scripting-language". The hard work
> would then be to define API/functionality exposed by the applications 
> so the Javascript can
> do something with the application.

I just created 
http://community.kde.org/Calligra/Proposal_for_scripting_in_ODF for that.

[Attachment #5 (text/html)]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    On 11/15/2011 04:05 AM, Sebastian Sauer wrote:
    <blockquote cite="mid:4EC1D6DE.1090907@dipe.org" type="cite">
      <meta http-equiv="Context-Type" content="text/html;
        charset=ISO-8859-1">
      <title></title>
      On 11/14/2011 09:54 PM, Adam Pigg wrote:
      <blockquote
cite="mid:CANFkB1zZJ3QBPo9BVsH5PokshGBVt0hv+XC15aqYAVkQbnbpkw@mail.gmail.com"
        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() &nbsp;{ 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 class="moz-txt-link-freetext" \
href="http://community.kde.org/Calligra/Proposal_for_scripting_in_ODF">http://community.kde.org/Calligra/Proposal_for_scripting_in_ODF</a> \
for  that.<br>
    <br>
  </body>
</html>

_______________________________________________
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel

[prev in list] [next in list] [prev in thread] [next in thread] 