A Handful of Code
In my last post about page controllers, Jason Holden asked on which pages I use page controllers. This is a great question and speaks to a larger issue of code organization that applies to CSS and JavaScript as well.
In my last post about page controllers, Jason Holden asked on which pages I use page controllers. This is a great question and speaks to a larger issue of code organization that applies to CSS and JavaScript as well.
Pluralizing in ColdFusion
Steve Bryant said: James,
Sorry I missed your comment earlier. I haven't compared to other libraries. I didn't even kn...
[More]
Pluralizing in ColdFusion
James Moberg said: Have you compared the results with other libraries? I use an inflector CFC and I see that some of t...
[More]
Git Branching Strategy for Web Development
Thomas said: Hi Steve,
thanks a lot for this post. While considering Git Web Flow for our branching strategy, t...
[More]
Getting Around Windows 7 "Destination Path Too Long" Error When Deleting Files
MxP said: The above robocopy command worked like a charm! I had a deeply nested folder structure that I wante...
[More]
New Open Source ColdFusion Shopping Cart
Paul said: I gave up on this after all kinds of pathing issues. Couldn't be bothered tracing where to change th...
[More]
I think most of the things that you could put in a view but might go in a page controller rightly belong in the controller rather than the view (as JavaScript belongs in a .js file and CSS belongs in a .css file).
I don't think I would exactly call that an encapsulation issue though, perhaps more of an issue of separation of concerns.
The only reason I mentioned encapsulation is that I don't think the "Handful of code" rule should be used to justify breaking encapsulation. For example, I don't think it should be used to justify using shared-scope variables in a model component.