Last night, I finished Phase I of my Exercise List journey into understanding Object Oriented Programming (OOP) in ColdFusion. Phase I was the "proceedural" phase; it was building the application in a quick, standard, proceedural way that does not take advantage of any sort of ColdFusion components or OOP principles. The important thing is that it laid the foundation on top of which I can now learn object oriented programming, not just for single objects, but most importantly, for object composition and relationships in the context of a small but highly applicable application.
Building Phase I took a little longer than I had expected because I was trying to keep the CSS fairly clean. After reading Bulletproof Web Design and Learning jQuery and having looked at the stuff Javi is doing, I wanted to really put some effort into making accessible forms and progressively enhanced functionality. Therefore, there are no tables in my forms (which is what I would normally do); instead, it is a strategic use of the Label element as well as many DIVs and the like. This was my first attempt, so I am sure it is not at clean as it could be, but I think, not bad for the first go in a new mind-set.
Also, as a side effect of using the jQuery and progressive enhancement, you don't have to worry about any Form Caching done by the browser. I am sure at some point, everyone has had to deal with FireFox keeping checkboxes checked even after a soft-refresh. This can cause issues because ColdFusion will view the FORM data as being different that the rendered FORM and therefore, mouse click events do not always act as expected. By using jQuery and progressive enhancement, however, you never have to worry about this because jQuery runs code at the end of every page request (including soft-refreshes) and because it works based on the rendered page, form caching becomes a non-issue.
Here is the code that I have at the bottom of the Search and Edit pages:
It's almost too easy! I love jQuery.
Exercise List: Next Steps
Now that Phase I is complete, it's time to start getting into an Object Oriented state of mind. If you look at the Add / Edit Exercise query page as well as the Search query page, you will see that the logic here is not exactly simple. I am going to have to figure out how to capture the relationship between joints and exercises and how to access that relationship. For example, are the joints actions composed in the Exercise object:
... or are they gotten from some sort of Exercise gateway / service:
ExerciseGateway.GetJointActions( ID = 1 )
Or are both of the ideas horrible? To be honest, I haven't the faintest idea. I have a whole host of ColdFusion Object Oriented Programming blog posts (by other people) in my "To Be Reviewed" bookmarks folder. I guess it's time I get reading.
Any and ALL advice would be greatly appreciated.
Want to use code from this post? Check out the license.