Its a little hard to make complete sense of the post from EETimes.com. But some interesting quotes from the short, slightly cryptic article:

By using our new IP, one can design a portable device capable of processing Adobe Flash Lite several times faster, when compared with using a processor.

Also in the announcement is a hint of better video quality as well.

After reducing the number of gates required for an IC and further tuning the video quality output by Adobe Flash Lite, NEC will start offering its IP in August this year.

One thing that does seem to be missing is an explanation of which Flash Lite version they are supporting, although the mention of video implies this is based around the FlashLite 3 player.

You can read the full (breif) announcement of NEC's new Flash Lite IP over at EETimes.com.

One further interesting thing is that I could find no mention of NEC being involved with the Open Screen Project from its press release.

Credit where its due: EETimes.com

Key New Features

3D Effects - Easily transform and animate any display object through 3D space while retaining full interactivity. Fast, lightweight, and native 3D effects make motion that was previously reserved for expert users available to everyone. Complex effects are simple with APIs that extend what you already know.

Custom Filters and Effects - Create your own portable filters, blend modes, and fills using Adobe® Pixel Bender™, the same technology used for many After Effects CS3 filters. Shaders in Flash Player are about 1KB and can be scripted and animated at runtime.

Advanced Text Layout - A new, highly flexible text layout engine, co-existing with TextField, enables innovation in creating new text controls by providing low-level access to text offering right-to-left and vertical text layout, plus support for typographic elements like ligatures.

Enhanced Drawing API - Runtime drawing is easier and more powerful with re-styleable properties, 3D APIs, and a new way of drawing sophisticated shapes without having to code them line by line.

Visual Performance Improvements – Applications and videos will run smoother and faster with expanded use of hardware acceleration. By moving several visual processing tasks to the video card, the CPU is free to do more.

An further note of interest is that the player is released on multiple platforms straight off the bat. Over on the Flash Player 10 Download Page you will find Mac, Windows and Linux verions of the flash player 10.

Full information is available from the Flash Player 10 Labs Page

 
property processesToIgnore : {}
tell application "Finder"
	set _b to bounds of window of desktop
	set screen_width to item 3 of _b
	set screen_height to item 4 of _b
end tell
tell application "System Events"
	set allProcesses to application processes
	set _results to ""
	repeat with i from 1 to count allProcesses
		set doIt to 1
		repeat with z from 1 to count processesToIgnore
			if process i = process (item z of processesToIgnore) then
				set doIt to 0
			end if
		end repeat
		if doIt = 1 then
			tell process i
				repeat with x from 1 to (count windows)
					set winPos to position of window x
					set _x to item 1 of winPos
					set _y to item 2 of winPos
					if (_x < 0 or _y < 0 or _x > screen_width or _y > screen_height) then
						set position of window x to {0, 22}
					end if
				end repeat
			end tell
		end if
	end repeat
end tell
 

I don't recall where I may have dug this up, but if you think you know, please let me know in the comments so I can give credit.

Interestingly this is a concept I began to scratched the surface of with my presentation at Flash On the Beach Last Year, and over the last few months has been a subject I have continued to keep close to hand both in my day job and my personal development projects. At the moment the Flash Player Fragmentation offers a considerable challenge to any developer wanting to design and or develop for multiple devices and multiple screens.

Articles like the one posted over at ADC on adaptive screen layouts offer a great foot up. But before we get to visual display we need to know what player version we are targeting. And to do that, we have to hit the time machine button and roll back all the way to Flash 4.....

