Everybody knows that it’s not possible to use Flash Remoting to call a cfc from a flash form. Furthermore, one of the limitations that the flash forms have is that they do not allow writing the keyword "new" (except in cfcalendar :) ), so we cannot use it to create a new remoting connection.
read more Category: CFForm | ColdFusion |In my previous post, Paul Hastings asked how to capture the x,y from a clicked image. In response to that, I made a small workaround that requires an invisible text field.
This is not the cleanest way to do it and I'm sure someone will come up with a simpler solution.
read more Category: CFForm | ColdFusion |I made an example that shows how to load different types of images into a flash form.
In a cfform, it is possible to load gif, jpg, png, and swf.
Basically, there are two types of methods to load an image inside a cfform: at compile time and at runtime. cfinput embeds the images in the cfform at compile time, allowing more variety of image types (png and gif) that are not directly supported by the flash player. cfformitem and other controls such as textarea load the images at run time, so they are limited to the types supported by the flash player, accepting only jpg and swf .
Note that cfinput type="image" will put the image inside a button, so in the example, the first four images have borders and rollover states.
Today, Ben Forta posted an example to "Programatically change Flash Form calendar selectable ranges". At first sight, this is a nice example of using Actionscript to manipulate form controls. Reading the code a little more carefully, you can find a little gem: the word "new" is used to create a new date object. Those that tried creating new objects within ActionScript code have found that new, import, delete, createChild, loadmovie, duplicateMovieClip, AttachMovie, registerclass, createTextField, __proto__ cannot be used and writing any of those keywords would throw an "Illegal usage of ActionScript" error.
However, it seems that there are no restrictions imposed if we put a piece of code with illegal keywords in a cfcalendar. I do not know what this means, and why the cfcalendar tag does not have the same restrictions that the other tags have. If we use this now, can we be sure that the calendar will not be limited in the future to match the other tags?
I hope that the opposite happens instead. :)
(or CF Presenter without its skin)
Before:
After:
All the changes were possible thanks to the implementation of CSS in flash forms. The code is exactly the same in both examples. The only difference is that one has CSS and the other is in its default plain vanilla skin that comes with cfform.
Although the CSS properties have to be placed inline and it's not possible to have them in an external file, the ability of skin our forms with CSS is a very nice feature.
PS: the source is coming
View the example without CSS
View the example with CSS