Funny enough, they are also less widely known as the Four Gangsters
after a someone with limited English skills referred to them this way at
a conference.
Perhaps it was actually English skillz ;-)
___
Flashcoders@chattyfig.figleaf.com
To change
Of David Ham
Sent: Tuesday, January 30, 2007 7:02 PM
To: Flashcoders mailing list
Subject: Re: [Flashcoders] Flair Pattern bad mixins good (?)
Been a while since I've posted here, a few years I think. I miss
the geek
tangents / debates. =)
Good man! Seriously, the world affords precious
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of T.
Michael
Keesey
Sent: Tuesday, January 30, 2007 9:00 AM
To: Flashcoders mailing list
Subject: Re: [Flashcoders] Flair Pattern bad mixins good (?)
How is this any different from a Decorator/Wrapper
Yeah, the GoF book is definitely like reading a calculus textbook. It's
dry and to the point and the examples are in Smalltalk and some C++,
which means a lot of cross-referencing with google. The concepts they
discuss and the examples they give are helpful to a point but code
examples you can't
If you feel like this:
GoF makes me very sleepy - I find it very dry and the chapters very long
winded. (Sorry GoF'rs)
then:
I would be interested to know if Head First Design Patterns follows the
same process as Moock - learn by doing. I can handle that, although I
will keep delving
, which is nice. Is this the one by the
GoF?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Glen
Pike
Sent: Wednesday, January 31, 2007 12:57 PM
To: Flashcoders mailing list
Subject: Re: [Flashcoders] Flair Pattern bad mixins good (?)
My 0.02:
GoF makes
In addition the the books already mentioned, I highly recommend
Refactoring by Martin Fowler and Refactoring to Patterns by Kerievsky
(in that order). Together they show you how to adapt code you've
already created to design patterns without breaking it in the process.
The examples are in Java,
On 1/29/07, David Ham [EMAIL PROTECTED] wrote:
startObjectDrag triggered by obj_mc.onPress
checkForSnaptriggered bysetInterval or onEnterFrame type of event,
in this case onObjectDrag
stopObjectDrag triggered byobj_mc.onRelease
This looks more like the Broadcaster pattern or
Hi,
maybe a dumm question but would it be off limits to express this
changing-behaviour in the interface?
For example in such an object as you are describing, you could add a method
setResizeBehaviour(r:ResizeBehaviorImpl) (in pseudo then).
Then you can change a certain type of behavior at
mailing list
Subject: Re: [Flashcoders] Flair Pattern bad mixins good (?)
OK, this is helping a lot. And Steven I see what you mean, poor Flair
is starting to look a little meager now.
In my app, I have several different states. Each state sets itself
up by initializing variables and drawing its
classCMethod():Number{...};
}
-erik
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of T. Michael
Keesey
Sent: Tuesday, January 30, 2007 12:09 AM
To: Flashcoders mailing list
Subject: Re: [Flashcoders] Flair Pattern bad mixins good (?)
On 1/29/07, David
, January 30, 2007 12:09 AM
To: Flashcoders mailing list
Subject: Re: [Flashcoders] Flair Pattern bad mixins good (?)
On 1/29/07, David Ham [EMAIL PROTECTED] wrote:
startObjectDrag triggered by obj_mc.onPress
checkForSnaptriggered bysetInterval or onEnterFrame type of event
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of T. Michael
Keesey
Sent: Tuesday, January 30, 2007 9:00 AM
To: Flashcoders mailing list
Subject: Re: [Flashcoders] Flair Pattern bad mixins good (?)
How is this any different from a Decorator/Wrapper? Looks like a
double decorator.
On 1/30
PM
To: 'Flashcoders mailing list'
Subject: RE: [Flashcoders] Flair Pattern bad mixins good (?)
A decorator is meant to be dynamic. It adds responsibilities to an object at
run time.
You take ComponentA and add methods to it on mouseclick, that's a decorator.
ComponentB is made up of ComponentC
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Erik Bianchi
Sent: Tuesday, January 30, 2007 1:49 PM
To: 'Flashcoders mailing list'
Subject: RE: [Flashcoders] Flair Pattern bad mixins good (?)
A decorator is meant to be dynamic. It adds responsibilities to an object at
run time.
You
:[EMAIL PROTECTED] On Behalf Of JOR
Sent: Tuesday, January 30, 2007 3:55 PM
To: Flashcoders mailing list
Subject: Re: [Flashcoders] Flair Pattern bad mixins good (?)
A decorator object composites the object it wishes to decorate and is
used in it's place. Since the decorator inherits from
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of JOR
Sent: Tuesday, January 30, 2007 3:55 PM
To: Flashcoders mailing list
Subject: Re: [Flashcoders] Flair Pattern bad mixins good (?)
A decorator object composites the object it wishes to decorate and is
used
Been a while since I've posted here, a few years I think. I miss
the geek
tangents / debates. =)
Good man! Seriously, the world affords precious few opportunities to
truly geek out on design patterns and such. Internet mailing lists
excepted of course.
I have the Head First Design
The Head First Design Patterns book rocks and I definitely recommend it
to anyone wanting to learn about design patterns. I actually got a kick
out of the clip art and humor but I'm kind of quirky that way I guess.
The Java examples were trivial to port to ActionScript and a good exercise.
To: Flashcoders mailing list
Subject: Re: [Flashcoders] Flair Pattern bad mixins good (?)
Been a while since I've posted here, a few years I think. I miss
the geek
tangents / debates. =)
Good man! Seriously, the world affords precious few opportunities to
truly geek out on design patterns
Anyhow I tend not to use decorators (matter of personal taste). I
prefer to
not Frankenstein an object at runtime and rather use mixins
(composition +
interfaces).
Ah, thank you, now we are getting somewhere!
Tell me about mixins. I have used EventDispatcher before, but I am
unfamiliar
some typos. =)
-erik
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David Ham
Sent: Monday, January 29, 2007 7:12 PM
To: Flashcoders mailing list
Subject: Re: [Flashcoders] Flair Pattern bad mixins good (?)
Anyhow I tend not to use decorators (matter
Erik Bianchi wrote:
The theory of mixins originated from multiple inheritance programming
languages such as C++.
So for example: Say you wanted to make an object dragable, clickable and
resizable. You would then create separate classes called: Dragable,
Clickable and Resizable (common naming
mailing list
Subject: Re: [Flashcoders] Flair Pattern bad mixins good (?)
Anyhow I tend not to use decorators (matter of personal taste). I
prefer to
not Frankenstein an object at runtime and rather use mixins
(composition +
interfaces).
Ah, thank you, now we are getting somewhere!
Tell me about
24 matches
Mail list logo
