Taco Fleur wrote:
Hi Scott,
I was hoping you would jump in at some stage ;-))
heh, I manage to find some time while i wait for Flash to finish compiling (9 mins for a swf to compile...)
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.
I was thinking exactly like you before, I did not want to post anything until it was perfect, but the bottom line is, how can it get perfect without input from the whole CF community? That's why I chose to finally stopped whining about it not being perfect and started posting parts I have documented and want to receive criticism on.
True, we are happy at this point to release it, but in truth, havent the time to setup a page and blah... that and can't be assed atm. Plus Spike was the architect, and well he should be here for the cutting the ribbon (so to speak).
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.
Criticism doesn't hurt me, it only makes me stronger, so keep it coming;-)) I love it when someone tries (or does) to break a rule or idea, it only requires me to think even more about "Why did I do it that way, why did I suggest that?"..
true, its annoying when people shoot your theories down and can at times be deflating, but it makes you rethink and even make sure your original strategies still hold.
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.
I realize that what is out there at the moment looks like just guidelines, but I hope people will see differently when I start publishing some of the methods I use for data filtering and data verification. And please, I am not trying to be better than BATFINK or any other methodology out there, as a matter of fact I am sure it won't be, I also realize that whatever you guys have is most likely brilliant and will have some functions or parts that everyone else can benefit from, but post it so we can all have a look and criticize ;-))
Not competing in anyway, BATFINK is unqiue and well when Spike first pitched the concept to me, i personally found it hard to accept, only through ongoing discussions and input, did myself and the other team come to vale its abilities and overall concept. I personally think its great, not only for its structured way of development but its also helped me attack other langauges like Flash MX with a new perspective. I've managed to apply BATFINK to Flash? i mean thats got to be a valid reason behinds its strength (works with bost Flash and CFMX?)
PS. Taking from the dictionary:
meth.od.ol.o.gy
A body of practices, procedures, and rules used by those who work in a
discipline or engage in an inquiry; a set of working methods: the
methodology of genetic studies; a poll marred by faulty methodology. The study or theoretical analysis of such working methods. The branch of logic that deals with the general principles of the formation
of knowledge. Usage Problem. Means, technique, or procedure; method.
If I interpret this, then I do believe what is out there at the moment can be considered as a methodology, or my English is just not good enough ;-))
I think you've focused on the "procedures" and forgot the rest, to me a methodology describes how a theory is to be processed and doing so without specific instructions on how. If you where to evolve your theory further, i think you may end up with a framework. So far based on what you have is merly a guidelines on how to code. There isn't any logic behind why or reasons for your directory structure. Furthermore do you adhere to an OOP pattern of some sort (not saying by law you have to adopt a GoF Pattern etc, merely whats the theoretical logic behind what you do the way you do it).
MVC is a pattern, if you interpret that into CFMX, imho that then becomes a methodlogy as it touches on some basic framework implementation but doesn't require you to adhere to that specific framework. At any point you can change your overall naming conventions and such, but underlying structure or theory is still intact. It could be based on MVC or a combination of MVC, Decorater and Observer patterns? I dunno, I am having a skewd perspective on the seperation of Methodology and Framework, i just debated what is batfink with Mina and while i still believe batfink is more of a methodology, i can see it can also be interpretted as a framework.
Regards Scott Barnes http://www.mossyblog.com
Taco Fleur
http://www.tacofleur.com/index/blog/
0421 851 786
Tell me and I will forget
Show me and I will remember
Teach me and I will learn
--
Regards, Scott Barnes - http://www.mossyblog.com http://www.bestrates.com.au
--- 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
