Savvy001

Unfortunately, i have some bad news; the problem lies in the libraries used by Filesaver and jsPDF. As it seems, one of the dependencies for jsPDF is actually the filesaver.js used by pode's plugin and conflict arises on global namespace when working with URL variable.

I tried to work around it; in C2 event sheet as well with adapting filesaver.js but with no luck.

julie12

I'm not sure what do you mean with "increasing the table width. I increased the following key property as well as html table width.".

Are you trying to render .html inside .pdf file using this plugin? The jsPDF library supports this functionality, but i have not managed to implement it in this plugin.

Upped plugin version to 0.1.2; please re-download and test; see change log for details!

Cheers!

zenox98

Yes, i did! I just did not want to simply c/p it, not because i'm lazy or mean, i just believe when somebody is learning it's valuable to let a 'student' discover stuff on his own; just give him push in the right direction...

The whole java/javascript story is interesting in it's historical contest. There's a lot of interesting details on javascript wiki page. Also, the web is full of articles on the topic. A simple google search results in a wealth of resources!

If you wish, you can purchase the signalling server in the scirra store here, host it yourself or adapt it to your needs.

Lunarovich

A superb plugin! Great, great addition to the plugin list, thanks for sharing!

It would be great that you include some kind of license with the plugin; both for the rot.js library and your plugin... (to keep rot.js licensing satisfied; as i see, there's no licensing info for rot.js in your plugin)

I took the liberty and created an example license.txt for you that would cover all licensing issues; do what you like with it!

is Java near to javascript?

Have you read the SDK overview ever? You should read the whole manual too, if you're serious about the writing plugins...

There are some resources around; but the best place to start learning how to use SDK is to read the sources (runtime.js) directly; You'll learn how to read source code, you'll learn how are things done in SDK, and you'll learn a lot of javascript along the way.

You could start with how the line-sight behavior is implemented, and than continue from there!

Also, check out the SDK template, you'll se that some of the basic stuff is implemented so you can get a good start...

Guys, just a heads up; the playable demo is available for download on http://collective.square-enix.com/proje ... ar-with-me

If anybody can help us test it on linux 32bit that would be great!

Also, a quick tutorial on how we created an windows installer for this release is coming soon!

Aphrodite

Oh noes, you got it wrong! Basic idea and the whole point of node-webkit is to get low-access to so from a browser-like environment! That's why it's so great, nothing stops you from executing any kind* of system code.

You can execute all kinds of fun stuff, even with built in C2 plugins; when need arises look into nodewebkit plugin, action "run file". You can use that to execute a .bat file!

*for some things you'll need acquire system/user permission.

Aphrodite

Not really, both rely on nodejs+chrome. Main difference is the approach on mixing those two. In nw, starting point is a .html file ; in atom-shell you start with a .js file and create a window from there. Atom-shell is backed up by github, so it won't go away any time soon. Fun thing is that top contributor (zcbenz) to atom-shell is also the second top contributor to nw. Almost as if he created his own, better version of nw with hook... khm... easier build process and context management. Anyhow, for now i'm with node-webkit, i just threw this outhere because i think it would be wise to watch how things develop further down the road.

Also; not sure in what do you mean with more low-level interactions. Node can do low-level quite good... Can you expand on this?

Ashley

What's your opinion on atom shell? In a way it's similar to nw, but uses a different approach.

My initial test were ok, but i've just created a simple test C2 app and packaged it. I'm satisfied with nw, but it's always nice to have an alternative.

have you looked into JSONP (json with padding)? this technique is known to be used on mobile apps to avoid CORS problems.