I am working in Mach-II at the moment, and this is supposed to be one of the reasons that we are using (BTW, I've been doing Mach-II for all of about two weeks now). I don't see how having a circuit in Fusebox or Mach-II allows for code reuse if the code has to be personalized for each user or group of users. It seems to me that there are three models for presentation extensibility:
1) Write application once. Force client to use it as it is. This is easy maintenance. 2) Write application once. Modify the code so it changes views depending on who's using it. It's easily extensible and centrally controlled but quickly gets nasty as more and more users need to access this application. 3) Write application once. Copy and paste an entirely new instance of it and modify that for each user/department. It's easy to maintain for that group/user but if a core modification must be made or an error is found in the code that is common to all of the applications, it must be changed in all of the applications individually. It seems to me that writing a CFC that contains presentation logic might be a viable way to override the presentation when you need to. I could just extend a CFC and rewrite only parts of the CFC that need to be changed. I have not fully thought out this approach. Any comments on this? Matthew Small Web Developer American City Business Journals 704-973-1045 [EMAIL PROTECTED] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Gold Sponsor - CFHosting.net http://www.cfhosting.net Message: http://www.houseoffusion.com/lists.cfm/link=i:4:188822 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
