Just wanted to add; I will be adding the "why's", that is why I love the criticism, as I said it makes me need to think "WHY" and when doing so I can add that to the document.
In my head I know the "WHY" but like you said, someone needs to know the "WHY". I am like that myself, if someone tells me something without the "WHY" then my mind cannot grasp the concept, I need to know the "WHY" behind it. Anyway I'm rambling on, the "WHY" is coming!!! > 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). I am trying to be as Object Orientated as possible at all times, with naming of anything, i.e. variables, stored procedures, tables, documents, site structure, I try to be Object Orientated when creating Code of any kind, but whether that is someone's "Methodology or whatever" I do not know. I am afraid to say I have never heard of MVC or Decorater, but I don't think that means I don't grasp the concept of "Object Orientated". Part of me wants to dig deeper in the meaning of "methodology" discussion, but it's not worth it, as I said let's call it what we want and let it do its job... ;-)) 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 --- 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
