Kyatric's Forum Posts

  • Canary: thank you for the info.

  • he engine can render using <canvas>, <svg> and WebGL.

    It runs in canvas. I still don't see the point there, sorry.

    For Native Client, atm it is only supported in Chrome. The developpement team for mozilla for sure and Safari, or Opera (I can't remember the exact quote) are not really looking into adding it to their browser.

    And it will require you to learn some language like c++, won't it ?

  • I knew it was too good to be true...

    What do you mean ?

  • Added to the how do I FAQ.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • Yes, you will have to find ways to code the game without the custom plugins/behaviors.

    For now that's what you need to upload to the arcade.

  • Congrats tomshreds !

  • JackieChan: check the plugins section there are a lot of plugins/behaviors released and some recent additions are GUI plugins.

  • rexrainbow : That's pretty much the job of the webstorage plugin.

  • FireLight, I'm not sure to get the difference you make between "plugin" SDK and "runtime" SDK.

    The runtime is described in the manual SDK as well as its functions. You can check its reference.

    Maybe you mean a SDK for the exporer (named Exporter Development Kit (EDK) in that blog article about C2's architecture in the "Future plans" part. The article is a few monthes old but the "Future plans" still stand).

    As Ashley is currently adding the familly feature to C2, undergoing a lot of modifications in the inner code, releasing an EDK is not wise right now. The code is not stable/subject to changes.

    He's been writing the manual, has already put a lot of work in it and yet still has a lot of writing and coding to do.

    Also, it is not because he doesn't acknowledge your suggestions that he doesn't read them or put them on his todo list.

    But you have also to be aware that you're not the only one suggesting things and that he also has his own plan.

    He has proven to be very attentive to the community's suggestions so far, no reason for it to change.

    Also changes to the SDK are delicate since they impact all the previous works already built upon it.

    And at last, I'll say it again, what transpired from Ashley directly is that, for now, the focus is on the HTML5 exporter.

    The rest are speculations and rumors, and should REALLY not be taken into consideration at all.

    EDIT: Also — executing a local server to execute your exported project prevents the annoying message. That's how preview works. It's a local server allowing you to execute your C2 app as if it was online. It works even if you're not connected to internet, and I think this is the solution that wrapping solutions propose.

    So here goes the points 1, 2 and hopefuly 3 of your argumentation.

    This point has already been discussed/covered in several topics in the forum.

  • FireLight: have you taken a look at the manual recently ?

    The full SDK is described there. There are also more and more 3rd party dev, as well as plugins and behaviors released in the plugins section.

    If you don't go to the developpers, it is unlikely indeed they'll come to you if you just stand in your corner.

    As far as suggestion goes, not all suggestion are good, and there must also be a choice made in the priority of features to add to C2. It's not because a feature isn't implemented TODAY, that it will never be.

    Also, it was clear from the beginning that C2 was aimed at HTML5 "against" flash and that an exe exporter was a possibility, not something set in stone.

    Once again, only time will tell wether there is or not finaly an exporter.

    Anyway, as long as the HTML5's one is not finished, don't expect it.

    EDIT: Reading again your suggestions, some are trickier to implement than you think I'd say, and would require some massive reorganizing before being added.

    For now Ash as already a lot of work on his hands, it's unlikely he could handle so much stuff at once. Give him time.

  • Mipey: the current AJAX object (the official one) is already a GET. (It does only GET type of request. Jessejoh's plugin add the option to do POST requests, more secured as they can't be reproduced by simply typing the url in a browser for example).

    If I'm not mistaken.

  • Create a local variable before your for loop and check it.

    example

  • In fact on the todo list should be placed (if not already) a : make all comboboxes able to be used as combobox or expressions in action.

    In the case of layouts, layers, sounds, tags, groups, etc... this applies too. The user should be able to use the solution that fits better his needs on the moment. (either fixed choice/combobox or expression/textfield)

  • Same here, with the steps given, resize works as intended (resizes the texture to the size indicated, troncating the parts which do not belong in the new size).

    Guess you should make the full report with a capx and describe precisely the steps to reproduce this bug.

  • I guess you could compare the Browser.Platform value (browser object) ?

    I don't have a phone, so I can't test it myself, but if the OS (therefore platform) is not mac or windows or another desktop OS, then it should be mobile.

    You could also maybe compare the Browser.Agent value, to make sure it is "for mobile".

    If this doesn't work, than maybe a plugin is required.

    Or maybe Ashley has a tip to save the day.