Integrating APIs

As you might know, there are (besides the big players like steam) some open platforms for casual/indie games. One of them is Kongregate

They offer an relatively easy to use API, supporting ActionScript 2/3 and Javascript.

Have a look at the Javascript API. How could it be integrated to C2?

Following the link, you can see that they also offer a html shell to make things easier. You need to embed the game in order to use the shell, of course. Does this work with C2?

In addition, there's the server-side JSON API, used for payment, high scores, badge feeds, etc. Again, how would that be integrated?

I know, that the API works for non-flash games, as I have tested several Unity games there. But I'm an absolute beginner when it comes to Javascript/html5.

Anyone?

I'm not looking for a complete solution to this problem, just a description of the way it would have to be done, maybe with some keywords that I can then google for. Or a statement that it isn't possible.

I'm not a kongregate user, so I don't really know how it works on their site.

From what I can see, I'd say you would have to modify the index.html file of an exported project and add the line:

<script src='http://www.kongregate.com/javascripts/kongregate_api.js'></script>

// Load the API
var kongregate;
kongregateAPI.loadAPI(onComplete);

// Callback function
function onComplete(){
  // Set the global kongregate API object
  kongregate = kongregateAPI.getAPI();
}

// Start the Construct 2 project running on window load.
        jQuery(document).ready(function ()
        {
            // Create new runtime using the c2canvas
              ?cr.createRuntime("c2canvas");
        });

Thank you very much, Kya, that helps a lot. I always try to solve issues, but in cases like that, I need a starting point. You just gave me one :)

Most javascript APIs should be straightforward to throw in to a plugin. Things like this we would do ourselves, but we have so much other work to do it will probably be put off for a long time until we get round to it. If third party plugin developers can pick up little jobs like this, it's really helpful to us and frees us up for other editor work and the like. Still, if nobody does as I said we'll eventually try to get round to it.

I can probably pick this up, but I can only work on stuff during weekdays. I still have to finish my bouncing ball behavior, fix that bug with the turret object (as well as implement the stuff that is missing and optimizing it), do the docs for all of them (those will probably have to wait a bit) and crank out a couple tutorials.

Funny how I'm overworked with scirra stuff, and I don't even work there :P

That would be awesome!

In the meantime, while you are optimizing your current plugins, I will start teaching myself javascript and test my capabilities. Kyatrics online version of the C2 SDK documentation is very useful, and from what I see it seems to be a straightforward adaptation of the C++ SDK for CC, so it shouldn't be too difficult.

Then again, learning is much harder as you get older... :D

Kyatrics online version of the C2 SDK documentation is very useful, and from what I see it seems to be a straightforward adaptation of the C++ SDK for CC, so it shouldn't be too difficult.

Then again, learning is much harder as you get older... :D

Beware though, the HTML version of the sdk is not up to date.

Be sure to dld Ashley's SDK package.

But yes, learning gets hard, but JS appeared quite simple, and when oriented at plugin developement, it is almost "follow the guide" :)