The Following code should be exported as a Flash 4 ActionScript 1 .swf. This will ensure it can run on the broadest client base. The resultant .swf acts a cross platform redirect that should work within both stand alone and browser based flash clients. Once the .swf loads it will identify the player variation and then redirect the viewer to the appropriate content for there player platform by loading a replacement content swf at the main player level.

 
/**
Declare flash platform player strings here. As more devices are discovered this list will grow, the strings are from the getVersion() function
*/
// FlashLite 1.1 player platform string
FL1PLATFORM = "5.2";
// FlashLite 2 or 3 player platform string
FL2PLATFORM = "FL ";
// psp Flash Player Platform string
PSPPLATFORM = "NF3";
// Wii Player Platform String
WIIPLATFORM = "WII"
// windows Flash Player Platform string
WINPLATFORM = "WIN";
// mac Flash Player Platform string
MACPLATFORM = "MAC"
/**
Declare files names for flash files of different device configurations
NOTE! Include the full path name here
*/
flashLite1 = "fl_fl1.swf";
flashLite2 = "fl_fl2.swf";
flashLite3 = "fl_fl3.swf";
flash6PSP = "flash6PSP.swf";
flash7WII = "flash7WII.swf";
flashFull8 = "FullFlash8.swf";
flashFull9 = "FullFlash9.swf";
// get the player version
flashVersion = getVersion();
// display full player information
trace(flashVersion);
// test for existence of player version for very early players
if(flashVersion == "")
{
	/*
	Player does not support $version so is VERY early Flash PLayer
	Decide how you wish to handle this case here
	*/
}
// crop the player version to store the platform
playerPlatform = substring(flashVersion, 0, 3)
// Assign a player version for testing
// playerPlatform = PSPPLATFORM;
// display platform information
trace("playerPlatform");
trace(playerPlatform);
// use flashLite 1.1 file
if(playerPlatform eq FL1PLATFORM)
{
	// launch a FlashLite 1.1 version of the file.
	trace("Launch FlashLite 1.1 player version");
	loadMovie(flashLite1, "_level0"); //+"?stgWidth="+Stage.width+"&stgHeight="+Stage.height);
}
else
{
	if(playerPlatform eq PSPPLATFORM)
	{
		// launch a PSP or Flash 6 version of the file
		trace("Launch PSP player version");
		loadMovie(flash6PSP, "_level0"); //+"?stgWidth="+Stage.width+"&stgHeight="+Stage.height);
	}
	else if(playerPlatform eq WIIPLATFORM)
	{
		// launch a PSP or Flash 7 version of the file
		trace("Launch WII player version");
		loadMovie(flash7WII, "_level0"); //+"?stgWidth="+Stage.width+"&stgHeight="+Stage.height);
	}
	else if(playerPlatform eq FL2PLATFORM)
	{
		// grab the player version number for flash lite
		playerVersion = substring(flashVersion, 4, 1);
		// display version information
		trace("playerVersion");
		trace(playerVersion);
		if(playerVersion == "7")
		{
			// launch a FlashLite 2 version of the file.
			trace("Launch FlashLite 2 player version");
			loadMovie(flashLite2, "_level0"); //+"?stgWidth="+Stage.width+"&stgHeight="+Stage.height);
		}
		else if(playerVersion eq "8")
		{
			// launch a FlashLite version of the file.
			trace("Launch FlashLite 3 player version");
			loadMovie(flashLite3, "_level0"); //+"?stgWidth="+Stage.width+"&stgHeight="+Stage.height);
		}
	}
	else if((playerPlatform eq WINPLATFORM) || (playerPlatform eq MACPLATFORM))
	{
		// grab the player version number for desktop player
		playerVersion = substring(flashVersion, 5, 1);
		// display version information
		trace("playerVersion");
		trace(playerVersion);
		if(playerVersion == 8 )
		{
			// launch a desktop version 8 of the file.
			trace("Launch desktop player version");
			loadMovie(flashFull8, "_level0"); //+"?stgWidth="+Stage.width+"&stgHeight="+Stage.height);
		}
		else if (playerVersion == 9 )
		{
			// launch a desktop version 9 of the file.
			trace("Launch desktop player version");
			loadMovie(flashFull9, "_level0"); //+"?stgWidth="+Stage.width+"&stgHeight="+Stage.height);
		}
	}
}
stop();
 

The below zip includes the full source and example 'redirection' movies. If you have any other Client version strings that can be added please let me know and I will try and keep the script updated. For example I would love to know what the Sony Ericcson Java client version reports.

Identiying Flash Client Versions

