Hi Alan I didn't think it appropriate to follow-up your last comment against http://code.google.com/p/openbluedragon/issues/detail?id=249 in the issue tracker (because it being off topic), so will reply here.
My dig regarding lack of CFML docs was more aimed at the historical situation with New Atlanta relying on Adobe to provide docs for them, which I think was a bit "commercially exploitative" of them. I understand you're an open source project so rely on the help of others to get stuff like docs done. Fair enough. I talked to Gert & someone else from the Railo team about trying to get Adobe, Railo, New Atlanta and I guess someone from the OBD team together round a table and agree on a common, unified (and "open source" / wiki-ed) documentation repository for all of the competing CF engines, as a gesture towards strengthening the CFML community. This was at a time when Railo seemed to be wanting to get their own open-source docs off the ground, but were getting very little community buy-in. I was hoping someone would be able to convince Adobe to "donate" at least the tag/attribute / function/argument skeleton part of their docs to a unified open-source CFML ref, as a starting point, and they could keep the rest of their docs (examples, explanations, etc...) as proprietary as they liked. I figured even just having a page for each tag / function, and a list of attributes/arguments would be a good start, and get a lot of the more tedious donkey work out of the way. Then the community bods like me could just add annotations along the lines of what we were discussing with randRange(). However nothing came of this, and I have to concede I never chased it up. I'm all for community participation, but I think it's a waste of resources for each CFML flavour to have its own duplicate of the CFML reference, esp when 99% of it would be the same. It'd be more helpful for the community as a whole to have one centralised (and flavour- neutral!) version of this. For my part, I am and will remain primarily a CF user, and am only really using OBD because of the remit of this current project, so I don't have the... err... "OBD community spirit" (or whatever) to want to invest my time writing docs for it. I'm happy to raise & discuss bugs I find though. Esp if you continue to fix 'em so quickly! Cheers. -- Adam -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon online manual: http://www.openbluedragon.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en
