New Public Release: 2015.2646

02 June 2015

New Public Release: 2015.2646


Corona native builds, Corona SDK, CoronaCards, News & Announcements

Today, we are shipping a new public release (2014.2646) for Corona SDK, Corona Enterprise, and CoronaCards.

Back in Jan, I identified several themes for the year. This public release exhibits a few of those themes as well as numerous other improvements. Here are a few highlights:

Check out the release notes for a full list of features and improvements.

Incidentally, if you have a Mac, we gave a minor facelift to several of the folder/tool icons:

Corona-folder-icons

walter
5 Comments
  • Harrison
    Posted at 08:55h, 02 June

    Does this allow builds for apple watch?

    • Walter
      Posted at 10:37h, 02 June

      You can with Corona Enterprise.

      For context, the Apple Watch does not currently have a native SDK for true native apps. Right now, that means the only way to create an Apple Watch app is with Xcode.

  • Ed Maurina
    Posted at 10:36h, 02 June

    @Harrison,
    I don’t think we should hold our breath for that. Due to the Apple implemented watches, this would be tantamount to adding a whole new target platform and software chain to Corona. If they’d (Apple) instead implemented a lightweight iOS on the watch it might have been possible.

    Note: If you want to develop Corona Apps for Android watches, it might be doable (depending on the watch). I’ve seen one example of this done already (last year).

    • Ed Maurina
      Posted at 10:41h, 02 June

      Yes, I should have said what Walter said there. w/ Enterprise. I guess the point I was trying to make is, as I understand it running a Corona app on the Watch would be a challenge.

      However, writing a Corona App that talks to the watch. Doable with Enterprise. Sigh… Sorry for any confusion.

  • Ed Maurina
    Posted at 10:38h, 02 June

    Dang, I meant to make that last post a reply not a post…

    Anyways, I just want to say ‘Yay!’. I’ve been seeing a lot of issues recently based on users simply using the (now) much older 2014.2511. Having the public release up-to-date will be great and help alleviate this.

    Thanks Team!