Earlier today I blogged about being aware of the differences between the way ColdBox and ColdFusion 8 handle variable names when serializing to JSON for remote calls (the original post name is much more elegant, I promise). Several questions arose as to the different ways variables can be created and how exactly each method would output, so I decided to put together this short test.
Nothing big, really. However, I did spend part of the morning figuring it out. If you follow me on Twitter, you might've noticed I had to work out a weird problem with ColdBox and jQuery. What was happening was that I had a jQuery plugin working great with CF8, but as soon as I started using it on an app built around ColdBox it stopped working.
Last night I had a little time on my hands and decided to start a project I'd had on the backburner for a while (hint, hint). While setting up Coldbox, I wondered: Why not use application-specific mappings to reference the right framework versions? You might remember I had made a (short) series on refactoring Coldbox, Coldspring and Transfer for this exact reason. However, reading the Jedi's Transfer adventures made me realize that being on ColdFusion 8 meant that I could have these specific mappings, rather than refactoring the frameworks. I ran into an issue or two, however, and here's how I got rid of them.
Last week, I showed you how I had setup my register method in my project. After a couple of comments, I realized I had tied my service layer too tightly with my MVC framework (ColdBox), by passing in the entire event object, rather than just the data that I needed. Today, I explore a different way of doing things, while also making a couple of little changes to the way the handlers are setup.
I've been stuck reinstalling Eclipse and friends (read plugins) for the last hour or so, so I figured I might as well read up on my backblogs (you never know, that word just might stick). If you haven't seen it, Jason's been writing up a really neat series on Coldbox and Coldspring. He's taking a different approach than I am, which is great since you get to have different point of views.
Yeah, yeah, I forgot the links. They're in now.
Recently I've been hard at work trying to understand the core principles of OO programming in ColdFusion. Last week Ben Nadel shared his experiences at a week-long course devoted to OOP with Hal Helms (the summary, which can be found here, also has links to his daily briefs). His posts opened my eyes to a couple of concepts that are now new to me, and since I'm on a new project I thought it'd be a great opportunity to try them out. As you know from my previous posts, I'm also trying to implement IoC (Coldspring) and ORM (Transfer-ORM) frameworks into my project, so figuring out where these two stand in relation to what I think I now know about OOP is my next challenge.
