If you haven’t seen it now you must check go2web20.net. It’s a “complete” Web 2.0 Directory. Very useful to discover new services.
Ahmet
Sep 172006
Sep 162006
Dimdim is a Web Conferencing open source tool, still in Alpha-Version that seems to have a great future. There are a lot to say about it so I prefer to give directly the link ;)
By now it’s only work on IE and is full of bug but the idea is awesome. I guess it can be a good alternative to Breeze as they want it to be free.
Watch Dimdim demo.
Have more info.
Ahmet
Sep 152006
If like me you hadn’t the luck to be at Austin for the Flashforward, you still can gather some informations ;)
Don’t miss the Videocasts from the Flashforward blog (lot of resources).
Other various resources : Rhjr, FlashMag, A.Balkan.
I can’t wait to see the final Adobe Flash9 (early 2007) :D
Ahmet
Sep 112006
Nice interactive video made from friends at zonoff. Every hit given to the rabbit (I guess, I’m not so used to see them furless) is from your click on the video. The best is to try it by yourself!
There are some really funny video, check the archive for more ;)
Ahmet
Sep 062006
Following my first video tutorial about AS3, in this one I go a bit further with AS3 by making more function in one class and using event (when user press Enter key). The video & audio quality is a little bit better than in the first video but I’m still not totally happy with it. Better will come in the next one.
To access the first video goto my as3 tutorials page.
Or play helloworld2 video.
Ahmet
Sep 042006
In my point of view, mobile world has 3 big problematic, first is Os and Platform and the wide variety of mobile generation, second is connection cost, third is user expectation.
It’s how I see the mobile world from Switzerland, I don’t know how is it in the rest of the world but to begin :
1- You thought that web development was head breaker? Well compared to mobile web (moweb ?) it’s paradise. The standard fight in moworld is huge, there is so few directing line that for developer it’s hell. Flash Lite is still a really nice advance for cross-compatibility but here appear the problem of wide variety of mobile generation owned by the public. The Flash Lite penetration statistic is too low compared to c++ / J2ME. If we talk about Flash Lite 2.0 it’s even worst (okay it’s going better everyday) but in this very moment the market is nearly inexistent for public. The only way I see for now is to work directly with the mobile operator to embedded Flash Lite Player in their offer. From the Adobe part should work strong on an auto-update for there Flash Lite Player and obviously let it free.
2- In my point of view the future of mobile application would be like RIA in an interconnected server and mobile interface, solving so the trouble of processing and memory space. For example media (sound, video, pictures, contacts, …) shouldn’t be saved on mobile but on a streaming server, delivering the wanted stream to the user mobile. By now the price are much too high to make this interesting for user. I’ve been testing streaming this month and my mobile invoice increase from 300% ! I don’t understand mobile operator strategy to keep so high price on data transfer in GPRS/UMTS. Maybe Wi-Fi phone could help for this issue.
3- The user expectation of a mobile phone is often to be able of making phone and to make some messaging and for some games. As Paul Golding suggest in his book (Next Generation Wireless Applications) mobile phone should be called communicator. I know some people don’t even known about Visiophony nor Localisation. Now that it’s possible to watch movie, to read Ebook, to surf, to make visio call, to know our localisation and have mapping, It’s really the time to advertise and promote it!
All these point slow the development of rich mobile application, wondering how long it will take.
Ahmet
Sep 012006
Although it sound obvious once known it was quite a surprise for me.
An example is better than a long sentence :
[kml_flashembed movie="http://www.metah.ch/blog/image/fp_soClass.swf" height="250" width="430"/]
Here you can notice that to access the Size() of a SO you need :
the_so.getSize ();
but to get access to the MaxSize() of SO you need to do :
SharedObject.getMaxSize();
It just mean that you can access the size() of the _so object, but you get the MaxSize() from the SO Class.
Ahmet
