migration from 1.3 to 2x

zyzzyxx

hello All:
Has any one tried migration from Sparrow 1.3 to 2.x? My App code has a gameCntroller which extends SPStage and then a Game class.
In my efforts so far here are the issues that I have encountered:
a) Code that works on iPad (iOS 7X) does not work in iPad air (iOS 😎, one of the problem is in the game rotation code:

if (animationTime)
    {
        SPTween *tween = [SPTween tweenWithTarget:mGame time:animationTime
                                       transition:SP_TRANSITION_EASE_IN_OUT];
        [tween animateProperty:@"rotation" targetValue:newAngle];
        [[SPStage mainStage].juggler removeObjectsWithTarget:mGame];
        [[SPStage mainStage].juggler addObject:tween];
    }
    else
    {
        mGame.rotation = newAngle;
    }

This works just fine for iOS 7, but for iOS 8, there is over rotation by newAngle amount. Why?

b) In Sparrow 1.x, we could reference an image just by name (without worrying about, @2x, @4x) but in 2.x, there seems to be a problem.
c) In Sparrow 2.x and iOS8 the launch screen looks Ok, but when the actual game background appears, it is shifted to right (or it does not cover the entire screen) why?
d) How do I reuse the existing GameController and the Game class without re-writing all of them?
My current approach is to make GameController a subclass of SPSprite and keep Game as a child of Gamecontroller. I tried making GameController a singleton object, and tried making it an aggregate of Game object, none of them looked like an elegant solution.
My App has a lot of

[SPStage mainStage]performSelector
...

.
Call it a bad design, but at that time it looked like a good idea.

So in short, the whole app is in bad dodo.
I need some direction in solving this problem.
Any ideas?

Excelcius

Hi
Its been a while since I made the leap from 1.3 to 2.0 so Im a little rusty, but did you use the Sparrow barebones / scaffold as a template for your original project ? and how are you transferring your project from Sparrow 1.3 to 2.0, are you just changing your class path to Sparrow 2.x ?

a) and c) Sparrow 2.x is a vast improvement over 1.3 and a lot of things like game rotation which was previously handled in the scaffold project are now handled internally in 2.x, so if your project is still using the original 1.3 scaffold rotation code this may be conflicting with the 2.x internal rotation code.

d) Stuff like the view controller ect are now gone from the new 2.0 Scaffold project, most of that stuff is handled internally, its just the AppDelegate and your base game class which now extends SPSprite, in the new version of the Barebones / Scaffold, much simpler and cleaner.

b) The @2x and @4x should work, I haven't had any issue with them personally, so Im not sure whats going on there.

Im not sure what additional code you have in your gameController but it might be worth creating a new 2.0 scaffold project and transfer your old code and assets over to that project, minus your game controller and other scaffold 1.3 start up classes with all the rotation code and stuff like that in, and you should be able to paste your Game class code straight into the new one, most of your other classes should work OK. Thats what I did, initially it seemed like a lot of extra work but I soon realised Sparrow 2.0 really is much simpler cleaner and easier to manage and I was up and running in no time.

Also there is a new way to access the stage in Sparrow 2.0 you might want to check out this post http://forum.sparrow-framework.org/topic/sparrow-20-faq
Hope this helps

zyzzyxx

thanks Excelcius.
The rotation problem is fixed.
As I'm updating the code, I realize there are other things that are broken/ not work as expected in 2x.
So, In my game class before any game play is started, I create a Sprite of Menu.
All it has is two buttons and two texts.
The text seems to show up after I reduce the x and y by 1/2. Why is that? has something changed in Sparrow 2x that creates this behavior?
My buttons don't show up at all.

Excelcius

Hi Im not sure I know exactly what you mean, but make sure your texture atlas is named correctly i.e.
Atlas@2x.png and
Atlas@2x.xml

also make sure you have the correct image path set in your xml file
<TextureAtlas imagePath='atlas@2x.png'>

and make sure you have the following code in your AppDelegate

[_viewController startWithRoot:[Game class] supportHighResolutions:YES doubleOnPad:YES];

Also check the obvious things like

myButton.visible = YES;
my Button.alpha = 1.0f

When you say reducing the x and y by half I assume you mean the positioning of the text, could it be that they're not showing up because they are off the screen in one of the orientations ? Another improvement in Sparrow 2.0 is that when the screen rotates the coordinate system is now always x,0 y,0 top left corner regardless of the device orientation, in the Sparrow 1.3 scaffold it would rotate the whole stage meaning that although x,0 y,0 would be the top left corner in portrait, in landscape the top left corner of the screen would be x = -80 and y = 80, if memory serves me correctly.

I rewrote my scaffold to keep 0,0 at the top left corner regardless of orientation, but now Sparrow 2.0 does that for you, again much cleaner and simpler. Could it be that your old code's object positioning, followed the old -80,80 landscape system ?

Also make sure your adding your buttons ect to game or a child of game, I can't remember if it makes any difference but game is now an instance of SPSprite not SPStage and make sure if your buttons are contained in another SPSprite for example your class "menuScreen" that, that class is positioned correctly.

And don't forget to use the iPhone 3g coordinate dimensions i.e. myButton.x = 200 automatically scales up to 400 on iPhone 4 and 800 on iPad retina

Daniel

I'd say the likeliest reason for the size problem is that you didn't enable "supportHighResolutions" in your old 1.4 code — could that be? The idea behind that is that you work with "point" coordinates instead of pixels, just as UIKit does.