phaser/2.7.0/resources/tutorials/01 Getting Started/part5.html
2016-11-22 01:36:56 +00:00

48 lines
No EOL
3 KiB
HTML
Executable file

<!doctype html>
<html>
<head>
<meta charset="UTF-8" />
<title>Phaser Tutorial 01 - Getting Started</title>
<script src="build/phaser.js" type="text/javascript"></script>
<style>
body {
font-family: Arial;
font-size: 14px;
}
</style>
</head>
<body>
<h1>Getting started with Phaser</h1>
<h2>Part 5 - Downloading Phaser</h2>
<p>Phaser is an open source project and available to download for free. We use github to manage the project and it's on the github site that you will find the latest version:</p>
<p><a href="https://github.com/photonstorm/phaser">https://github.com/photonstorm/phaser</a></p>
<h3>Can I just get a zip file?</h3>
<p>Yes. Github provide the option to <a href="https://github.com/photonstorm/phaser/archive/master.zip">download the whole repository</a> as a zip file. You can then unzip this locally to get to all the files. However we would strongly recommend you learn to use git instead. It will allow you to easily update to the latest versions as we release them, and it makes contributing towards the project much easier as well. If you don't fancy learning to use git via the command-line there are some great applications you can use instead. We'd recommend <a href="http://www.syntevo.com/smartgithg/">SmartGIT</a> on Windows or <a href="http://www.git-tower.com/">Git Tower</a> on OS X.</p>
<h3>Repository Structure</h3>
<p>The Phaser repository is split across 2 main branches: <a href="https://github.com/photonstorm/phaser">master</a> and <a href="https://github.com/photonstorm/phaser/tree/dev">dev</a>. The master branch contains the most recent stable release and is the one you should try first. The dev branch is where we prepare the latest versions. In here you'll find experimental features and API changes, some of which may not work. But it's also where you'll see the bleeding-edge features we're working on.</p>
<p>Right now there is an approximate delay of around 4 weeks between dev and master. This means we build the new features out in dev and let them bake for a month before we move them to master. This gives them time for others to test and comment on them, and it keeps the release rate of Phaser to a manageable monthly cycle.</p>
<p><a href="part6.html">Part 6: Hello World!</a></p>
<ul>
<li><a href="index.html">Part 1: Introduction</a></li>
<li><a href="part2.html">Part 2: Installing a web server</a></li>
<li><a href="part3.html">Part 3: Run in the Cloud</a></li>
<li><a href="part4.html">Part 4: Choosing an Editor</a></li>
<li><a href="part5.html">Part 5: Downloading Phaser</a></li>
<li><a href="part6.html">Part 6: Hello World!</a></li>
<li><a href="part7.html">Part 7: The Phaser Examples</a></li>
<li><a href="part8.html">Part 8: Next Steps</a></li>
</ul>
</body>
</html>