Greg Burch has made a post on some things to watch out for when using Object.registerClass to set the type of an object to a custom class.
The same thing applies on the Flash Communication Server when using application.registerClass. The constructor for your class must be in this form:
function MyClass(){};
Doing this on the client and server allows you to send custom classes between the client and server and have them automatically serialized and deserialized. This is a very cool feature.
We have updated the Flash Communication Server components, adding some new components bringing the total up to 14 total components.
Among others, there is a whiteboard component that is pretty cool.
You can find a complete list, as well as download the components here.
We have posted a new Technote on how to work with logging in the Flash Communication Server. Aside from a lot of information, it also comes with a tool to allow you to read the logs.
You can view the technote here.
O’Reilly has posted a good introduction / discussion of using Flash on Devices. It discusses the advantages of using Flash on devices, and has quite a few links to resources.
You can read the article here.
Registration for Macromedia DEVCON 2002 is now open. It is October 27 - 30 in Orlando Florida, and includes tons of sessions and other events. I will be there doing some sessions on advanced Flash Remoting and Security within Flash.
Notice that you can register using HTML, or a Flash Application. There is also a Flash based Agenda Builder that you can use to help you plan your agenda for the conference.
I have been writing some Flash Communication Server code (on the server side), and had a need to connect methods and properties to the Client object. Normally, I would use _resolve so i would not have to attach methods directly to the Client object, but doing that would mean that my code could not work with the Flash Communication Server components, which also define _resolve.
The solution, was to create a namespace on the Client object and store my data there.
Guy Watson (aka FlashGuru, or is it the otherway around?) has started a discussion on charging for components. Very interesting read, and a topic that is sure to come up again and again as more advanced components are developed.
You can read the post and comments here.
Opinion : When you consider the amount of work that goes into a well designed and built component, and the amount of time and money it can save you in multiple projects, I really have no problem paying for something that i need to use. But in return, i expect high quality product and documentation.
We have published some new Flash MX resources at the Designer and Developer Center. Not as much Flash content as usual, but we have launched a number of new topic pages for:
Here is the Flash related content:
Check them out.
We have posted what I think is a very cool Flash application / documentary, titled “Macromedia, The Story”, that goes over the 10 year history of Macromedia.
On a related note, you can find a list of links on the history of Macromedia Flash here.
[via ericd]