After introducing a revamped home screen and an alert capability in the previous version, Playpanel 1.4 was released few days back. So what exactly does the new Playpanel version hold in its kitty? Lets take a closer look.
First and foremost, Playpanel is now available in 15 international languages which makes it accessible, globally. A major effort has also been put in to improve the performance of the application and the results have been amazing. Navigation through different parts of the application is super fast. Now you can also open Playpanel in windowed mode just like any other normal windows application. This makes it very useful for the users who want to drag it across multiple screens, minimize it to taskbar as per their wish.
Starting with 1.4 release, users can also view the games pinned by their Facebook friends within the Friends tab. This keeps them updated about what their friends like and a chance to try them out. Likewise, you can share your favourite games and also view them in the newly introduced Pinned games tab on the top. Additionally, you can invite any of your Facebook friend who is not on Playpanel, right at the click of a button.
All in all, Playpanel 1.4 offers an array of exciting features to take the users’ game playing experience to a whole new level.
If you are a game publisher, and are interested in making your game reach out to more users, please let us know by dropping a mail to PlaypanelMarketing@adobe.com.
Play more, Play better!
This post will talk about a small optimization that developers can do within their code to reduce the amount of time taken for AOT compilation of their application I would recommend developers to read this post to understand what is meant by AOT compilation.
One of the intermediate steps in AOT compilation requires LLVM to process the LLVM bytecode and to optimized LLVM bytecode. In case one of your function has a lot of actionscript code (~30000 lines) then the corresponding LLVM code is around 1.3 million lines. LLVM is known to perform badly (compilation time) on large functions. As a recommendation, actionscript developers should break down on large function into smaller functions to reduce the AOT compilation time. They need not change any code, just break a large function into many smaller functions to reduce AOT compilation time significantly.
Traditionally flash developers have been more focused on the browser to deliver their content. While delivering the content through the browser, developers generally embedded their assets within the root swf. Honestly, there is no other way except loading these images off their servers but this could have resulted in a lag whilst the content was running
With AIR however, developers need to make certain changes to their applications to make them more apt for deployment on mobile devices. With AIR, developers get access to the file system and the assets for their content can be accessed off the file system instead of being embedded within the root swf. Assets for the application should be packaged along with the application and then should be accessed on demand by simply loading them using a Loader.
Traditionally, computer programs can be executed in three possible ways – interpreted, static (ahead-of-time) compilation and Just In time (JIT). In interpreted mode, the code is translated from high-level language to low level language during execution whereas in ahead-of-time compilation the high-level language code is converted to low-level machine code before hand. JIT (Just in time) compilation is a hybrid approach of the two. Here the code translation into native code occurs during the execution time and the translated code is cached so that this conversion need not be done every time. Obviously there is a small penalty when compared to ahead-of-time compilation as there is a cost associated with this translation.
After this brief introduction lets get into the Adobe AIR world and what is there in it for an iOS AIR developer. SWF content on all platforms other than iOS is JIT compiled, whenever possible. The swf is downloaded locally and JIT compiled where possible. Continue reading…
In this post, I will explain a little about how Cache As Bitmap can impact Anti Aliasing of your content.
Let’s start with a definition. To put it very simply, I will say that anti aliasing is what gives smooth look to your content. Anti Aliasing is a way to make content look smoother by drawing certain pixels to avoid jaggedness.
For iOS applications, there are two render modes – cpu and gpu. Let us look at what all can happen with this seemingly harmless change. For all further purpose please assume that we have set the render mode as gpu within application descriptor.
Before I start, look at the two ellipses in the diagram. If you stare hard enough you will agree with me that the left image loses out when compared to the one on right in terms of quality. The right one looks like a smoother version of the left one. If you had difficulty defining anti aliasing then this image should help clear the definition. The right one is anti aliased better or is smoother.