My Fantom JS app works quite happily when served up from WISP, but as a quick'n'dirty deployment solution I thought I'd try just serving up the pod JS and Images statically. Only now I'm confronted with the following JS error on startup:
It seems to caused by the fwt::Canvas static initialiser. (One of my classes extends it.)
Any idea what I'm doing wrong?
andySun 29 Jul 2012
If you use a different URI for pod files - you need to configure your Env var - see web::WebUtil.jsMain
SlimerDudeSun 29 Jul 2012
Thanks, the pod resources are being served up at the right address (in fact, I don't use the arrows and even when the app works, the browser never requests them).
After a bit more investigation it seems some other JS libs that get rendered with the page are interfering with the pod JS somehow. (For if I strip them out, it works fine.)
SlimerDude Sun 29 Jul 2012
My Fantom JS app works quite happily when served up from WISP, but as a quick'n'dirty deployment solution I thought I'd try just serving up the pod JS and Images statically. Only now I'm confronted with the following JS error on startup:
the offending JS lines being:
fan.fwt.TablePeer.$arrowUp = fan.sys.Uri.fromStr("fan://fwt/res/img/arrowUp.png"); fan.fwt.TablePeer.$arrowDown = fan.sys.Uri.fromStr("fan://fwt/res/img/arrowDown.png");It seems to caused by the fwt::Canvas static initialiser. (One of my classes extends it.)
Any idea what I'm doing wrong?
andy Sun 29 Jul 2012
If you use a different URI for pod files - you need to configure your Env var - see web::WebUtil.jsMain
SlimerDude Sun 29 Jul 2012
Thanks, the pod resources are being served up at the right address (in fact, I don't use the arrows and even when the app works, the browser never requests them).
After a bit more investigation it seems some other JS libs that get rendered with the page are interfering with the pod JS somehow. (For if I strip them out, it works fine.)