This document wants to help developers to migrate their Cell·SDK 1.0 code to the 1.1 version.
The new version adds lot of new pretty cool features (camera, Localytics integration, status API…) but there is a new one that has a slightly impact in the Cell·SDK development: The Screen Manager.
Screen Manager
This new component allows you to manage multiple screens in an isolated way, making much easier to control your application flow. For example, we can make a menu screen, an options screen, a game level screen and navigate through them.
The basic operations of the Screen Manager are:
- - Go to a new Screen. The basic way to set a new screen in the app. Just replace the current screen with a new one.
- - Push a new Screen. Push the new screen into the top of the screens stack. That’s very useful to return to a previous screen, or maintaining a tree of screens (options menu, for example).
- - Pop the current Screen. Heavily related to the previous method, popping the current screen is the only way to return to the previous one.
In addition, we can add some extra shininess to your application with the inclusion of transitions. We offer a set of default transitions, but you can make your own and (surely) awesome transitions.
However, to ensure correct flow of the application we need to make some simple changes of our previous code. The most important is to transfer some behaviors from the previous Application class to the new Screen class, like component addition, resources management and animation control.
Don’t forget to backup your work first, before you try to convert it.
List of errors resolved using this post
|
'Application.BackButtonPressed()': no suitable method found to override
Argument 1: cannot convert from 'string' to 'Microsoft.Xna.Framework.Graphics.Texture2D'
Argument 1: cannot convert from 'string' to 'Microsoft.Xna.Framework.Graphics.Texture2D'
The best overloaded method match for 'Syderis.CellSDK.Core.Graphics.Image.CreateImage(Microsoft.Xna.Framework.Graphics.Texture2D)' has some invalid arguments
The name 'AddComponent' does not exist in the current context
The name 'RemoveComponent' does not exist in the current context
The name 'CreatePhysicWorld' does not exist in the current context
The name 'SendToFront' does not exist in the current context
The name 'Adjustment' does not exist in the current context
The name 'SetBackground' does not exist in the current context
|
Moises Nuñez
16. March, 2012 | #
How interesting!, I have some ideas to join. An iPad 2 is a great prize! .. There is still a long time, I hope the competition is not...
Marcos Cobeña Morián
14. February, 2012 | #
Hi Lucas,
Currently we don't plan to have such feature -although we know it'd great. We depend on MonoTouch to generate .apk, and it...
Dandev
13. February, 2012 | #
very well explained! good job guys!
Lucas
02. February, 2012 | #
Hi. I would like to know if you plan to make an enviroment to develop for iOS on Windows (instead of MacOX). Thanks!