From: "Zhichu Chen" <zhichu.chen@gmail.com>
To: "Mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: luatex and javascript
Date: Sun, 7 Dec 2008 19:59:46 +0800 [thread overview]
Message-ID: <769ba7780812070359m765d62ap60ee83a2c2e4aa53@mail.gmail.com> (raw)
Hi,
I've searched the list and it seems that no one has been occurred
to my problem.
Has the javascript interface gone? 'cause I failed the following
simplest file:
================================================================
\setupinteraction[state=start]
\starttext
A few years back, \TEX\ could only produce \fillinfield [dvi]
{DVI} output, but nowadays, thanks to \fillinfield {Han The
Thanh}, we can also directly produce \fillinfield [pdf] {PDF}!
Nice eh? Actually, while the first field module was prototyped
in ACROBAT, the current implementation was debugged in
\fillinfield [pdfTeX] {\PDFTEX}. Field support in \fillinfield
[ConTeXt] {\CONTEXT} is rather advanced and complete and all
kind of fields are supported. One can hook in appearances, and
validation \fillinfield [JavaScripts] {JAVASCRIPT}'s. Fields
can be cloned and copied, where the latter saves some space. By
using \fillinfield {objects} when suited, this module saves
space anyway.
\stoptext
================================================================
It's copied from the mwidget-s.pdf
My luatex is 0.30.3, and I just run "luatools --generate" and
"ctxtools --update" today.
The error message is:
================================================================
! Undefined control sequence.
\:j::j:fields_1 ->
var
visible_field = new Array() ; var visible_fields = 0...
\docommand ...code {\getvalue {\r!java \r!java #1}
}\ifoneJSpreamble \@EA \se...
\next2 #1,->\docommand {#1}
\doprocesscommaitem
<argument> \relax fields_1,
Do_Check_Answer
\doprocesscommalist ...aitem \gobbleoneargument #1
,]\relax \global \advance ...
\presetJSpreamble ...[\allJSpreambles ]\docommand
\ifoneJSpreamble \gdef \al...
...
l.18 \stoptext
?
================================================================
--
Best Regards
Chen
----------------------------------------------------------------
Zhi-chu Chen | Shanghai Synchrotron Radiation Facility
No. 2019 | Jialuo Rd. | Jiading | Shanghai | P.R. China
tel: 086 21 5955 3405 | zhichu.chen.googlepages.com
| www.sinap.ac.cn
----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2008-12-07 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-07 11:59 Zhichu Chen [this message]
2008-12-07 12:56 ` Taco Hoekwater
2008-12-07 13:10 ` Zhichu Chen
2008-12-07 18:32 ` Hans Hagen
2008-12-08 1:07 ` Zhichu Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=769ba7780812070359m765d62ap60ee83a2c2e4aa53@mail.gmail.com \
--to=zhichu.chen@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).