However the MackBook black uses the mini DVI connector, as a result I thought it would be a snap to just pick up a Mini DVI to CVI connector, and then from there I could use the DVI to VGA connector I already own. Not so. Despite the packaging suggesting otherwise, the DVI result from the apple mini DVI connector is not a standard DVI out. There are 4 pins "missing". The pictures Below explain better.

All you need to do is open the apple script editor.

"/Applications/AppleScript/Script Editor.app"

Then paste a similar line of code to the commands that Macca and Anders mentioned:

do shell script "ifconfig fw0 down" with administrator privileges
do shell script "ifconfig fw0 up" with administrator privileges and password
do shell script "/System/Library/StartupItems/CiscoVPN/CiscoVPN  restart" with administrator privileges and password

Feel free to run the apple script to test it, just note you will be asked for an administrator password for the script to run.

Once you are happy you should compile and save the script to keep it safe, or "save as" and choose application. Alternatively, you could just download the AppleScript Fix for the "Error 51: Unable to communicate with the VPN subsystem" problem, that I have pre compiled as an application.

Credit where its due.
Ian Talks Tech for jogging the grey matter.
Anders.com for solving my problems when I had them.
Apple for showing me how to do shell scripts in Apple Script.

My session is scheduled for Friday afternoon.

Flash Video Nokia Masterclass - Dave Williamson (Adobe)Learn how to create live video applications with the most popular online video format on Nokia devices.

Over the Air is all sold out now, but you can find all the information about the event over at the Over the Air Blog

I look forward to catching up with you if you are there.

PlayerVersion: FL 8,1,55,0

You can see a FlashLite version test movie here..

Related to this I found myself in the situation where the Nokia Software Updater would not allow me to install the new firm ware, my t-mobile branded phone was just such a device. A quick search and it seems that devices on certain service providers are locked from the update. However there are always round such restrictions. Below is how to modify your Nokia N95 product code so that it is unlocked for applying new firmware updates.

WARNING THIS PROCESS MAY BRICK YOUR PHONE, VOID YOUR WARRANTY AND ANY NUMBER OF OTHER TERRIBLE THINGS. DO NOT DO THIS IF YOU ARE IN ANYWAY UNSURE OF THE CONSEQUENCES. I ACCEPT NO RESPONSIBILITY FOR ANY NASTY THINGS THAT HAPPEN TO YOU, YOUR DEVICE OR ANY ACTION YOUR SERVICE PROVIDER TAKES AFTER FOLLOWING THESE LINKS AND INSTRUCTIONS

That said, I only had one minor hiccup in the whole process, and it seems I am not the only one to have experienced it. I for got to mention that to Mike on MSN

Right with that out the way, on to the fun.

1. First off BACK UP YOUR DEVICE! make sure you have a back up of the memory card and also the device memory.
2. In order to install the new 21.0.016 firmware you will also want to make sure you have the following software.

* Download the latest version of Nokia PC Suite.
* Download the Nemesis Service Suite.

3. Next read this post, it provides a list of the available product codes for the N95.
4. Finally you should make sure you read this post, it covers how to update the product code on the N95.

As I began to progress through the steps outlined on changing the product code of my Nokia N95 mobile phone there were a couple of items where I was left to 'take a leap of faith'.

1. When installing Nemesis Service Suite I left the device connection as the default virtual USB device. And that seemed to be the right thing to do.
2. When deciding on a new product code for the device I chose the one for EURO1 Plum, this appears to have worked fine for my location and device. I have a silver/grey Nokia N95 and am based in the UK.

Once the product code was updated on the mobile phone the Nokia Software Updater worked fine to allow me to upgrade to the latest 21.0.016 firmware.

Curse my slow blogging skills, beat to the post.

Well, you really believe that Flash is synonymous with the internet and frankly, anybody who wants to browse the web and experience the web's glory really needs Flash support. We were very excited about the announcement from Windows Mobile, adoption of Flash on their devices and the fact that we've shipped 0.5 billion devices now, non-PC devices. So we are also committed to bringing the Flash experience to the iPhone and we will work with Apple. We've evaluated the SDK, we can now start to develop the Flash player ourselves and we think it benefits our joint customers. So we want to work with Apple to bring that capability to the device.

If the mountain wont move to you..

