Play 'index.html' in your browser ! !

0 favourites
  • 6 posts
From the Asset Store
This is a single chapter from the Construct Starter Kit Collection and the Student Workbook from the Workshop.
  • How to play 'index.html'in your browser.

    You can use this method to play/test your Construct games(html.index) in your browser (running from your hard drive) without getting the dreaded security alert.( Ive only got a Voda 2 gig internet limit, so having the abilty to test a game before uploading to Dropbox is gonna help......anyway the important bit.



    1, Go to Website

    and download 'mongoose' web server (open source Chrome project)


    (its only about 130kb) I got the 'no istall'version

    2, Drop the mongoose.exe file into the exported Construct game directory (containing your html.index file) and double click it.(the .exe)

    The server creates an icon on your bottom taskbar when its running.

    3, Start you browser, and point it to   http://your_machine:8080 (I used for machine number.

    4, Your game start loading into your browser.

    To close the server ( right clicking icon for options)

    MY spec :Windows XP SP2 CHROME 16.0.912.77 m

    It worked first time , but i might have been lucky.

    Please read the documentation on the mongoose website before using it.

    There are various settings and security issues that you need to know about.


    <img src="smileys/smiley3.gif" border="0" align="middle">

  • Don't you mean 'index.html'? Also, why not just preview inside Construct 2? It's quicker and should work the same.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Maybe for offline gaming? I am still confused as to how to accomplish offline gaming with HTML5.

  • : You have this tutorial to guide you with offline gaming with Construct 2 exported projects.

    Ashley: I think what Chris meant is testproof an exported project without having to upload it to an online webserver first.

    Solution, local server testing.

    Moongoose, WAMP any kind of html server with local application will do the trick indeed.

    Moongoose sounds simple enough though for quick tests (hierarchy of the files starting in the very same place as the executable, this is easy and quick to remember for punctual testing).

  • Construct 2 uses its own local server for previewing on. The code is almost identical for preview vs. export. So it's hard to imagine anything that could go wrong, apart from I guess maybe quickly checking all your third party plugins work with the minifier.

  • "The Final build"

    "During the early days of iPhone software development, there were no mechanisms for doing beta tests. Those of us on the bleeding edge were developing apps with very little peer review and beta testing.

    But this essay isn�t about reminiscing. It�s about telling you how to test the applications you upload to iTunes Connect.

    If you�ve submitted an application to the App Store, you know that sinking feeling of not being able to test your final build. The binary that gets signed with the �App Store� distribution mechanism cannot be run on your test devices: you can�t be sure that the final bits you send to Apple are complete.

    But there�s a simple way around this problem and it�s called codesign. The same application we used for our pre-Ad Hoc beta testing can also be used for a final test on your App Store submissions.

    The first step is to create your distribution build for the App Store. For this example, we�ll be using the Frenzic application and putting it into build/Distribution-iphoneos. After the build completes, make the ZIP file archive immediately. Put it in a safe place so you can upload it to iTunes Connect after you finish your final test.

    Now you can move the updated application onto a test device and make sure that the final build is OK. Everything except the signature is the same: if there�s a missing file or something that�s messed up, you�ll be able to find it before the QA engineers at Apple do (and with 10 day turnaround times, that�s a very good thing.)

    Once you�re happy that everything looks good, upload the ZIP file you created earlier to iTunes Connect and crack open a beer. As you�re enjoying that beer, take a look at the codesign man page for more information on this essential utility. Or write an essay for your web log :-)

    Updated July 2nd, 2009: Note that this procedure can also be used if you are beta testing. This is particularly helpful in cases where you�ve upgraded to an iPhone 3GS and the Ad Hoc .mobileprovision file for the beta contains the UDID for your older device. Many developers have hit the 100 device limit since the release of the new phone, and can�t add devices into a new .mobileprovision file. You�ll be able to test the beta releases after signing the code with your own certificate. The only case where this won�t work is when the app being resigned uses the keychain."

    Download full version rtf


    A Overview of Game Testing Techniques.pdf


    Testing the final product BEFORE distribution is essential. When a car rolls of the Ford production line it gets tested...You cannot final test a product until its finished.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)