I understand the black box principle of CFC's, make sure that your cfc's
can stand on their own as black boxes. When doing OOP based development,
does this paradigm
extend to non-cfc ColdFusion files, IE: display and action pages.
Thanks
sas
--
Scott Stewart
CTT+ Technical Trainer
At some point your going to have to develop some uniqueness into your
application that is project specific. You can spend a lot of time on form
generators, and generic and configurable work flow engines, but is the time
worth it?
I even have some CFC's that are project specific. What I try
On Wed, Aug 4, 2010 at 3:22 AM, Scott Stewart sstwebwo...@bellsouth.netwrote:
I understand the black box principle of CFC's, make sure that your cfc's
can stand on their own as black boxes. When doing OOP based development,
does this paradigm
extend to non-cfc ColdFusion files, IE:
I understand the black box principle of CFC's, make sure that your cfc's
can stand on their own as black boxes. When doing OOP based development,
does this paradigm extend to non-cfc ColdFusion files, IE: display and action
pages.
In general, any program should have a defined set of inputs
On Wed, Aug 4, 2010 at 7:50 AM, Dave Watts dwa...@figleaf.com wrote:
So, my overall advice here would be not to overthink display logic -
it's the least formal layer in an HTML-based MVC application.
I might go further and suggest not to overthink any aspect of your
design. The biggest
So what your saying is, design patterns, like music theory, exist so
you know when you're breaking them :)
On Wed, Aug 4, 2010 at 11:56 AM, Sean Corfield seancorfi...@gmail.com wrote:
On Wed, Aug 4, 2010 at 7:50 AM, Dave Watts dwa...@figleaf.com wrote:
So, my overall advice here would be not
On Wed, Aug 4, 2010 at 9:27 AM, Scott Stewart webmas...@sstwebworks.com wrote:
So what your saying is, design patterns, like music theory, exist so
you know when you're breaking them :)
That's a good way of phrasing it :)
The key thing to remember about design patterns is they include a set
7 matches
Mail list logo
