Looks great. Only two things I might have issue with: 1. Only writing for CFMX 7 will alienate the many out there who finally moved to 6.1 (once achieving corporate approval) or who have moved to BlueDragon. An option within the install to define the server environment can enable/disable features that might be version specific (like Flash or XForms or CFDocument).
2. Use of stored procedures will alienate anyone using MySQL prior to version 5. Many shops may not upgrade for a year or more to guarantee (in their minds) stability as well as testing (kinda the same reasoning you may night want to write exclusively for MX 7...). I would suggest a DAO architecture that you could then extend for different database platforms (MSSQL, MySQL, Oracle, etc.) and include the need within the install to define the db platform being used. A good example of this can be seen by DAO CFC's written by CFCCreator. I would also suggest defining some basic coding guidelines. Code indentation, variable naming conventions, db table and column naming conventions, documentation specifications (I suggest JavaDoc), etc. This will keep everyone on the same sheet of music, make code review and revision easier, and implement some design consistency to make final packaging much cleaner. My $.02, which is all I can give with the rising moving expenses I am about to incur. Cutter ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:224448 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
