NaTcl status
5 views
Skip to first unread message
Alexandre Ferrieux
Jul 19, 2011, 1:29:48 PM7/19/11
to NaTcl
To those interested: NaTcl works on Chrome 10,11 -- however, due to
ABI instability in the Google NaCl runtime, a separate .nexe must be
generated (with a dedicated SDK version) for each and every major
Chrome version. Moreover, the exact mechanism of browser-plugin data
exchanges has yet to stabilize too. To avoid wasting resources, we'll
thus wait for the upcoming NaCl official release, after which Google
promised stability.
Independently from these "environmental" issues, NaTcl is functionally
in a stable state: the only missing thing maybe is the encoding
system, since it is based on a bunch of files and there's currently no
VFS. (One could imagine to fetch the .enc files lazily over an XHR,
like the [source] emulation does).
Building on NaTcl, Colin has developed a bunch of DOM-based widgets in
NaTk. Colin, the stage is yours :)
-Alex
ABI instability in the Google NaCl runtime, a separate .nexe must be
generated (with a dedicated SDK version) for each and every major
Chrome version. Moreover, the exact mechanism of browser-plugin data
exchanges has yet to stabilize too. To avoid wasting resources, we'll
thus wait for the upcoming NaCl official release, after which Google
promised stability.
Independently from these "environmental" issues, NaTcl is functionally
in a stable state: the only missing thing maybe is the encoding
system, since it is based on a bunch of files and there's currently no
VFS. (One could imagine to fetch the .enc files lazily over an XHR,
like the [source] emulation does).
Building on NaTcl, Colin has developed a bunch of DOM-based widgets in
NaTk. Colin, the stage is yours :)
-Alex
Reply all
Reply to author
Forward
0 new messages