I'm getting ready to create some development standards for my client
with regards to ColdFusion and Mach-II. To put some context around
this effort, I've been working with ColdFusion for over 13 years, but
mainly inside of my own framework. Most of my work has been within
corporate environments where the concern over organization and
compliance with such was the most important aspect of development.
Now I'm with a client who does not have a lot of ColdFusion expertise
and they are primarily a Java OO shop. Mach-II works well as our OO/
MVC framework, but we recently hired a new developer and his style and
mine are quite different. Although we both agree in form, e.g. using
a service layer, DAOs, etc. and not placing a lot of business logic
within our extended Mach-II componets, we almost seem to be on
opposite sides with how our business objects should be organized. In
case I'm confusing anyone, I'm referring to the directory structure
and how the various code artifacts of our Mach-II framework
applications are organized. I prefer to organize code based upon its
function and so beans exist in a "beans" directory at the root of my
application, the same goes for listeners, filters, plugins, views,
DAOs, services, etc. However, I'm curious to see what others are
doing with Mach-II apps and code organization. How do you organize
your code?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to Mach-II for CFML list.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/mach-ii-for-coldfusion?hl=en
SVN: http://greatbiztoolsllc.svn.cvsdude.com/mach-ii/
Wiki / Documentation / Tickets:
http://greatbiztoolsllc.trac.cvsdude.com/mach-ii/
-~----------~----~----~----~------~----~------~--~---
