#Physicseditor corona sdk portable#
#Physicseditor corona sdk windows#

With our graphics engine, we’ve vastly simplified how you achieve numerous visual effects intuitively and efficiently on modern GPU’s. Our vision for 2D graphics has always been very ambitious. At the same time, there are some key steps we need to take to help would-be plugin writers, especially resources focused on learning by example. So our goal is to broaden the types of folks who can offer their plugins to the entire Corona community. Today, we recognize that we could do more to make this more open. Originally, we focused on 3rd parties that wanted to offer their services to the Corona community via these plugins. A plugin could be hosted on our server and be made available instantly to all Corona developers. When we first introduced plugins, we architected it to be optimized for distribution. Support for new platforms becomes a lot more feasible if we only have to commit to a core set of features, leaving out ancillary feature and/or services.

#Physicseditor corona sdk windows#

We think the way forward is to simplify, as we did with Windows Phone 8. In this context, it only makes sense to target platforms with iOS/Android-level market traction. That complexity is compounded by the sheer amount of features in Corona SDK. There’s a lot of effort to support an initial port, and a continuing cost to support OS updates and new hardware for that OS.

#Physicseditor corona sdk portable#

PlatformsĬorona has been designed to be portable and cross-platform, but that doesn’t mean there aren’t challenges in supporting new platforms. So instead, I’ll touch on some of our thinking around four different themes where we will be doing significant work:Īnd in keeping with our philosophy, I’ll talk about our approach and direction, holding off on specifics until I have concrete news to share. I’ve previously discussed our thoughts on why we don’t do roadmaps (and neither do other companies, at least not successfully) as well as our strong bias to talk about what we’ve actually delivered. Now, as I look ahead, I’m incredibly excited about where Corona is headed this year, so I’d thought I’d share the direction we’re taking this year.īefore we dive in, I should emphasize that this is not a roadmap. These were all great additions to the Corona platform and we continue to work on them. On the Corona and product side there are lots of highlights, including CoronaCards, Windows Phone 8 support, debugging introspection, CoronaViewer, Composer API, Composer GUI Beta, Particle Designer support, and much more. We want to make sure the Fuse/Corona integration is rock solid and battle-tested before we open the doors to everyone.

Right now, we’re in a small pilot with a small group of Corona developers. The more we interact, the more it feels like we’ve all been working together for a lot longer - and having been through a couple of other acquisitions, that actually is a pretty big deal.Īs I’ve mentioned before, Fuse’s products help developers make more money. It sounds cliché but there couldn’t be a better cultural fit.

We’re all really happy to be part of the Fuse family. The biggest thing that happened was that we were acquired by Fuse Powered. A lot has happened in the past year, so let’s talk about where we’ve been and where we’re headed.