New Blog for Export Reports
If you are interested in my new venture ExportReports, we now have a blog you can follow what's going on and give feedback.
One guy's take on the web, programming, cigars, politics, Philadelphia, and whatever else comes to mind.
If you are interested in my new venture ExportReports, we now have a blog you can follow what's going on and give feedback.
Cf.Objective is in just a few weeks now. Are you going? Here's why you should:
That's right, today is your last day to get reduced prices for the WebManiacs conference. After today, the only way to get a reduced price is to take a picture of you flashing your gams, send it in, and hope the guys and gals at Fig Leaf approve.*
Of course, you want to go, and see me speak about Air and SQLite, so sign up and get that reduced pricing.
* Actually, I'm fairly certain that won't work. And gams are legs, for those of you who didn't grow up during the Great Depression.
Or I would be if you are subscribed to the ColdFusion Weekly Podcast.
I got to participate in the CF_Rountable, a new format for the show where a bunch of ColdFusion community members talk about various geeky topic fodder. This week's group was:
This is in addition to the hosts:
It was a tremendously fun to participate. It was also impressive to see the amount of work and effort that Matt and Peter put into the podcast. They deserve a lot of credit for making it look effortless.
If you get a chance to participate, or see a call for participation, do it. You won't regret it.
Come to think about it, you should probably listen to it too. You won't regret that easier.
The ColdFusion community is aflutter with news that Blue Dragon has gone open source. Many other voices have chimed in on this. But I feel like I have something different to say.
Regardless of the any business gains that Blue Dragon gets from doing this, I don't think the community will get a tremendous benefit from this.
Continue reading "Yawn, Blue Dragon Goes Open Source"
I'm pleased to announce that I've teamed up with Mark Phillips and the guys at Vertabase to publicly release ExportReports.com.
What is ExportReports.com, you ask?
ExportsReports.com is a site that enables users of the 37signals product Basecamp to export copies of their projects to a PDF file. Before ExportReports, a Basecamp user could request a backup of their site, and receive an XML dump of their project. Now, through our site, a user can ask for PDF exports at will. It's perfect for either ongoing status reports, or an end of project knowledge dump to a client.
We do charge a small fee, but for the first month, we are running at reduced rates.
Technology
ExportReports was written with Adobe ColdFusion, and uses the Basecamp API's provided by 37signals. Three factors led to us choosing ColdFusion:
So, wish me luck on this commercial endeavor. If you're a Basecamp user, I hope you like it. If not, become one, it's a fantastic product. Then use ExportReports.com.
I few days ago I came across this post at Signal vs. Noise. The first item is about a clock that tells you the approximate time - for example 11:59 is "Nearly Twelve", 12:30 is Half Past Twelve, etc. etc. The idea is, "Do you really need to know it is 12:53?" This clock gives you the amount of precision that you actually need when dealing with time.
I thought it was kinda cool, but I would never buy one. However when I thought about it, I realized it would make a good AIR application.
After thinking about I decided to do it because:
All of these things added up to me writing the thing in about a day. Here's what I did:
The amazing thing to me was how easy it was to do. The actual app worked relatively quickly, most of my time was spent getting the details like icons, and text placement correct.
So if you want to know about what time it is, download your copy of About Time.
Disclaimer: This totally is "an Air app that didn't really need to be". I get that. I figured someone else might like it, or at least want to look at the source.
I'm working on someone else's code base, and found that they were posting forms to themselves. However they had hard coded the form template names into the code for the form. Like the following:
<cfform action="index.cfm" method="post">
This is a bit of a pet peeve of mine because it tends to make the code very un-portable. What happens if you rename the file "dosomethingelse.cfm." Now you have to go back and change the file name and the reference.
It was a quick proof of concept application, so I don't fault the author. But they just aren't lazy enough.
I prefer doing it this way:
<cfform action="#cgi.script_name#" method="post">
It's highly cut and paste-able, and you never have to worry when you rename your templates. If you aren't using cfform, you can still do it, just wrap the form element in a <cfoutput>.
Now, I imagine that I will get a comment that says something about not trusting cgi variables. It works with every flavor of IIS and Apache that I have ever worked with. Anybody see any gotcha's doing that.
| Su | Mo | Tu | We | Th | Fr | Sa |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | ||||
| 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| 11 | 12 | 13 | 14 | 15 | 16 | 17 |
| 18 | 19 | 20 | 21 | 22 | 23 | 24 |
| 25 | 26 | 27 | 28 | 29 | 30 | 31 |
adobemax06
adobemax07
air
Air
Basecamp CFC
Cigar Reviews
Cigars
ColdFusion
Entertainment
Film
Flex
Internet Meme
Meta Blogging
Movable Type
Personal
Philly
Philly Mayor 2007
Places to Smoke
Politics
Random
Religion
Running a ColdFusion Shop
Squidhead
svnAuth.cfc
TV
Web Development
Who Needs A Cockpunchin' ?
Writing