1. You are a non-conformist
Basically you are "doing your own thing" despite moderate criticism from the likes of Macromedia's Sean Corfield who has by his own admission been involved in (ColdFusion) web development only recently compared to us (8 years now).
Seriously, bad comment to make :) From what I have heard, Seans not some punk jnr CF Developer wannabe, he's got allot of history in OOP development which we would safely assume to have read loads of "Methodologies".
As for Coldfusion and having 8 years of development? I've been using CF personally since it came on 3.5 disks :) yet, in the last year that means dick. CFMX changed allot of the rules in CF Development and made us now stop emulating OOP and actually touch on it more so. It may not be totally 100% pure OOP but its just as good. So pulling out the "i'm a old skool CF`er" won't work.
Furthermore, CF is a basic language to understand in that i've seen people who have had no Programming background at all, pick it up under 3-6 months or less! Its more of an extension of HTML in many ways, as thats how easy it is. The only situations where I have seen a developer stumble is when they start playing with the more advanced tools (SQL, CFC's, RegExp etc).
Tacos "guidelines" are ok, personally their not my cup of tea. Its great someone puts his reputation on the line so to speak, and produces an online document outlining his style or coding and general CF ethics.
We here at TQ have our own methodology, called BatFink. Few people have heard about it, and we have casually mentioned its principals once or twice. Its kind of based on MVC well, last look it was apparently MVC complient and works in the fashion of keeping both backend / frontend logic abstract from one another along with keeping the business seperate from the data layer.
Now I look at all the methodlogies/frameworks out there and personally i don't think these even come close to ours, but thats because i am biased.
I mention this as we haven't published it, yet we should but in truth its matter of making sure our I's are dotted and T's crossed, because the moment it becomes public, people will criticise its flaws. Having said that, thats not a problem, as it will strengthen the theory behind it. Seans comments were on the mark imho, I'm not a MM suckup, but i thought they where valid.
If you put something like taco did online, expect both negative and positive reviews, and if you assume its a methodology and its really just a guidelines or even framework, expect to be corrected as they can be easily confused or overlap.
Imho,The more i read it, and the more i think what taco has done; it's more of a coding guidelines, and not so much as a pattern or methodology. Thats my view, could be wrong dont care :) The reason i think its so, is due to the fact there is no apparent underlying structure to the concept.
Methodologies imho should have some basic rules (that are breakable, but more of a guide) and from there you code based on the core concept. An example would be batfink (early version, its changed since, but not updated on the new naming conventions etc).
Batfink basic rule of thumb is, that each package basically has a controller, that takes requests and deligates to sublogic.
eg;
com.mysite.Security.controller
If i wish to handle basic site, with basic security, i have to then instantiate the security controller into either a empty scope or via memory (session, server, application).
I then make various calls eg:
mySecurity = createObject("component","com.mysite.Security.controller");
mySecurity.authenticateUSer(username=balh,password=blah);Basically without getting to deep in code review, what happens is i make the calll to the controller, the controller does its basic logic (string validation etc) then instantiates the com.mysite.Security.persist object, passes in some arguments. The persist then does its Database lookup, extracts the data, passes it back out to the controller, which then filters out excess noise, and hands it back to the caller.
At no point does this methodology imply specific rules, you have loads of room to play with and you can bend the rules to suite your needs. It also keeps both persist and controller abstract from each other, as persist could be swapped out to use ORACLE instead of SQL, that or get excess information due to it being used multiple times from other objects.
To me this is a start for a methodology label, as it makes use of existing OOP patterns but translates them into CFMX terms. What I have read on Taco's is more of a "how to code" guideline.
Sorry to be blunt.
Regards Scott Barnes http://www.mossyblog.com
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
