Archived:How to develop Flash Lite games for Nokia series 40 and S60 devices
Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.
We do not recommend Flash Lite development on current Nokia devices, and all Flash Lite articles on this wiki have been archived. Flash Lite has been removed from all Nokia Asha and recent Series 40 devices and has limited support on Symbian. Specific information for Nokia Belle is available in Flash Lite on Nokia Browser for Symbian. Specific information for OLD Series 40 and Symbian devices is available in the Flash Lite Developers Library.
We do not recommend Flash Lite development on current Nokia devices, and all Flash Lite articles on this wiki have been archived. Flash Lite has been removed from all Nokia Asha and recent Series 40 devices and has limited support on Symbian. Specific information for Nokia Belle is available in Flash Lite on Nokia Browser for Symbian. Specific information for OLD Series 40 and Symbian devices is available in the Flash Lite Developers Library.
Article Metadata
Code Example
Source file: Media:Flashlite game.zip
Compatibility
Platform(s): Nokia series 40 and S60
Article
Created: narender_raul
(09 Apr 2008)
Last edited: hamishwillee
(14 May 2013)
24 May
2009
So you have decided that you would like to make a Flash Lite game for Nokia devices. Before you start coding the game you should be aware of a few things about Mobile Devices and Flash Lite.
Contents |
Device issues
Developing for a device means, we have a few limitations that we must keep in mind, when develop Flash Lite games or content.
- The screen resolution on a device tends to be much lower then that of a desktop computer. The mobile screen size is 128X160, 176X208, 240X320, 320X240 pixels in resolution. Compare to the desktop resolution of 800X600.
- The CPU tends to be slower on a device.
- The input options are different on a mobile devices and a desktop.
- The amount of RAM available to a mobile device compared to a desktop computer can differ very much. Making games that 2MB of Bitmap, Vector and sound run on desktop computer but not feasible on a mobile devices.
- Two key press at a same time not work. For example player run and jump same time. No mouse click and drag navigation.
Flash Lite issues / tips
- Use vector graphics rather than bitmap graphics. Flash is vector based, so the final Flash file will have small size and would also automatically resize for large screen.
- It is also good idea to use bitmap images at sometimes. When the graphic to be drawn is of small size and would not be rescaled, its wise to use Bitmaps as it would eliminate the need for computation.
- Use vector graphics, but not use lots of curves, add less anchor points and do not use gradients .
- Use device fonts and use pixel fonts For example hooge 05_53
- Fonts are distorted when flash Lite file automatically scaled and small make them fonts blur or not readable.
- Optimize the graphics in such a way that clarity and presentation are not reduced but the computation involved is reduced.
- Use variable and predefine values, not use too much hard-code.
- To optimize the graphics use:
fscommand2("SetQuality",quality)
- Reuse your functions
One of the most important thing in game development is - How well Flash Lite game actually play on mobile devices. . This is determined by -
- How Responsive it is
- How smooth it is
Always test the game on your handset as there are certain parts of the script that can be tested only on a physical device. Always remember that the emulator or Adobe Device Central is not completely efficient and is an approximation of the performance.
Flash Lite 1.1 Game with simulated Array
When you are developing Flash Lite 1.1 game. you may think to use the array. But in flash Lite 1.1, you don't use the array. what to do?
- The solution is to develop simulate array by creating a set of variables or instance name.
- The eval function was used to simulate array.
- You can also use eval function to dynamically set and retrieve the value of a variable or instance name.
For example: A player eat bugs and add point with use of simulate array and predefine values.
- There is also an alternative approach for Simulating Arrays in better way in Flash Lite 1.1
- First you have an idea of game.
- you want to create a nice background for game.
- Define a 12X12 grid.
- player size 12X12 for four sides. For Up, Down, Left, Right positions .
- Make a instance name player set frame label up, Left, Right, Down. Stop them four frames.
- Create a bug and give a instance name b1, b2, b3, b4
- Make sure that both player and bug have registration point in left top corner.
- Now lets declare variables in frame.
- Maximum bug=total bugs.
/:max_bug=tot_bug=4
- Text variable for score.
/:score=0
Define event handler
- First move the player around screen.
Move a player in four direction. Move X and Y position 12 pixel.
tellTarget ("/player") {
gotoAndStop(2);
if (_root.player._x>22) {
//_x and _y position and speed
posX = _x-12;
posY = _y;
_x = posX;
tellTarget ("/player") {
gotoAndStop(2);
}
- Predefine values of bug x and y position on screen.
- Check bugs on screen.
Use For loop to check the bugs on screen. crate simulated array to check the bugs and collision with player x and y position. If collision happened add score and decreased one bug on screen make bug visible false on screen. if player x, y coordinate and bug X, Y coordinate collide.
- Check if bug maximum equal to 0 then go to completed frame.
if (_root.max_bug<=0) {
tellTarget ("_level0") {
gotoAndPlay("completed");
}
}
Code
//Left Key
on (keyPress "<Left>") {
tellTarget ("/player") {
gotoAndStop(2);
if (_root.player._x>22) {
//_x and _y position and speed
posX = _x-12;
posY = _y;
_x = posX;
tellTarget ("/player") {
gotoAndStop(2);
}
//Checking for bug
for (i=1; i<=/:tot_bug; i++) {
//Simulated Array
if (eval("/:bug" add i add "0") == posX) {
if (eval("/:bug" add i add "1") == posY) {
// Add score
_root.score += 10;
_root.max_bug -= 1;
tellTarget ("/b" add i) {
_visible = false;
}
//check if bug max equal to 0 then go to completed frame
if (_root.max_bug<=0) {
tellTarget ("_level0") {
gotoAndPlay("completed");
}
}
break; // this will terminate/exit the loop
}
}
}
}
}
}
//Right key
on (keyPress "<Right>") {
tellTarget ("/player") {
gotoAndStop(3);
if (_root.player._x<140) {
//_x and _y position and speed
posX = _x+12;
posY = _y;
_x = posX;
tellTarget ("/player") {
gotoAndStop(3);
}
//Checking for bug
for (i=1; i<=/:tot_bug; i++) {
//Simulated Array
if (eval("/:bug" add i add "0") == posX) {
if (eval("/:bug" add i add "1") == posY) {
//Add score
_root.score += 10;
_root.max_bug -= 1;
trace("b" add i);
tellTarget ("/b" add i) {
_visible = false;
}
//check if bug max equal to 0 then go to completed frame
if (_root.max_bug<=0) {
tellTarget ("_level0") {
gotoAndStop("completed");
}
}
break;// this will terminate/exit the loop
}
}
}
}
}
}
//// Up key
on (keyPress "<Up>") {
///Path
tellTarget ("/player") {
gotoAndStop(1);
if (_root.player._y>24) {
//_x and _y position and speed
posX = _x;
posY = _y-12;
_y = posY;
tellTarget ("/player") {
gotoAndStop(1);
}
//Checking for bug
for (i=1; i<=/:tot_bug; i++) {
//Simulated Array
if (eval("/:bug" add i add "0") == posX) {
if (eval("/:bug" add i add "1") == posY) {
//Add score
_root.score += 10;
_root.max_bug -= 1;
trace("b" add i);
tellTarget ("/b" add i) {
_visible = false;
}
//check if bug max equal to 0 then go to completed frame
if (_root.max_bug<=0) {
tellTarget ("_level0") {
gotoAndPlay("completed");
}
}
break;// this will terminate/exit the loop
}
}
}
}
}
}
////Down Key
on (keyPress "<Down>") {
///Path
tellTarget ("/player") {
gotoAndStop(4);
if (_root.player._y<176) {
//_x and _y position and speed
posX = _x;
posY = _y+12;
_y = posY;
tellTarget ("/player") {
gotoAndStop(4);
}
//Checking for bug
for (i=1; i<=/:tot_bug; i++) {
//Simulated Array
if (eval("/:bug" add i add "0") == posX) {
if (eval("/:bug" add i add "1") == posY) {
_root.score += 10;
_root.max_bug -= 1;
trace("b" add i);
tellTarget ("/b" add i) {
_visible = false;
}
//check if bug max equal to 0 then go to completed frame
if (_root.max_bug<=0) {
tellTarget ("_level0") {
gotoAndPlay("completed");
}
}
break;// this will terminate/exit the loop
}
}
}
}
}
}
Download
- You can download an example with source code here: Flashlite game
Author
--Narender Singh Raul
Featured article, May 24th 2009 (week 22)
When creating a flash lite mobile game, is it possible to use the Nseries Game keys?
A comprehensiv article on game development in FlashLite.
The article is highly recommended for the beginners/intermediate developers who want to try developing the games in FlashLite. The article is very instructive and gives a brief idea of Device specific and FlashLite specific issues in game development.
The code snippet is very useful for the beginners as it is defined in FlashLite 1.1. If you want to target the games for many nokia devices, it is necessary to develope in FlashLite 1.1 and the the coding standards/structure in FlashLite 1.1 is far different from that of FlashLite 2 and above.