new flash chat demo support Red5 and flash media server all versions

This is my another flash chat application. I 'm just trying to bring all yahoo chat featurs in ths chat room this flash chat support all media servers like flashcom all versions, flash mediaserver and Wowza media server. This application in a test mode please visit and send your comments.

Now tested featurs

Room chat
video chat
personal chat
audio chat
emothicons support


screen shot

Websites to follow if you’re into Web Development


2. woork

3. Web Designer Wall

4. Smashing Magazine

5. Vitamin

6. Wake Up Later


8. Signal vs. Noise

9. adaptive path blog

10. Tutorial Blog

11. WebAppers

12. Web Resources Depot

13. Ajaxian


15. Design Float

16. IBM’s developerWorks

Best Sites For Good Free Stock Images

  • BurningWell - a repository for public domain (free for any use) images. Donations welcomed - anyone have any Melbourne images they could upload, Melbourne is not represented there at all!

how to applay Multiple classes to one html element

this is very simile but many of us don't know this. if you know it leave it :)

.red {color: red;}
.bold {font-weight: strong;}

This text will be red yet also bold!

how to Position an element center screen

here is a simple css code with this you can simply Position any html element to screen center

#popup { height:400px; width:500px; position: absolute; top: 50%; left: 50%;}
#popup{ margin-top: -200px; margin-left: -250px;}

How to remove the dotted border from image hyperlink

Many times, when you click on someone’s logo, you see that little dotted border around the image it very boring. here is a simple css solution for that.

a { outline: none; }

The future of Actionscript

Yesterday, a small bomb exploded among the Flash programming community - the proposed ECMAScript 4 standard will not become the next generation of Javascript. Instead, the working group have opted for a much less ambitious expansion of the existing ECMA3. To Flash developers, this means that Actionscript 3 is now based on a standard that's up in the air.

The working group named TC39 consists of major players in the web space (Mozilla, Microsoft, Apple, Opera, Google, Yahoo and others). These have worked in a committee to decide how the next version of ECMAScript shall be like. ECMAScript is the language that both Javascript and Actionscript is based on. The existing version was developed back in 1999 so an update is long overdue. Up until yesterday, the committee was split in two camps: one that wanted to do a big overhaul (ECMA4) and one that wanted to do just small changes to the existing language (ECMA3.1). The result is now that a unified committee will support the ECMA3.1 standard.

When Adobe created Actionscript 3, it was entirely based on the ECMA4 standard. At that time, this was a "draft standard", a suggestion not yet approved by a standards committee. This standard could bring to Javascript all the constructs that Flash developers now take for granted such as packages, namespaces, vectors as well as a host of other features. ECMA4 would have been a big leap forward for JavaScript, but it also required that the browser manufacturers rewrote the code executing the scripts.

Adobe wanted ECMA4 to become the new standard and to speed this process they donated the Tamarin virtual machine to Mozilla. This piece of technology is what runs at the heart of the Flash Player. With this in place, Mozilla had a lot of what was needed to support ECMA4. Other manufacturers such as Apple and Microsoft would have to write this themselves. Writing code cost money and nobody is making money from selling browsers. This and other "political" issues caused the committee to split in half.

John Resig works for Mozilla and he is kind of a demigod when it comes to Javascript. He sums up the struggles of the commitee and the results in a very sober way. His conclusion is that unity is more important than features and so thinks ActionScript 3 is not going away, and we are not removing anything from it based on the recent decisions. We will continue to track the ECMAScript specifications, but as we always have, we will innovate and push the web forward when possible (just as we have done in the past)."

Also don't forget - ECMA4 is not gone and forgotten. There is something beyond 3.1 as well as Brendan Eich points out in his mail titled ECMAScript Harmony. A committee that actually works will do a lot more work than one that's split in two. ECMA4 may get there, but it will take time. That's one of the many things you get from design by committee. In the mean time, Flash/Flex will have a cutting edge language that will continue to expand in terms of fans and features. It'll be like JavaScript could have been, if politics didn't get in the way.


JavaScript Stalled, AS3 Orphaned - Microsoft to Blame?

As you may have already read, the ECMAScript 4 standard, the standard on which AS3 is based, and the draft proposal for future versions of javascript has been rejected in favour of ECMAScript 3.1, which proposes small incremental changes to javascript for the foreseeable future.

This leaves Adobe in a somewhat awkward position. Firstly, it casts ActionScript back to being a proprietary language. Secondly, it means they have released an extremely valuable chunk of intellectual property (in the form of the Tamarin ES4 execution engine), without gaining the expected benefits for the Flash platform.

It's also very disappointing for the web at large. This decision means that Javascript will effectively stagnate, and is unlikely to become a robust language for supporting rich/complex client side applications any time soon. Had ES4 become a ubiquitous standard, I would certainly have looked at doing a portion of our work in the AJAX space. I'm sure other Flash developers and traditional programmers would have done the same. I suppose from that perspective, this could be good for the Flash platform, but I prefer competition, options, and thriving innovation.

So why did this happen? When I heard the news, I analysed it in light of who has the most to gain, and in context of previous discussions / information I've read. I guessed that the most likely reason that ES4 was dropped, was due to Microsoft. They would have to either write a new execution to support ES4 (which costs money), or swallow their "not built here" pride to use Tamarin. By crushing the standard they would avoid having to do either of these and take a stab at their rival Adobe by pulling the carpet out from under AS3's standard compliance. Being that they control 80% of the browser market, they are also one of the few groups that could unilaterally block adoption of the standard (having a standard that's only supported by 20% of browsers isn't very useful).

So to me, it looks like a power play by Microsoft. And it seems that I'm not the only one - Hank Williams over at has written an article mirroring my thoughts almost exactly.

These situations are frustrating for developers (well, for almost everyone, I imagine). Standards bodies are so hampered by politics and corporate interests, but of course they are the lesser of two evils (no one wants to return to the wild west of HTML coding). Almost makes you glad that the Flash player is a proprietary product, eh?

UPDATE: Adobe has just made their public response here. Quite candid, and definitely seems to follow the lines of my speculation with mentions of "a morass of bickering, infighting, and sometimes, out and out name calling".


PHP developer Cochin |PHP developer Kerala | PHP developer India | Flash developer/programmer Cochin | Flash developer/programmer Kerala | Flash developer/programmer India | web programmer kerala |web programmer Cochin |web programmer India |web developer kerala |Web developer Cochin | Kerala PHP | PHP freelancer| flash actionscript freelancer