i like the idea of a wiki for oo cf. i raised the question on cf-talk several days ago about whether the community needed a devoted discussion area for oo concepts and was referred to cfcdev.
i signed up right away and have been reading the posts, er, religiously, so to speak ;) since then i've been researching other oo-related communities and have seen wiki's that are fantastic resources for picking up on all the oo-lingo and design patters, etc. they often serve as historical chronicles on emerging oo trends and provide a great deal of background which is both interesting and pertinent - overall, they've been a great resource to supplement the discussions that go on here within the cf community. and, as wiki's, they make it very easy for potential oo-acolytes to explore the meanings of unfamiliar terms. i referenced this site in cf-talk (i think) last week, but i'll point it out here again as an example of what i'm talking about... http://c2.com/cgi/wiki?WelcomeVisitors (welcome and overview) http://c2.com/cgi/wiki?DesignPatterns (intro to design patterns) which purports to be the oldest known wiki, created in 1995 (tons of info!) brian -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cliff Meyers Sent: Tuesday, April 05, 2005 12:15 AM To: [email protected] Subject: Re: [CFCDev] CF, OO, and CFCs I think it would be silly be have a separate list for OO-design and CFCs because the two are far too closely linked. Whenever you have a vibrant community there seems to be an eventual move to fracture it based on differences that exist, but it rarely works out for the best! I think the best compromise is to respond in kind to the question asked. If it's a simple straightforward question - even if the approach doesn't seem really sound - it might be best to answer it concisely and then add, "however that might not be the best design." See if the person bites and asks for more info. What might frustrate a lot of new users is when people launch into lengthy posts explaining all kinds of OO concepts that are way over their head. No one should be discouraged from providing valuable info, but in every case the question-asker might not be interested. It's just a matter of trying to gauge that I suppose. I'm writing documentation for my development team on CFCs including a lot of the best practices I've pulled from various sources (including all the great responses to my question today). I think a lot of those practices can be presented very concisely and answer a lot of questions that newbies have about using CFCs. I think it would be a cool resource to start up a Wiki on CFCzone.org and just direct users to that post. That would save a lot of us typing and also not open up these big debates about OO design :) -Cliff ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
