ZDNet UK


Skip to Main Content

ZDNet.co.uk - Winner of Best Business Website 2007
  1. Home
  2. News
  3. Blogs
  4. Reviews
  5. Prices
  6. Resources
  7. Community
  8. My ZDNet

 

ZDNet UK RSS Feeds


IT Jobs

Application development Toolkit

Tools for building Pocket PC Flash applications

John Wilker Builder.com

Published: 02 Feb 2004 15:30 GMT

  • Email
  • Trackback
  • Clip Link
  • Print friendly
  • Post Comment

In the last article about Flash on the Pocket PC platform I covered the basics of creating flash interfaces that will work and look good on the "small screen", covering the aspects of the platform that need to be considered when developing an interface or application. With this article I'll be talking about the tools used to create more advanced applications. These things aren't necessarily Pocket PC-specific, but they do work a little differently in some cases.

Shared objects
Shared objects are used in many Flash applications. Flash isn't allowed much interaction with the client's computer; there's no built-in method for creating text files, though existing ones can be read. The primary option for storing user data is to store it remotely but if the client isn't connected to the Internet that option isn't always available. If that's the case, then store the data in the only local vehicle available for client storage data: shared objects.

Shared objects are small files that Flash stores on the client computer. The shared object is specific to the application that created it. They're also not easy to find, usually residing within a hidden subfolder on the client computer.

In terms of a Pocket PC device, the shared object exists only until the next soft reset. Therefore, you can't rely on it always being there. In fact, the application you'll be looking at only uses a shared object to store data temporarily while a network connection is not available.

Creating the shared object is pretty straightforward:
1 var MyBlog = SharedObject.getLocal("blogobject");
2 MyBlog.data.Blog = new Array();

Line 1 only executes if the shared object doesn't exist. Line 2 assigns the shared object a value. You can put anything you want in your shared object; I use an array since I want to put several pieces of data in the same container. I'll address actually putting data into the shared object array later.

Next

Previous

1 2


  • Email
  • Trackback
  • Clip Link
  • Print friendly Print with Dell

Did you find this article useful?
105 out of 225 people found this useful


Full Talkback thread

0 comments

Company/Topic Alerts

Create a new alert from the list below:



Related Jobs

Test Consultant

Experience of testing engagements within a complex IT environment - Expert knowledge of formal testing processes and ability to rapidly diagnose ...

Application Developer

Develop detailed systems design and configuration including data modelling of bespoke BI and SEM objects such as info sources, info cubes, ODS ...

Tester Manager

Detailed Test Plans - Organise and manage off-shore delivery as required - Manage the relationship with other team leaders in the project - ...

Discussions

187205 187205

Companies to react to downtime

Thursday 24 July 2008, 2:51 PM

1 comment
pearce_jj pearce_jj

Defragging: Merits?

Thursday 24 July 2008, 2:19 PM

13 posts
David Long David Long

Defragging: Merits?

Thursday 24 July 2008, 10:30 AM

13 posts

Featured Talkback

The fact is: Software developers today are really designers and not coders. The reason that business anlaysts exist today to model solutions is because they understand the value of designing software before writing it. All too often developers create code that has little value because they do not understand that business classes interact with other classes within the confines of a working model or pattern.

By: 1000165269

Read full story:
Making sense of agile modelling