In my existing code,I don’t need to use the Graphice 2.0 new features.
If I don’t convert my existing code to Graphics 2.0 and use the old API,Will I cause any problem?
Will the old Corona version be supported forever?
I’ve not heard either way. Do you have a heavy dependency on ReferencePoints??
Rob
Even though Rob has already replied, I’ll stick my neck out and say that the older SDK builds will not be *supported* forever.
This means as time goes by and you run into bugs with the older SDK you can’t expect to get them fixed.
I suppose you’ll be able to use the older SDK as long as you like, but my advice is to consider migrating to the Graphics 2.0 SDK even though you don’t use any G2 specific features.
It’s not all that bad. Reference Points and color values are the main conversion work for many projects.
However, if you use the old sprite.* API then you’ll have more work cut out for you since you’d have to migrate to the new sprite API as well.
I mean I use the old Corona SDK to compile the my existing code .when I have free time ,I convert the code to Graphics 2.0,because Our game will be published soon. Will it cause any problem??
There should be no problems.
You can publish your game with the old SDK now, and looking forward you can migrate to G2 when you have time.
thanks
As you are a starter account, the last build you can use is 1202. This build cannot build for Facebook any longer due to changes in Facebook’s login requirements. It also has bugs regarding native textFields on iOS 7 and probably a few other iOS 7 related issues that came up after we released 1202. There were also significant bugs fixed between then and 2100, the current public build.
If you stay a starter with 1202, you may find problems with Apple rejecting apps at some point as their policies evolve and we have to adapt to them. The first likely scenario here would be two years when they release iOS 9 and cull older OS’s which, iOS 6 would be included, if they don’t kill it with iOS 8. They really don’t like supporting older SDKs. The next likely scenerio is that Apple could start rejecting apps that are not designed for iOS 7’s look at feel. I’ve not heard anything yet, but this is something they would want to do.
1202 doesn’t get you much in the way of iOS 7 like widgets.
Now what I was responding to in the first post was using a G2.0 build like 2076 or 2100 and using the V1 compatibility mode. We’ve already removed the old sprite library (but it’s available on our github if you need it). So at some point, you could expect that we will remove reference points completely and things like setTextColor() which is a hold over from G1.
My advice is if you are close to launching, stay where you are. Any new apps, by all means start with G2 and go forward. If you are somewhere in between, or you expect to update your app in the long term, then it would be beneficial to move to G2. Apps have a shelf life and your needs to go back and update apps that are a couple of years old isn’t all that common unless its really popular, but if that’s the case you are probably updating it regularly and in which case, that would be a candidate to move to G2.
My company is a Enterprise account,so we will publish our game using 1202 first,and then move to G2 immediately after that.Am I doing this right?
If you are happy with your app on 1202 and it’s close to publishing, I would finish out there.
Rob
I am a developer from China.I am not good at English. So Thank you for your patience.
I’ve not heard either way. Do you have a heavy dependency on ReferencePoints??
Rob
Even though Rob has already replied, I’ll stick my neck out and say that the older SDK builds will not be *supported* forever.
This means as time goes by and you run into bugs with the older SDK you can’t expect to get them fixed.
I suppose you’ll be able to use the older SDK as long as you like, but my advice is to consider migrating to the Graphics 2.0 SDK even though you don’t use any G2 specific features.
It’s not all that bad. Reference Points and color values are the main conversion work for many projects.
However, if you use the old sprite.* API then you’ll have more work cut out for you since you’d have to migrate to the new sprite API as well.
I mean I use the old Corona SDK to compile the my existing code .when I have free time ,I convert the code to Graphics 2.0,because Our game will be published soon. Will it cause any problem??
There should be no problems.
You can publish your game with the old SDK now, and looking forward you can migrate to G2 when you have time.
thanks
As you are a starter account, the last build you can use is 1202. This build cannot build for Facebook any longer due to changes in Facebook’s login requirements. It also has bugs regarding native textFields on iOS 7 and probably a few other iOS 7 related issues that came up after we released 1202. There were also significant bugs fixed between then and 2100, the current public build.
If you stay a starter with 1202, you may find problems with Apple rejecting apps at some point as their policies evolve and we have to adapt to them. The first likely scenario here would be two years when they release iOS 9 and cull older OS’s which, iOS 6 would be included, if they don’t kill it with iOS 8. They really don’t like supporting older SDKs. The next likely scenerio is that Apple could start rejecting apps that are not designed for iOS 7’s look at feel. I’ve not heard anything yet, but this is something they would want to do.
1202 doesn’t get you much in the way of iOS 7 like widgets.
Now what I was responding to in the first post was using a G2.0 build like 2076 or 2100 and using the V1 compatibility mode. We’ve already removed the old sprite library (but it’s available on our github if you need it). So at some point, you could expect that we will remove reference points completely and things like setTextColor() which is a hold over from G1.
My advice is if you are close to launching, stay where you are. Any new apps, by all means start with G2 and go forward. If you are somewhere in between, or you expect to update your app in the long term, then it would be beneficial to move to G2. Apps have a shelf life and your needs to go back and update apps that are a couple of years old isn’t all that common unless its really popular, but if that’s the case you are probably updating it regularly and in which case, that would be a candidate to move to G2.
My company is a Enterprise account,so we will publish our game using 1202 first,and then move to G2 immediately after that.Am I doing this right?
If you are happy with your app on 1202 and it’s close to publishing, I would finish out there.
Rob
I am a developer from China.I am not good at English. So Thank you for your patience.