As I mentioned in a previous blog post<\/a>, scenes are loaded in 2 at a time. Each time this happens, certain bits of code are triggered to first remove (purge) the previous 2 scenes before grabbing textures for the next two scenes (the app looks in folders which are named by number for each scene – this is strict). All sprite sheets within these selected folders are loaded into an Asset Manager<\/a>. Once this has completed, an xml file which contains all the required information for the newly loaded assets (more on this xml file later) is loaded and data is captured for the newly loaded scenes, including but not limited\u00a0to:<\/p>\n This snippet for a sprite sits in the apps xml file. Data here provides the x and y positioning in the particular scene (number represents percentage in the viewport which is set to 1024 x 768 as standard), parallax for x and y which dictates the speed in which is animates in and out of view, touchable simply tells the app to listen for when it has been selected like a button (because its part of an interactive scene) and audio is the unique audio file to play once the sprite has been tapped.<\/p>\n As each sprite is loaded from the xml file, its contents then dictates what happens next but they all get added to the stage as well as few other things depending on its complexity.<\/p>\n Once all of this is complete, the audio is loaded and run depending on their settings, again dictated by the xml file.<\/p>\n There’s a lot more complexities involved here. But in a nutshell, this is it!<\/p>\n How is this easy to edit you wonder? Well, its pretty easy because now this is in place, all that is required to add a new for example is:<\/p>\n Thats it! See below screenshot\u00a0where you can see an example\u00a0how to include an interactive scene, with\u00a0audio. Obviously there are naming conventions for the xml to adhere to, but these don’t really vary much!<\/p>\n![\"sprite](\"http:\/\/blogs.plymouth.ac.uk\/digital-education\/wp-content\/uploads\/sites\/96\/2016\/06\/sprite-code-snippet.png\"){kind=icon}
<\/a><\/p>\n\n
![\"scene](\"http:\/\/blogs.plymouth.ac.uk\/digital-education\/wp-content\/uploads\/sites\/96\/2016\/06\/scene-9-xml.png\")
<\/a><\/p>\n![\"iCARE](\"http:\/\/blogs.plymouth.ac.uk\/digital-education\/wp-content\/uploads\/sites\/96\/2016\/06\/iCARE-simplified-workflow-v2.png\")
<\/a><\/p>\n