 | LocalServer Cache and serve application resources (HTML, JavaScript, images, etc.) locally |
 | Database Store data locally in a fully-searchable relational database |
 | WorkerPool Make your web applications more responsive by performing resource-intensive operations asynchronously |
Custom Events are not a replacement for the Event object. Its really meant to aid in the loose coupling of the Model from the Controller in your client side code. Now that you've heard my spiel. Here's the code:
CustomEvent = {};
CustomEvent.Events = {};
CustomEvent.Events.Base = Class.create();
CustomEvent.Events.Base.prototype = {
initialize: function(){
this.listeners = new Array();
},
addEventListener: function(f){
this.listeners.push(f);
},
removeEventListener: function(f){
this.listeners = this.listeners.without(f);
},
dispatchEvent: function(n, d){
var data = this.setupData(d);
this.listeners.each(function(l){
l({name : n}, data);
});
},
setupData: function(d){
return $H(d);
}
}
CustomEvent.EventController = Class.create();
CustomEvent.EventController.prototype = {
initialize: function(){
this.events = new Hash();
},
create: function(n, t){
var args = arguments[2]?arguments[2]:null;
this.events[n] = new Event.CustomEvent[t](args);
},
addEventListener: function(n, f){
this.events[n].addEventListener(f);
},
removeEventListener: function(n, f){
this.events[n].removeEventListener(f);
},
dispatchEvent: function(){
var n = arguments[0];
var d = arguments[1] ? arguments[1] : {};
this.events[n].dispatchEvent(n, d);
},
destroy: function(n){
this.events.remove(n);
}
}
var EventController = new CustomEvent.EventController();
EventController.create("test", "Base");
EventController.addEventListener("test", myTest);
function myTest(evt){
alert('Event Name: '+evt.name);
}
EventController.dispatchEvent("test");
<?xml version="1.0" encoding="utf-8"?>
<mx:ApolloApplication xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute">
<mx:Style>
.main{
top:0;
left:0;
bottom:0;
right:0;
}
.address{
top:0;
left:0;
}
.content{
top:50;
left: 30;
right: 30;
bottom: 10;
}
</mx:Style>
<mx:Model id="browserObj">
<root>
<location></location>
</root>
</mx:Model>
<mx:Script>
<![CDATA[
private function updateLocation(_loc:String):void{
trace('Address: ' + _loc);
browserObj.location = _loc;
trace('HTML Page Location: ' + htmlPage.location);
}
]]>
</mx:Script>
<mx:Panel styleName="main" label="Apollo Browser">
<mx:HBox>
<mx:ComboBox id="protocol">
<mx:dataProvider>
<mx:Array>
<mx:String>http:// </mx:String>
<mx:String>https:// </mx:String>
<mx:String>ftp:// </mx:String>
</mx:Array>
</mx:dataProvider>
</mx:ComboBox>
<mx:TextInput id="address" styleName="address" text="http://www.google.com/" />
<mx:Button label="Go!" click="updateLocation(protocol.selectedItem + address.text)" />
</mx:HBox>
<mx:HTML height="{this.height - 100}" id="htmlPage" styleName="content" location="{browserObj.location}" />
</mx:Panel>
</mx:ApolloApplication>
After I read this post, all I was left with were questions.Silverlight
In the end, the deciding factor for most developers will be the server-side language of their choice. But one things for sure, there will be an interesting battle ahead.
Programming
Business
