Impressions on FlashLite

During these days I'm involved in my first mobile project on FlashLite...uhm...not so impressive as news!
However I would like to point out some considerations on how FlashLite looks like from a C++ developer perspective without any knowledge of authoring tools ( to be honest the only one I knew was Paint..shame on me!)
Why did I (and my team) finally come to FlashLite? Mainly because of:

1. uncertain project requirements ;
2. reduced time to set up a prototype.

These reasons seemed good enough to try to develop a first FlashLite "moke-up" application even if noboby within the team had pregress experiences.
We have limited budget so the decision was to realize the demo version using in-house resources.
I've collected some documentation, tutorials, I've installed Flash 8, and I faced the timeline for the first time!
After two weeks spent on how to use the Stage (the area where you place visual elements), how to create basic effects (transition, tween, mask) I was impressed by the possibility to create easily amazing User Interfaces.
Developing Symbian C++ applications, I really miss an environment which enables me to drag&drop elements and to create new ones; the RAD (Rapid application development) tools I tried as such as Codewarrior did not impress me positively because the code autogenerated does not fit with my coding style...but I admit that is my limitation.
The most important issue I've dealt with using FlashLite (till now!) was how to manipulate the visual elements in order to react to user inputs.
Well, Actionscript is the language to modify Flash clip, indeed you can create the whole clip using Actionscript avoiding visual elements ( aka Symbol) taken from the library. Actionscript supports Object Oriented Programming (wow...something familiar to me ) but it is not straighforward how to connect a visual element on the Stage with a class.
Even harder was to figure out how to extend a movieclip class and create a movieclip istance!

Something hard to understand is the silent fail, that is an instruction can fail but nothing happens , the execution goes on and no error is reported!

However Actionscript syntax is simple and give access to some functionalities of the operating system as such as: battery level, signal strenght, sms, phone call, data connection.
In order to send an sms only one instruction is necessary, on the other hands the same task in Symbian takes much more time.

In conclusion, FlashLite is still a demo tool easy to learn but it still suffers of important limitation, but I have a dream when I see UI designed in FlashLite, engines coded in C++ called from FlashLite as external libraries. Maybe I'm not dreaming it's just happening and we will see in the next release of FlashLite.