Pretty old but someone just sent this to me today.

“The difference between the Pope and your boss... the Pope only expects you to kiss his ring”

After a few suggestions coming by the way of emails, I decided to put them into the distribution of the CFC DAO, Bean and gateway creator for Coldfusion MX 6/7 . Also, it should correctly work with Microsoft SQL server.

Changes:

1. Bean's setter functions now have two additional optional arguments: isNull and Validate
2. Now the bean controls the length of fields and if something is nullable.  Initially the generator will create the configuration for you but you can modify later by changing the setBeanConfig() function inside the bean CFC.
3. The bean setter functions perform validation on the data passed in according to the specs from bean config.
4. Each property of the bean has an isNull{property name} function
5. All data coming from the database is considered trusted and will not be validated when passing it back to the bean setters.

To see the changes in action, view the demo.

You can download it here. The downloadable version contains a transformsbasic directory that contains the original transforms.

I am not sure I will put any other changes in the distribution as other suggestions were more specific and could be implemented in other ways.  But, remember you can incorporate your changes just by modifying the XSL files.  If you need some help, just contact me via the email address in the readme file.

The more and more I am generating code with the CFC Bean, DAO and gateway creator

The more I am noticing the need to support a null value and I am trying not to go in and write work arounds for each bean / dao / gateway CFCs to support nulls.

So, would defining a default bogus null value per bean be the way to go?

Example:

Now in the DAOs have something like:

I uploaded new transforms to the demo CFC Creator script to reflect these changes if you want to see how a fully generated CFC looks using the above.

Thoughts?

Think I should use the new transforms in the downloadable version of CFC Creator?

Since MXNA is aggregating my feed now, I needed to have BlogCFM notify MXNA when a new post was done.

Previously , I showed how to add your own configuration options to BlogCFM.  This time I added a PING_ON_UPDATE configuration option, along with adding the field to the admin screen.

My SendPings function is very simple but could use some work for error checking and stuff.  Perhaps I will work in some error checking later but since it is only me using this function currently, I know I will type in the correct ping URLs.

I added the following to the BlogCFM.cfc but could be used in any blog really. It accepts one argument, a list of URLs to send to seperated by ";"



Next was to tell BlogCFM to send the pings.
I put the following below the notifications area of SaveEntry()

       

That did it!  Now BlogCFM will ping whatever URLs I type into the admin screen (MXNA).

Well, this is probably not new technology to most but I just read about it the other evening.

http://greasemonkey.mozdev.org/

For anyone that doesnt know what it does, it basically allows you to make any webpage look how you want it to look.  Lots of cool examples at http://dunck.us/collab/GreaseMonkeyUserScripts.

Anyways....  after reading over all this stuff I decided I wanted to make something.  The best thing I could think of was a minor annoyance I had with some websites not offering their own search feature.

So I figured every site should at least have a google search on it.  Now I just needed a decent way to show the form and I found http://www.xs4all.nl/~jlpoutre/BoT/Javascript/RSSpanel/rsspanel.html as a starting point of my project.  It offers a user draggable interface for a floating window.

After mangling his code and inserting some of my own, I came up with:


Couple key things added to his code.

1. It saves the location/visibility of the search box for the site you are currently visiting.
2. Has a user command to force the search box to show for the current site.
3. You can restore the default location of the search box via the user command menu.

So, now whenever I visit a site, I can always search the site directly from the webpage.  If the webpage has a form that contains the text "search", the search box will not display unless I force the search box to display.

If interested, you can install the Greasemonkey script at http://www.franciswscott.com/downloads/searchthissite.user.js

To sum up Greasemonkey..... very very nice idea!