<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 11/14/2011 09:54 PM, Adam Pigg wrote:
<blockquote
cite="mid:CANFkB1zZJ3QBPo9BVsH5PokshGBVt0hv+XC15aqYAVkQbnbpkw@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
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>
<br>
<blockquote
cite="mid:CANFkB1zZJ3QBPo9BVsH5PokshGBVt0hv+XC15aqYAVkQbnbpkw@mail.gmail.com"
type="cite">
<div><br>
<br>
<div>On Mon, Nov 14, 2011 at 8:30 PM, Sebastian Sauer <span><<a
moz-do-not-send="true" href="mailto:mail@dipe.org">mail@dipe.org</a>></span>
wrote:<br>
<blockquote>
<div>
<div>
<div> On 11/14/2011 01:51 PM, Pierre Stirnweiss wrote:
<blockquote type="cite"> <br>
<div>
<blockquote> <br>
Background: I indeed think that is a rather
important feature<br>
cause it's the only way to get content into a
document that<br>
can be in a centralized way edited/updated.
Means you for<br>
example a document describing the features of
Calligra as<br>
released and then add a user-variable field for
the<br>
version-number (e.g. 2.5 in our case). Then in
some months<br>
if the document is updated to reflect what 2.6
is about<br>
someone only need to change the content of the<br>
calligra-version variable and voila. The
alternate is to find+<br>
replace for "2.5" manually which is error-prune.<br>
</blockquote>
<div><br>
Do you mean that the only difference between a
2.5 and 2.6 release announcement would be the
release number????<br>
</div>
</div>
</blockquote>
<br>
</div>
</div>
No, that was an example. Think of a document where you
list<br>
all changes done between the 2.x versions. Then you can
just<br>
add a new chapter for a new version that includes the
changes<br>
done in e.g. 2.6, change the version-uservariables from
2.5 to<br>
2.6 and have text like "The last version of Calligra is
[2.6]" or<br>
"Last release on [2011-12-24]" auto-updated.<br>
Other examples could be a reference-number in an<br>
invoice or a postal code, city-name, etc. pp.<br>
<br>
<blockquote type="cite"><br>
PierreSt
<div><br>
<pre>
_______________________________________________
calligra-devel mailing list
<a moz-do-not-send="true" href="mailto:calligra-devel@kde.org">calligra-devel@kde.org</a>
<a moz-do-not-send="true" href="https://mail.kde.org/mailman/listinfo/calligra-devel">https://mail.kde.org/mailman/listinfo/calligra-devel</a>
</pre>
</div>
</blockquote>
<br>
</div>
<br>
_______________________________________________<br>
calligra-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:calligra-devel@kde.org">calligra-devel@kde.org</a><br>
<a moz-do-not-send="true"
href="https://mail.kde.org/mailman/listinfo/calligra-devel">https://mail.kde.org/mailman/listinfo/calligra-devel</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
calligra-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:calligra-devel@kde.org">calligra-devel@kde.org</a>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/calligra-devel">https://mail.kde.org/mailman/listinfo/calligra-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>