Archive for September, 2006

Flash 9 public alpha

Sunday, September 24th, 2006

I’ve been tryin to avoid AS 3.0, as I’ve been knee deep in Flash 4 syntax for the past two years, but over the past week I’ve managed to get caught up with Flex 2. Quite frankly I’m in love, not having Flex builder available for mac has put me off until I read this post by Josh Buhler and installed the SDK to use with Xcode and within 10 minutes I had my very first Flex application. So after a few breezos and a weekend of trawling through the docs on Adobe Flex dev centre I came across Flash 9 public alpha for AS 3.0 preview over at Adobe Labs.

It’s been around since the end of July but I haven’t seen it until now.

Flash 9

Q. When is passive content not passive content?

Tuesday, September 19th, 2006

A. When it’s bundled with active content.

So I finally got my ACS publishers ID from verisign, and as I thought the next step is to follow the instructions to download your certificate and replace it for the developers *.cert file we used to create a dev .sis for testing.

So I finally had my .sis signed with an ACS publishers ID and everything, all that was left to do was to upload my application through the Symbian signed website it’s fairly self explanatory, but in the interests of documenting everything I’ll blog that too at a later date.

Onto the passive / active saga

A day or so after I submitted my application I received this response from the testing house:
We have received your application and for your interest, we performed a free
basic check for it.

During the basic check, we observed that the application needs connect to
network but privacy statement for it is missing.

According to Symbian Signed criteria (CON-02), there are two display modes
for Privacy Statement as following and either of them can meet the Symbian
Signed criteria,

Mode 1: Privacy Statement is displayed at the first ever launch of the
application and after user confirmed the statement, it will not prompt again
for subsequent runs.

Mode 2: A checkbox can be made available in Privacy Statement to enable the
user to disable the prompt for subsequent runs. Or a query dialog text can
be used instead of the checkbox.

Following is Best Practice for privacy statement,

TITLE: For your information

BODY: This application will make use of the following features of your
phone. If you have any questions or concerns, please contact us at


e-mail address>:

Bluetooth to connect to other Bluetooth-enabled devices
Sending SMS messages
Sending MMS messages
Making phone calls
Making a connection to the Internet
Allowing you to add or edit contacts
Reading existing information from your contacts database
Recording sounds using your phone’s microphone

TICKBOX: Do not show me this information again

Could you please kindly have a double check?

(more…)