Go Adobe!

Read the full ZDnet article here
Read the SeekingAlpha transcript here

A customizable dashboard, multi-file upload, built-in galleries, one-click plugin upgrades, tag management, built-in Gravatars, full text feeds, and faster load times

If you are interested in giving the release candidate a test run, probably in a test environment I would think at this stage, You can download WordPress 2.5 here.

Read the Full Press Release here

The Lightroom team have posted an announcement that Lightroom and Camera Raw have both been updated. According to the post the update wont filter through the Adobe Update system until next week, so if you want to get the update early you can find them on the adobe site and download them manually.

download Lightroom 1.4 Update for Macintosh
download Lightroom 1.4 Update for Windows
download Camera Raw 4.4 Update for Macintosh
download Camera Raw 4.4 Update for Windows

The full post detailing the changes in the updates to Lightroom and Camera Raw are here

Before we get into the main instruction, I want to highlight some points.

1. [[** UPDATE **]]
   See this comment Sorry I was wrong, thank you for clearing this up
   [[** UPDATE **]]
   Currently the Mac version of TrueCrypt does NOT support hidden volumes, so if you need data to be available on Windows, Mac and Linux, you will have to forgo hidden encrypted volume functionality for the time being. Remember hidden TrueCrypt volumes you have previously created will NOT work on Macintosh computers.
2. Currently the Mac version of TrueCrypt only seems to support the FAT file system. This is actually pretty logical . There is no native support for NTFS on Macintosh computers yet. If you already have a Windows based NTFS formatted encrypted volume, you may want to set up a new encrypted volume and format it to FAT so that you can mount the volume on multiple operating systems.
3. Remember you will need to download the latest version of TrueCrypt

Below the fold is the full step by step instruction on how to create a free, portable, cross platform encrypted drive using TrueCrypt. The encrypted volume you create should allow you to move a secure encrypted file across windows, macintosh and linux computers. As long as you have the TrueCrypt application with you on something like a USB drive or TrueCrypt is pre-installed on your target computer you should be able to mount your encrypted file as a standard drive.

So off we go!!

1. Open TrueCrypt on your machintosh OS X computer.

   

   This is the default screen for TrueCrypt on os x

2. Click create volume.

   

   Although you are asked if you would like to create a 'Hidden TrueCrypt Volume' the macintosh OS X version currently only supports standard TrueCrypt volumes.

3. Select or create a new file that will be replaced to become your TrueCrypt Volume.

   

   In this case I have created a new file, one point to note is my choice in file extension. You could choose any extension to disguise your TrueCrypt volume, I have chosen teh file extension for Microsoft Power Point files, I know from experience these files can get pretty large, something that should help avoid the file drawing undue attention.

4. Set the size of your TrueCrypt Volume.

   

   While it is easy to put in a nice whole number as your TrueCrypt Volume size, its unusual to see large files of nice rounded file sizes, think about mixing it up a bit!

5. Select the encryption Algorithm that will be used to encrypt the data in your TrueCrypt volume.

   

6. Select the Hash Algorithm that will be used to encrypt the data in your TrueCrypt volume.

   

7. Select a password to secure your TrueCrypt volume.

   

   Make your password a good one, if the data is worth protecting then a weak password will only let you down, TrueCrypt will warn you if your pass word is to weak. I have actually given up devising new passwords, I let the handy cross platform password application, KeePass, generate passwords for me.

8. Select the File System that will be used to mount your TrueCrypt volume.

   

   You can currently only use FAT file system format, but thats what we want for cross platform support.

9. Provide random seed for encrypting your TrueCrypt volume.

   

   Wiggle that mouse good!!

10. TrueCrypt will then format your TrueCrypt volume.

    

11. Your true crypt volume has been created.

    

12. Mount you new TrueCrypt Volume.

    

13. Add a file to your TrueCrypt volume.

    
    In my case I have simply taken a screen grab of my desktop as an example

14. Copy move or make availible to windows machine. Here I am using a VMWare fusion shared directory between mac os x and my Windows XP apple bootcamp partition. Open TrueCrypt on windows machine.

    

    This is the default screen for the TrueCrypt application on Windows based computers, it is similar to the Macintosh interface.

