Now, while I'm saying this, I know that there will be others who simply don't agree, but we've got to refactor at some point, maybe not for this specific release, but sometime. There's CFMX specific workarounds throughout the code (note : no updater) that can be removed - FarCry requires 6.1. There's four different cffunction style <cfdump>s throughout the code base, cfimports which never have a custom tag being used (I don't know if that's a perf hit or not) etc.
You're right its a bit messy in places -- but we're happy to treat things of this nature as bugs and receive fixes for them. Contact me off list if you are keen to be a regular committer.
To end, I'm not AT ALL knocking on anyones implementation that is currently in the code, nor am I discounting the effort behind it. But at some point we're going to have to look at future-proofing the code, which is on the top of my personal list. Adding a database, or working in BD would be a lot easier to do so.
Either way, my bit has been said.
I'll say though that I think it's pretty badass that BD is getting there when it comes to BD + FarCry, to think, we now have a total "free" stack for situations that a free CMS is needed.
We're not big on BD -- not that we have any sort of bent against New Atlanta but our clients are simply not asking for it. Any assistance you can give getting the code base supported on a wider platform is greatly received.
If BD is a major concern for FarCry Developers, we're keen to start fostering that community. I'd be interested in hearing ideas as to how we support BD post 2.4 when we move to leverage CF7 specific features.
-- geoff http://www.daemon.com.au/
--- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
