I decided to throw in a couple of additions as well as a solution for a problem some people where having. The first thing I added was a source attribute. This will be an external URL that you can load into a window. You may be asking yourself, what about the autoLoad attribute. Right now the updater will only load files from the same domain and I believe there are security reasons behind that. If you try and pass an external URL to the autoLoad attribute it will not work. That is where the source comes in, it will trick the window and load the URL into and iframe that fills the window. I may remove autoLoad later and based the domain of the source figure out if I should auto load it or throw it in an iframe but we will visit that another time. Here is a quick example of how to use the source attribute.

view plain print about
1<cfimport prefix="ext" taglib="cfext">
2<html>
3<head>
4    <title>cf_window / External SRC Example</title>
5    <ext:include widget="cfwindow"/>
6</head>
7
8<body>
9    
10    <ext:window id="adobe" title="www.adobe.com" width="800" height="600" modal="true"
11                closeAction="hide" collapsible="true" bodyStyle="padding:0px;" source="http://www.adobe.com">
12    </ext:window>    
13    
14    <a href="##" onclick="adobe.show();">www.adobe.com</a>
15    <br /><br />
16    
17</body>
18</html>

Next I added some features to the include library. The first is the ability to pass in a theme name. Themes change the appearance of the windows. Right now the only other option is the gray theme so you can just pass in gray as the theme. Also many people were having issues with path issues and the include files. This would happen if you had the cfext folder placed in the root and tried to call the tag from somewhere else in your application. I think (and the jury is still out so let me know) an easy fix for this is to pass in a full path to the cfext folder. An example would be I placed the folder under folder whatever from the root. My Path would be http://www.danvega.org/whatever/. This should just give full paths to the includes and should resolve that issue. Again please let me know for those of you having that problem. Here is an example of combining both of these features.
view plain print about
1<cfimport prefix="ext" taglib="cfext">
2<html>
3<head>
4    <title>cf_window / Full Path</title>
5    <ext:include widget="cfwindow" path="http://www.danvega.org/examples/" theme="gray"/>
6
7</head>
8
9<body>
10    
11    <ext:window title="A Basic Window" width="300" height="200">
12        I am <strong>html</strong>
13    </ext:window>
14    
15</body>
16</html>
Finally I have added all of these examples to the demo page. Let me know how everything looks. I think I am finally close to focusing on planning out a full library.
http://www.danvega.org/examples/cfwindow/
 

This entry was posted on January 11, 2008 at 1:08 AM and has received 3282 views. Comments 7 | Print this entry.