This section explains what you will build, with a screenshot of the completed project.

This section explains why the project is cool, unique, exciting, and interesting. It describes what advantage the project will give you.

This section explains the major tasks required to complete your project.

This section explains any pre-requisites for the project, such as resources or libraries that need to be downloaded, and so on.

This section explains the task that you will perform.

This section explains any preliminary work that you may need to do before beginning work on the task.

This section lists the steps required in order to complete the task.

This section explains how the steps performed in the previous section allow us to complete the task.

The extra information in this section is relevant to the task.

You will also find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.

Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "We also added a call to that command at the end of the timeup command."

A block of code is set as follows:

on openStack
   answer "Greetings!" titled "Hello Planet!"
end openStack

New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "So, navigate to File | Standalone Application Settings."

You can download the example code files for all Packt books you have purchased from your account at http://www.packtpub.com. If you purchased this book elsewhere, you can visit http://www.packtpub.com/support and register to have the files e-mailed directly to you.

Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you would report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the errata submission form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded on our website, or added to any list of existing errata, under the Errata section of that title. Any existing errata can be viewed by selecting your title from http://www.packtpub.com/support.

Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works, in any form, on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.

Please contact us at <[email protected]> with a link to the suspected pirated material.

We appreciate your help in protecting our authors, and our ability to bring you valuable content.

You can contact us at <[email protected]> if you are having a problem with any aspect of the book, and we will do our best to address it.