15. Mount you new TrueCrypt Volume.

    

16. Using a PPT (powerPoint file extention) results in a warning.

    

    Although using the .ppt Microsoft Power Point file extension presented no issue under OS X, the windows version of the TrueCrypt application gives you a warning that anti-virus software may impact performance of the encrypted drive.

17. View your new mounted TrueCrypt volume containing your test file from Mac OSX on your Windows machine.

    

    Ta Da!! my screen grab that was encrypted on the Macintosh OS X operating system, survives to be decrypted on my Windows XP Boot Camp partition.

For best results I would recommend keeping the Windows, Linux and Macintosh version of TrueCrypt on a USB drive along with your data. At least then you will have no problem accessing the encrypted data you store, wherever you store it :D.

Personally I find this new version wonderful. My previous cross platform encryption solution was to use bcrypt a command line application availible for both Windows and Mac OS X, however this was really only useful for file encryption. Alternatively I could use an encrypted drive image in OS X, But then this was no use if i needed the files on my Windows machine.

True crypt 5 allows a user to set up an encrypted volume that can be mounted as a drive, in the same way as an OS X drive image, only now of course its cross platform, and if you run truecrypt in traveler mode, its portable too! Bonus!

In addition if you happen to have a Linux box, or maybe one of the shiny new Nokia Internet Tablets you 'should' also be able to run TrueCrypt 5 on those as well, TrueCrypt has supported Linux for a while I believe.

You can Download TrueCrypt here.

Initially available for Internet Explorer Mobile on Windows Mobile 5 and 6 devices, mobile web app developers have already started integrating Gears for mobile into their online services.

also

if you're not a Windows Mobile user, stay tuned -- we're working to roll out Google Gears for other platforms with capable web browsers, including Android.

you can find out more at the Google Gears on Mobile Devices developer site.

Separately, today came news from Nokia that they are to add support for Silverlight on S60 and Series 40 devices on Symbian OS and Nokia Internet tablets.

This is an important relationship on so many levels. Working with Nokia means we are easily able to reach a huge number of mobile users, including customers of all S60 licensees. This is a significant step in gaining broad acceptance for Silverlight and ensuring it is platform agnostic. This is critical since we want to make sure developers and designers don't have to constantly recreate the wheel and build different versions of applications and services for multiple operating systems, browsers and platforms

said S. Somasegar, Senior Vice President of Microsoft's Developer Division.

Exciting times ahead

credit where its due:

• cellular-news - Nokia Adds Support for Microsoft Silverlight to Their Handsets
• Google Mobile Blog - Shifting Google Gears to mobile

Get more from your handset with fring’s new flash fringME! widget and stay connected with your internet communities while on the go! With the fringME! widget placed on your website or blog (i.e. myspace page), your web visitors can fring you at anytime, enabling you to stay connected even when you’re away from your PC.

With fringME!, your online buddies will now be able to:

• chat with you from fringME! on the web direct to fring on your mobile – even if they don’t have fring
• see where you are. You can choose for fringME! to show your location via Google Maps using your GPS-enabled phone
• view your online presence status - and see if you’re online, offline or in a call

Download the new Fring version 3.3 for mobile chat

One of the most enjoyable features of FlashLite 1.1 is its (lack of) ability to measure the height, width or any metric of text once it is displayed on the screen of your shiny new Nokia N95. This makes efficient text scrolling a particular joy to produce. To this end I have produced a simple example of a fairly flexible scrolling text component for FlashLite 1.1.

Below is a comprehensive (hopefully) tutorial describing how to create such a component.

Creating the component project
The first thing to do is to create a new FlashLite file, in this tutorial I have based the development on a QVGA mobile phone, such as the N6110 or N95. To do this simply set the stage size to a width of 240 pixels and the height to 320 pixels. I haven't altered the default frame rate. In the flash publish settings "File > Publish Settings" set the Flash version to FlashLite 1.1, this will automatically set the ActionScript version to 1.0 (is there a 1.anything else?) after that we are good to go!

Creating the scrolling text field

