Re: [flexcoders] Re: AS3 Question

Sat, 12 Aug 2006 10:47:18 -0700

Tim,

> good to see you back from the component exclusive world.

Well, it was more of a 'had to answer most of questions world'.

I don't know, you are out in lala land creating and using things that are new, it gets lonley sometimes.-)

Really, I have been working on components, I had to turn the lists off for awhile ;-)

Now I know tens times as much and still more to go!

Geoff,

Yeah, I didn't mean to say you 'can't, just that it was the source of the error.

Peace, Mike

astgtciv,

> psychological aspect of "loss of control" and the associated discomfort is definitely there for me.

I had the same thing going. Give yourself time and you will get it. I mean the horse and carriage to a car gave people A LOT of feelings of no control. But, time changes everything and programming is bound to change with it sometime.

MXML from the stand point of layout has nothing to do with loss of control. You need to look at it as automation. All design patterns still fit, just are a different color. And nowhere does it say that any of your controllers have to get muddled in the MXML. This is like going into space and experiencing no gravity for the first time. You are still a human in space but the 'pysics' are different and you have to get used to them.





On 8/12/06, astgtciv <[EMAIL PROTECTED]> wrote:

This is actually a very interesting discussion to me, because
psychologically I've been going through the same "uncomfortability" learning
curve with MXML. I am coming from a "pure" AS2 background (and Java before
that), where I prefered to contain as much code as possible to my classes.
One psychological aspect of this approach is that you as a programmer
control exactly what your code is doing, you know every single little thing
going on because you wrote the code. When mxmlc started to generate
initialization code "behind the scenes" it made feel uncomfortable, and I am
still trying to get over this feeling by reading the mxmlc-generated
actionscript (which isn't exactly transparent in terms of understanding
either). Yes, certainly MXML is so much more preferrable in terms of layout
to pure AS, but the psychological aspect of "loss of control" and the
associated discomfort is definitely there for me.

When you work with an framework which does a lot of things for you, the
mindset is somewhat different from the "ground-up total control approach".
Certainly, the things that the frameworks authors thought about when
desigining the environment are so much simpler to implement that the choice
should be clear. But often, as soon as you (the developer) slightly deviate
from the path intended for you by the framework designers, you get into the
game of trying to fool the framework into doing what you want. This pattern
of reasoning is really very different from the "total design" pattern that a
developer has go through in the "ground-up approach".




--
What goes up, does come down. __._,_.___

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com



YAHOO! GROUPS LINKS



__,_._,___

Reply via email to