John C. Bland II

A while back I starting building cfgithub and noticed I was, technically, writing unit tests but poorly. I then took a dive into CF-based unit testing frameworks and finally dove into mxunit. It was kicking my butt! Nothing in it was working properly but I finally got it working perfectly fine. I posted my issues on Twitter how I felt it was “…outdated, IMO…” to which @MarcEsher responded asking how to which I’m finally responding tonight.

At a minimum the homepage should work perfectly fine. Unfortunately, the homepage has some code issues. In order to get this page working, it takes a few tweaks. I’ve posted these tweaks on the the Google Code issue tracker so those guys can get the builds together. It, honestly, looks like quality control wasn’t done on this build before publishing since these are so blatant you can’t miss them.

So…I’m off to see if I can get the rest of mxunit working. We’ll see how well this goes since my last attempt(s) were feeble but mainly because of the mxunit failures.

Disclaimer:

I can write test suites without a problem. That works perfectly fine. I hit walls when I attempt to use the Stub Generator, etc from the /mxunit site (not the .com but the actual site built within the /mxunit folder).

Yesterday I was pinged on IM by John Farrar about an issue he was having connecting Flex to ColdFusion on his new system. He’d done this many times before but hit a bump so we jumped on Adobe Connect and looked into it.

Continue reading

The long debate is back. So many argue the affirmative and are absolutely crazed over the argument. I’m not going to jump into it this time around. I would LOVE to see Standard offered for free but I won’t cry if I have to buy the next upgrade to CF9.

So, my post comes from Ben’s dissertation (hehe) he “just posted on his blog”:http://www.forta.com/blog/index.cfm/2008/6/2/The-ColdFusion-Pricing-Debate-Revisited. I’m turning comments off on this post because I don’t want to steal any thunder from Ben’s overall reason for posting (research into the discussion for Adobe’s planning purposes; or that’s what I got from the post).

It is cool to see “a bug you reported”:http://www.johncblandii.com/2008/04/coldfusion-801-cftooltip-is-br.html fixed.

Grab the “hotfix here”:http://kb.adobe.com/selfservice/viewContent.do?externalId=kb403622&sliceId=1.

Thanks to “Ray for blogging the hotfix release”:http://www.coldfusionjedi.com/index.cfm/2008/5/17/Did-you-know-a-hot-fix-for-ColdFusion-was-released-this-week because I had no idea one was released.

I spoke with Delmore and Adam Lehman this weekend about the use of multiple javascript libraries. Ext 1.1 didn’t have everything Ext 2.0 has so they had use multiple libraries. Makes sense.

For CF9…PLEASE GET RID OF YUI! The UI components are absolutely flakey. I’ve been able to reproduce tons of issues with _cflayout_ tabs (I mean really horrible one’s; haven’t spent time debugging the JS though) and _cftooltip_ (“fix here”:http://www.johncblandii.com/2008/04/coldfusion-801-cftooltip-is-br.html).

So…no code suggestions or anything…just please nix YUI and fully integrate Ext 2 or whatever the current version is when CF9 comes out.