1. Create a new symbol in your Library and name it "TextArea".
2. On the stage of this symbol create a dynamic text field with a width of about 220 pixels and a height of 280 pixels.
3. With the text field selected put "text" in the Var field in the properties inspector. We will use this later to assign text to the field, remember no instance names on text fields in FlashLite 1.1.
4. Next create a new symbol in your Library and Name it "ScrollingTextArea".
5. On the stage of this symbol drag an instance of your "TextArea" symbol and position it to position X:0 and Y:0 and give it an instance name of "textArea_mc", for clarity you should name the layer this instance sits on "TextArea" or you might prefer "textArea_mc".
6. Add a new layer to your "ScrollingTextArea" symbol and name it "ActionScript". On this layer in frame 1 add the ActionScript command stop();.
7. Create a new layer folder and name it "CallFunctions".
8. Inside the "CallFunctions" folder create a new layer and call it "init", on this new layer create a blank key frame on frame 2 and give it the frame label "init".
9. On the new "init" frame add the following code that will be used later to initialise our scrolling text field.

   
// store maxScroll Locally
maxScroll = textArea_mc:text.maxscroll;
// if max scroll is greater than 1 we know we need the text to scroll
if(maxScroll > 1)
{
// store the current scroll position loccally
currentScroll = 1;
// set scrollPercent to 0.
scrollPercent = 0;
//set the scroll bar height to the height of the text field
scrollBar_mc.trackHeight = textArea_mc._height;
//set the scroll thumb height
scrollBar_mc.thumbHeight = 30;
// init the scroll bar
call("scrollBar_mc/:Init");
// show the scroll bar
scrollBar_mc._visible = true;
}
// otherwise hide the scroll bar, its not needed.
else
{
scrollBar_mc._visible = false;
}


   At this stage most of the values in this code block will not function, but they will be required in a later step.

10. Inside the "CallFunctions" folder create a new layer and call it "setText", on this new layer create a blank key frame on frame 3 and give it the frame label "setText".
11. On the new "setText" frame add the following code that is used to populate our text field component.

    
// set the text value to the text field
textArea_mc:text = text;
// call init to reset scroll parameters
call("init");


12. Inside the "CallFunctions" folder create a new layer and call it "scrollUp", on this new layer create a blank key frame on frame 4 and give it the frame label "scrollUp".
13. On the new "scrollUp" frame add the following code that is used to scroll the text in our component up the screen.

    
// increase the text scroll
textArea_mc:text.scroll++;
// store the current scroll position locally
currentScroll = textArea_mc:text.scroll;
// if the current scroll position is the same as maxScroll scrollPercent is 100
if(currentScroll == maxScroll)
{
scrollPercent = 100;
}
// other wise calculate the percentage scroll position
else
{
scrollPercent = Math.ceil(((currentScroll-1)/maxScroll) *100);
}
// set the scroller scroll percentage
scrollBar_mc.scrollPercent = scrollPercent;
// call the scrollBar setScrollPercent function
call("scrollBar_mc/:setScrollPercent");


14. Inside the "CallFunctions" folder create a new layer and call it "scrollDown", on this new layer create a blank key frame on frame 5 and give it the frame label "scrollDown".
15. On the new "scrollDown" frame add the following code that is used to scroll the text in our component up the screen.

    
// decrease the text scroll
textArea_mc:text.scroll--;
// store the current scroll position locally
currentScroll = textArea_mc:text.scroll;
// if the current scroll position is at 1 then there is no more scrolling to be done, so scrollPercent is 0
if(currentScroll == 1)
{
scrollPercent = 0;
}
// other wise calculate the percentage scroll position
else
{
scrollPercent = Math.ceil(((currentScroll-1)/maxScroll) *100);
}
// set the scroller scroll percentage
scrollBar_mc.scrollPercent = scrollPercent;
// call the scrollBar setScrollPercent function
call("scrollBar_mc/:setScrollPercent");


16. Finally add code to frame 1 of the actionscript layer so it looks like this:

    
// by default hide the scrollbar
scrollBar_mc._visible = false;
// call the text field init function
call("Init");
stop();


