SDK 2.0 revision

Today, finally CORONA SDK Beta 2.0 is available which includes iPhone, iPad and Android simulator into one unified SDK and lot of bug fixed of version 1.1

However I was a little disappointed about this version new functionalities (still in beta anyway).

  • I didn’t see any new improving in APIs, except Multitouch handler.

So no improvements in GPS, Mapkit framework support, Audio volume management or Bitmap manipulation as it was shown in Corona blog regarding Photoshop 20 anniversary App for iPhone.

  • This version becomes with extra png and eps file to quickly get buttons, checkmarks or arrows and backgrounds for application design, which is something valuable; all of them included in a new folder called Visual Library.

But again, I was expected more power on APIs, more Native controls or at least ability to control audio volume and bitmap manipulation such as blending or color management, etc.

Therefore as a customer of Ansca, I would really like to know the roadmap of this framework.

I hope to believe my, as well as the Corona community wishes are on Corona Developer Request at least on roadmap.

[import]uid: 3022 topic_id: 809 reply_id: 300809[/import]

yes, a roadmap would be great so we can see what we can expect next.

And I agree with fpassa. [import]uid: 5712 topic_id: 809 reply_id: 1729[/import]

We are going to publish a roadmap. I will post the link once it is pubishing.

Carlos [import]uid: 24 topic_id: 809 reply_id: 1748[/import]

Hope to see the roadmap soon. I am planning to buy a Mac only to develop using Corona but, considering the delay in answering several questions in the forum, I am afraid to spend some money and not have answers for several questions I have already (plus the new ones I will have when I start to use Corona). Some replies from Carlos talk about SQLite, MapKit, more UI components, Symbian export, etc but they are not available in the SDK 2. Also, several other requests are left without answers.

I know it is hard to be a small start up but, just comparing orange with orange, the Appcelerator team seems to be as small as Ansca and they are updating their product almost in a weekly basis. And besides, they are providing BlackBerry support in their next version. All we would like to know, as customers, is information to keep us aware of our limitations in getting new projects. A roadmap with dates (at least the estimated quarter information) is fundamental to our businesses.

Thanks again,
Alex [import]uid: 4883 topic_id: 809 reply_id: 1750[/import]

A roadmap will be published with the features with its expected release date… Expect far more releases now that we have a unified codebase.

We needed to get all three components, iPad, iPhone and Android at the same code base so we can then implement all the features we have talked about here on the forum. and on the feature request emails we get here at Ansca into one source tree rather than three different branches.

Now that the codebase for all three different platforms is from one source tree, it will make it easier to add a feature in one source branch, than in three different branches. We also didn’t want to add a feature just for iPhone and leave the Android without that feature. With Corona 2.0, publishing for iPhone, iPad, and Android just gotten a lot easier, and now that all of them are seamlessly integrated adding features will be that much faster and easier for us.

Corona’s 2.0 main feature was the integration of the three different platforms, iPad, iPhone, Android (both Nexus and Droid)

We are looking at adding Android OS 1.6 support, as Android OS 1.6 still has a bigger market share than 2.x. This way, your product has a wider reach and you could sell more of your apps.

We are going to add OS 4.0 support. We got an email from one of our developers who installed it and ran Corona using iPhone OS 4.0 and it worked.

And next week, I am going to have an even bigger surprise coming from our Labs.

Carlos
[import]uid: 24 topic_id: 809 reply_id: 1753[/import]

Great news Carlos. Thanks for the update (I still need some UI components thou :slight_smile: [import]uid: 4883 topic_id: 809 reply_id: 1755[/import]

Hi Carlos,

I was talking to Evan the other day about the missing support for lower Android versions. I asked for 1.6 AND 1.5.

From the last numbers of google, 1.5 has the biggest markt share!!! Look here:

http://developer.android.com/resources/dashboard/platform-versions.html

Android Platform Percent of Devices
Android 1.1 0.1%
Android 1.5 38.0%
Android 1.6 31.6%
Android 2.0 0.3%
Android 2.0.1 2.7%
Android 2.1 27.3%

With 1.6 and 2.1 you just reach 58.9% atm. At the 38.0% to it and tHEN we have a target group you can be happy about.

Also, why did you guys removed IPhone OS3 version 2.2.1 from the selectable Os versions, when you build for the IPhone (in the newest beta) [import]uid: 5712 topic_id: 809 reply_id: 1759[/import]

Roadmap is published :

Corona Developers

Am happy to announce that we published our roadmap and you can see it at Roadmap

Please not this is a first pass and we are going to drill down even further.

One thing I would like to hear from you is what *your favorite* feature is and how soon you would like to see it. You can send us email at support@anscamobile.com and we will start tallying up the request and move features around.

Carlos [import]uid: 24 topic_id: 809 reply_id: 1801[/import]

…about the roadmap, maybe (but it’s only my idea) it’s better to have a poll every seven days so You as Ansca can build make what we need.

In example.
1° week

  1. Improved landscape support
  2. Box2D physics engine

and in the next nightly build (maybe every friday) Ansca can release a new build
2° week

  1. Multitouch gesture library
  2. SQLLite

…and new build published :slight_smile:

3° week

and so on.

So we can have every friday a new build, with bug report (if any exits), or missing features.

Hope this help… :slight_smile:
Ale

[import]uid: 940 topic_id: 809 reply_id: 1816[/import]

Great idea !

C. [import]uid: 24 topic_id: 809 reply_id: 1817[/import]

Hi, MikeHart – agreed that Android 1.5 is still pretty common, but the good news is that we’ve now tested 1.5 and it doesn’t seem like it’ll be a problem for us (it’s not missing anything critical).

You can read more about this on the Labs page: http://www.anscamobile.com/corona/labs/ . [import]uid: 3007 topic_id: 809 reply_id: 1840[/import]

Yes! Thanks Evan and all the others at AM to take your customer requests serious. I hope it won’t take to long till we can use support for 1.5 and 1.6. [import]uid: 5712 topic_id: 809 reply_id: 1851[/import]