Carl
ps. So Scott is that a knitted blanket in the back seat of your Kingswood that your nanna made for you? hehe
Scott Barnes wrote:
Robin Hilliard wrote: I'll take patterns for $100...
A Pattern is a term used in knitting..eg:
Agnus: "Maude, i did a really nice cross-stich pattern last night"
Maude: "Oooh thats nice...say did you see old sexy eyes ken suncliff, he and ray martin look mighty tastey now days..mind you though, i.." ZzzzzzzzzZzzzzz
Sorry old people have way of not being able to stay awake.
Architecture; The thing that binds your layers together (data,model,view,dataprep etc).
Specification; Something that never gets done.
Requirments; Something that always gets asked, but never gets done.
Patterns;
A collection of design concepts to help you understand how to use OOP plays..ie like a playbook, general concept up to you to figure out how to put it in play..
I use the "decorator" pattern a lot (think thats the pattern in question) - where i take an object, that i want to sometimes have methods attached to it while other times dont.. so instead of storing all these un-needed methods in it all the time, i simply take an object (eg EventDispatcher in flash) and decorate the object, this way that object now works as if it originally had the methods..
eg:
myObject = new MySpecialObject();
com.system.events.EventDispatcher.initialize(myObject);
myObject.dispatchEvent({type:"onMonkey", target: this})
:)
Scott
Hi,
Just to clear up terminology here, all the stuff discussed here so far comes under the heading (in my book at least) of "framework" - actual code you fill out the gaps in to create your application. Methodologies are things like RUP (the Rational Unified Process) - more a list of design processes to carry out than actual code.
BTW what is the distinction between a framework and an API (Application programmer interface) library like CFLIB? Typically in a framework you see an inversion of control (otherwise known as the Hollywood pricipal - "don't call us, we'll call you") where the framework code is responsible for coordinating and calling the developer's code (Mach II an excellent example). With an API the developer's code is almost always calling the API functions, and the API doesn't know anything about the caller. So a framework makes a lot more demands on the shape of the application components you create - methods, arguments, responsibilities - so that it can integrate them into the finished application.
Anyway, thought it was worth pointing out. Might be interesting to discuss what we think some other terms mean - Architecture, Specification, Requirements, Patterns - not too OT I think.
Cheers,
---
Robin Hilliard Partner RocketBoots Pty Ltd Professional Services for Macromedia Technologies m +61 418 414 341 f +61 2 9798 0070 e [EMAIL PROTECTED] w http://www.rocketboots.com.au
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