Thats all there is for the development of the text field, and also for the scrolling functionality. You will notice that in our text field "scrollUp" and "scrollDown" call frames we reference a scroll bar clip, we will now create that scrollbar.

Create a simple FlashLite 1.1 scroll bar component

1. In your library create a new symbol and call it "square".
2. On the stage of your new "square" symbol draw a square with no stroke give it a width and height of 50 pixels, place the graphic at X:0 and Y:0.
3. In your library create a new symbol and call it "scrollbar".
4. Label the layer in your new "ScrollBar" symbol "scrollTrack". Bring an instance of the "square" symbol on to this layer and position it at X:0 and Y:0 change the symbol instance's with to 10 pixels and its height to 100 pixels. Also give the instance an instance name of "scrollTrack_mc" and apply a colour tint of your choice.
5. Create a new layer above the "scrollTrack" layer name this new layer "ScrollThumb" and add another instance of your "square" symbol to it.
6. This time set the instance name to "scrollThumb_mc". Position it at X:1 and Y:1. Set the new "scrollThumb_mc" width to 8 pixels and its height to 50 pixels. Again apply a colour tint, making sure it is different to the one you applied to the "scrollTrack_mc" instance.
7. Add a new layer and name it "ActionScript". In frame 1 of this new layer add the following code:

   
// call the scroll bar init function
call("init");
stop();


8. Create a new layer folder and name it "CallFunctions".
9. Inside the "CallFunctions" folder create a new layer and call it "init", on this new layer create a blank key frame on frame 2 and give it the frame label "init".
10. On the new "init" frame add the following code that will be used later to initialise our scrolling scroll bar.

    
// apply padding to the scroll thumb
scrollPadding = 1;
// call the set scroll height function
call("setScrollHeight");


11. Inside the "CallFunctions" folder create a new layer and call it "setScrollHeight", on this new layer create a blank key frame on frame 3 and give it the frame label "setScrollHeight".
12. On the new "setScrollHeight" frame add the following code.

    
// resize the scroll track
scrollTrack_mc._height = trackHeight;
// resize the scroll thumb
scrollThumb_mc._height = thumbHeight;
// set the tscroll thumb position to the padding value
scrollThumb_mc._y = scrollPadding;
// store the max scroll position
maxScroll = (trackHeight - thumbHeight);


13. Inside the "CallFunctions" folder create a new layer and call it "setScrollPercent", on this new layer create a blank key frame on frame 3 and give it the frame label "setScrollPercent".
14. On the new "setScrollPercent" frame add the following code.
    
// set the scroll position based on a percentage value using math.
scrollThumb_mc._y = Math.max(((maxScroll*(scrollPercent/100))-scrollPadding), scrollPadding);


This completes the development of the simple scrollbar component, all you need to do is to add it to the "ScrollingTextArea" clip we created earlier.

1. Return to editing the "ScrollingTextArea" symbol in the library. Add a new layer above the "TextArea" layer and name it "ScrollBar".
2. Drag an instance of the SrollBar symbol out onto the new layer. Position the new instance at X:225 and Y:0.
3. Give the new ScrollBar instance an instance name of "scrollBar_mc".

This completes the development of the scrolling text field component. All that remains is to show how it can be used within a project. To do this we need to add the scrolling text field to the stage of the main time line, add some ActionScript to populate the text field component, and then add a key press handler.

Completing the project

