Luis F. Majano » Flash Forms http://luismajano.com Computer Engineer Wed, 18 Jan 2012 06:17:25 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 Flash Forms Illegal usage of actionscript http://luismajano.com/2005/10/18/Illegalusageofactionscript/ http://luismajano.com/2005/10/18/Illegalusageofactionscript/#comments Tue, 18 Oct 2005 00:00:00 +0000 Luis Majano http://www.luismajano.com/ <cfsavecontent variable="ShowAlert">
//create the alert alert("Do you wish to delete the selected file.", "Warning", mx.controls.Alert.YES | mx.controls.Alert.CANCEL, myClickHandler);
</cfsavecontent>

<cfform name="myform" height="200" width="400" format="Flash" timeout="100">
    <cfformgroup type="hbox">
       <cfinput type="Button" name="myBtn" onClick="#showAlert#" value="Show Alert" />          
   </cfformgroup>
</cfform> Simple. However, no compilation, nothing, nada. Well, since it was a parsing error and an invalid actionscript command. It got me thinking, hmmm, maybe the parser does not like the word: Delete in any string, not even commands. TADAAAA!!! We see the light. The parser doesn't even read actionscript commands, but the whole actionscript, parsing for these keywords and throws an error. I was even getting errors by naming my button: button_delete So there you go, when you receive this compilation errors, make sure that you check your "name" values and your actionscript for reserved words.]]> I have been recently using flash forms in several different locations of my new Textus Coldfusion framework which I have been developing for work. I will soon be placing entries about Textus, to give you an insight into this simple but powerful coldfusion framework.

Anyways, I have been implementing a backup system on Textus and decided to use flash forms to populate a cftree with the backups directory contents. Then from here I can open/delete files. What seemed strange was all these errors I kept receiving, that seemed totally out of place, since my code was straightforward. These were the errors:

Illegal usage of actionscript org.apache.oro.text.regex.Perl5Pattern@1e3621b.

The following actionscript commands are not allowed: “import, new, delete, createChild, loadmovie, duplicateMovieClip, AttachMovie, registerclass, createTextField, __proto__, uiobjectdescriptor, createclassobject, createemptyobject, createchildatdepth, createchildren, createclasschildatdepth, createobject, createchild, webservice, httpservice, remoteobject”.

]]> http://luismajano.com/2005/10/18/Illegalusageofactionscript/feed/ 2 NetDebugger and CF Flash Forms http://luismajano.com/2005/09/02/netdebuggercfflashforms/ http://luismajano.com/2005/09/02/netdebuggercfflashforms/#comments Fri, 02 Sep 2005 00:00:00 +0000 Luis Majano http://www.luismajano.com/ <cfinput type="button"       
       name="button_hello"
       value="Say Hello"
       onclick="#sayhello#"> The "sayhello" variable holds the remoting call:
<cfsavecontent variable="sayhello">
//NetDebuggin ON, That was simple var debug:Boolean = mx.remoting.debug.NetDebug.initialize();

//create gateway connection var connection:mx.remoting.Connection = mx.remoting.NetServices.createGatewayConnection("http://www.luismajano.com/flashservices/gateway/");
//declare service var myService:mx.remoting.NetServiceProxy;
//Create response handler var responseHandler = {};

responseHandler.onResult = function( results: Object ):Void {
alert(results);
}

//function that receives any error that may have occurred during the call responseHandler.onStatus = function( stat: Object ):Void {
//if there is any error, show an alert alert("Error while calling cfc:" + stat.description);
}

//get service myService = connection.getService("utilities.hello", responseHandler );

//make call myService.sayHello();
</cfsavecontent>
And there you go, the NetDebugger will now work. That was a lot of research for one line. Please let me know if you have any other ways of enabling debugging. Thanks.]]> This entry is to enlighten those who need to enable the Flash Remoting NetDebugger using CF Flash Forms. By default, coldfusion has the flex debuggin off, so you either have to tweak the flex settings or programmatically activate the debugging.

I would not recommend the first solution on a production environment, due to the nature of somebody peaking in to your requests and responses. However, for development is fine. So to start, find the following file: flex-config.xml which can be found under the following directory:

{CF_ROOT}/WEB-INF/cfform/flex-config.xml

Open the xml file and locate the following section:

<!– When production-mode=true, the debugging options are always
false and may not be set. –>
<debugging>

<!– allow override of values in debugging section via
query parameter on a per-request basis, if applicable –>
<process-debug-query-params>true</process-debug-query-params>
……
</debugging>

This is the flex debuggin configuration. So in order to activate the debugger change the following entries to true.

<!– turn on debug to see the request and response on the server side as well
as debug information in client side tracing –>
<remote-objects-debug>false</remote-objects-debug>

<!– turn on debug to see the request and response on the server side as well
as debug information in client side tracing –>
<web-service-proxy-debug>false</web-service-proxy-debug>

<!– turn on debug to see the request and response on the server side –>
<http-service-proxy-debug>false</http-service-proxy-debug>

]]> http://luismajano.com/2005/09/02/netdebuggercfflashforms/feed/ 0