[NTG-context] Forms and JavaScript

Hans Hagen pragma at wxs.nl
Wed Oct 7 01:18:53 CEST 2015

On 10/6/2015 6:34 AM, Henning Hraban Ramm wrote:
> http://wiki.contextgarden.net/Widgets
> Again working with widgets, this bug or feature – JavaScript code is only copied to the PDF if it’s used in a \goto – is still open.

feature but you can say

\startJSpreamble FOO used now

> Additionally, I found that \setupfields (plural) doesn’t work, I need to setup all formatting in each \setupfield.

fields have always be special as there can be thousands of fields their 
settings are saved in a special way (in order not to run out of memory / 
hash space then) ... kind of mkii compatible

> I found another issue with workaround:
> http://wiki.contextgarden.net/Tabulate#Itemization_or_framed_objects_inside_a_tabulation
> You need to set "\tabulatesplitlinemode \plustwo" if you put widgets in a tabulation.
> Is there any reason not to set this per default?

it would break other things

it's hard to predict what goes in cells so some heuristics works better 
when explicitly told


> Am 2015-04-03 um 11:06 schrieb Henning Hraban Ramm <texml at fiee.net>:
>> Am 2015-04-02 um 21:07 schrieb Rik Kabel <context at rik.users.panix.com>:
>>> On 2015-04-02 03:42, Henning Hraban Ramm wrote:
>>>> while trying to create some interactive forms using latest beta (MkIV), I found that JavaScripts are only then copied into the PDF, if there’s a \goto referencing a JS function.
>>>> According to the old widgets manual I thought I could set default values of fields calling JS functions or variables as [JS(MyFunc)], but that doesn’t work.
>>> Greetlings Hraban,
>>> This appears to be a pdf reader problem. On Win 8.1, Windows Reader and Chrome both show an editable field; Firefox and Sumatra show a non-editable field.
>> That’s not the problem, creating fields works great. Since JS works (probably) only in Adobe products anyway, I don’t care about other viewers.
>> But JavaScript code (within JSpreamble or JScode sections) is only copied by ConTeXt into the PDF if there’s a call of \goto to one of the defined JS functions.
>> Additionally, calling JS functions for default values of fields doesn’t work like it did in MkII (and like it’s documented in m-widgets.pdf).
>> JS in PDFs is not easy to handle, but ConTeXt should at least copy my code into the PDF as it’s documented and used to work in MkII.
>> Greetlings, Hraban
>> ---
>> http://www.fiee.net
>> http://wiki.contextgarden.net
>> https://www.cacert.org (I'm an assurer)
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> maillist : ntg-context at ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________


                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl

More information about the ntg-context mailing list