Scott Barnes wrote:
We have a similar thing happening at Daemon. No time to get it into shape as yet but we are planning to publish it to the web and make a kind of collaborative/feedback driven "best practices" document.I am slowly compiling a development guidelines for both CFMX/FlashMX/DHTML/CSS and FlashCom for Tourism Qld atm, if allowed I don't mind publishing it.
We use a bastardised FUSEDOC implementation. But we're trying to work out how to automate, CFCs standard code blocks and conceptual documentation into one living document... looks like chasing the holy grail at this time unfortunately.I've also compiled a JavaDoc Commenting Solution for all of the above technologies.
If your interested we have released a component pattern for database interaction called FourQ (http://fourq.org/). The documentation is a little dated compared to the code. But you can browse all the code online without having to download etc which is kind of nice.- In your cfc's keep your sql out of your main stream, in that say you have a products component that handle all business logic relating to the product, don't put SQL queries within this component. Make a separate component called "productsSQL or productsORACLE" and instantiate that as an object either within the component or within the invoking application page.
The code browser is at:
http://fourq.org/index.cfm?objectid=EA9832E7-CEAF-EC74-4EB55103D6A5E8AC
Or you can browse there from the Documentation section.
-- geoff
http://daemon.com.au/
PS. I'll be talking through concepts like FourQ and other persistent CFC methodologies at http://mxdu.com/ if anyone is interested.
---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MX Downunder AsiaPac DevCon - http://mxdu.com/