1. Re-name the layer "Layer 1" on the main movie time line to "textArea".
2. Drag an instance of our "ScrollingTextArea" clip onto the new "textArea" layer. Position the new instance at X:0 and Y:19. Give the new instance an instance name of "scrollingText_mc".
3. Create a new Layer above the "textArea" layer and name the new layer "ActionScript". On frame 1 of this layer add the following code:

   
// dummy text to populate our text field
textVar0 = "Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Fusce non urna. Ut leo metus, euismod non, semper et, ultrices at, nisl. Fusce non orci vitae dui blandit sagittis. Vestibulum laoreet feugiat leo. Suspendisse malesuada. Maecenas ultricies fermentum mi. Proin nulla. Mauris at dolor a nisl cursus congue. Maecenas id justo tincidunt augue molestie commodo. Donec nec metus eu tellus cursus mollis. Cras justo. Nunc sapien arcu, luctus id, porta sit amet, ultrices non, metus. Donec cursus. Aenean eleifend facilisis odio. Sed suscipit, odio eu fringilla ornare, eros metus eleifend quam, eget facilisis nulla turpis at tellus. Ut et massa a est faucibus fringilla. Nam nisl magna, condimentum non, lobortis et, porta non, ipsum. Aliquam ultricies augue sed urna. Sed ligula magna, vehicula at, scelerisque id, luctus eget, tortor. Donec aliquet purus ut neque.\n\nCras porttitor facilisis sem. Praesent cursus nulla euismod lorem. Donec vitae nunc. Quisque nec quam. Integer nonummy nisl vel mauris. Aliq\n\nam sed felis eu risus scelerisque scelerisque. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Sed tortor nisl, sodales et, eleifend sed, porta eget, urna. Sed adipiscing dolor sit amet dolor. Vestibulum fermentum lorem quis nulla. Donec id ligula. Suspendisse potenti. Aenean ac quam quis sapien sollicitudin dapibus. Cras vitae neque nec ante pharetra hendrerit.\n\nDonec ante lectus, gravida non, nonummy et, pulvinar ut, lectus. Ut sem nisi, dapibus non, scelerisque at, convallis sit amet, dolor. Cras vitae velit et lectus rhoncus ullamcorper. Sed sodales adipiscing tortor. Curabitur non dui ut ligula laoreet mattis. Ut vitae lacus quis enim placerat tristique. Donec ornare mauris eget sem faucibus lacinia. Vestibulum hendrerit diam et neque. Vestibulum imperdiet. Maecenas tincidunt felis vitae lectus. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Nam suscipit hendrerit felis. Mauris convallis elit vel justo. Nulla facilisi. Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Etiam vel mi. Phasellus ultrices porta felis. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos hymenaeos. Ut sed metus vel erat ultricies egestas. Pellentesque et ligula.";
// alternate dummy text to try, this should hide the scroll bar
textVar1 = "Test Text";
// set the text var we want assigned to our text field
scrollingText_mc.text = textVar0;
// call teh set text function on our scrolling text field
call("/scrollingText_mc/:setText");
stop();


This provides some dummy text with which to populate the text field component that has been developed, it then assigns one of the text variables to the components "text" value, and calls the "setText" function in the call frame of the scrolling text field component.

At this point you could export and test the movie, you should see the field is populated, and the scroll bar is correctly scaled and displayed to indicate that the text will scroll. Finally we create the controls to make the textscroll.

1. Create a new button in your library and call it "keycatcher".
2. In the "up" frame of this button I have put simple text label with the string "KeyCatcher" so I can identify the symbol on stage.
3. Return to the main timeline and create a new layer above the "textArea" layer, name this new layer "KeyCatcher".
4. Drag an instance of the "keycatcher" button onto the stage on this new layer. Position it off stage at X:-110.0 and Y:0.
5. With the "keycatcher" button still selected add the following key handling code to the button:

   
// assign our down key press handler
on (keyPress "")
{
// only cal the scroll function if the test is not at its maximum scroll
if(scrollingText_mc.currentScroll < scrollingText_mc.maxScroll)
{
call("scrollingText_mc/:scrollUp");
}
}
// assign our up key press handler
on (keyPress "")
{
// only cal the scroll function if the test is not at its minimum scroll
if(scrollingText_mc.currentScroll > 1)
{
call("scrollingText_mc/:scrollDown");
}
}


All that should remain is to save, export and test you new component in Device Central.

Download the source files of the scrolling text component for Adobe FlashLite 1.1

NOTE: If you have used embedded fonts in your text area and are seeing no text appearing, try using device fonts (non embedded) instead. Apparently there is a know isue with Flash CS3 exporting embedded fonts in FlashLite 1.1 swf files that are viewed in Device Central. More information is discussed briefly on the Adobe Device Central forums

Credit where its due:
Into Mobile
Internet Tablet Talk
Tablet Blog