Graphics 2.0 - need some advise on how to take it...

I’ve been playing around with the new beta and it is so cool :slight_smile: great job Corona (I ran across a few issues but they are all tracked already., )

I must say I find the transition from setReferencePoint/xReference/yReference to the anchors a bit confusing and so I would like to request a some blog post (from rob? :)) on how to achieve the same results I had with the old API especially in regards to groups because even in compatibility mode I’m having issues.

Basically what is the difference between them for example how do I achieve the same result as setting BottomCenterReferencePoint on a group in the old API. will anchorX, anchorY = .5, 1 do (and anchorChildren=true)? or should I also change something with the childrens positioning?

Also another question would be how should I approach future games, I have a long term project (a shooter-scroller type) which obvisouly I’m going with 2.0,

But I also have several projects I took as a freelancer that should be published in a much shorter timeframe and I really don’t know what to do? I mean working on 1.0 when I know I’ll need to port it in the near future is disturbing…

As you get more familiar with G2 you’ll realise there aren’t that many changes you need to make (unless of course you must use a G2 feature in which case… errr not a lot you can do!).

G2 is only just in beta* IMO - it has enough functionality that you can play with pretty much everything it offers (and you should, it is fun!), but is not near ready for production-type builds - it still has too many quirks and outright bugs to be useful. This is why G2 hasn’t been rolled into normal daily builds. I doubt Corona team are going to put a timescale on when it is done, as we all know what can go wrong when you do that - so don’t plan on using it in the short-term (personally I’d expect it to be in beta like this for minimum of a month, probably 2 or even more before it merges with the main daily builds, but that is just my opinion, and I hope Corona don’t feel rushed into merging as that would create more issues than it would solve).

*Alpha = not-feature complete, beta = feature complete and now just in bug-fixing phase. I actually would put G2 in late alpha using this standard definition, but the changes I foresee are minimal.

As you get more familiar with G2 you’ll realise there aren’t that many changes you need to make (unless of course you must use a G2 feature in which case… errr not a lot you can do!).

G2 is only just in beta* IMO - it has enough functionality that you can play with pretty much everything it offers (and you should, it is fun!), but is not near ready for production-type builds - it still has too many quirks and outright bugs to be useful. This is why G2 hasn’t been rolled into normal daily builds. I doubt Corona team are going to put a timescale on when it is done, as we all know what can go wrong when you do that - so don’t plan on using it in the short-term (personally I’d expect it to be in beta like this for minimum of a month, probably 2 or even more before it merges with the main daily builds, but that is just my opinion, and I hope Corona don’t feel rushed into merging as that would create more issues than it would solve).

*Alpha = not-feature complete, beta = feature complete and now just in bug-fixing phase. I actually would put G2 in late alpha using this standard definition, but the changes I foresee are minimal.