?

Log in

No account? Create an account
An Appropriate Coding Class - Redhead Rantings [entries|archive|friends|userinfo]
Lanette

[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

An Appropriate Coding Class [Sep. 26th, 2007|09:03 am]
Lanette
[Current Mood |relievedrelieved]


I'm taking more training on ActionScript 3, which isn't really scripting because it is a full Object Oriented Programming language. My first class was on Flex Builder, which is a program for rapid application development,..well, mostly it allows you to create UI and add action scripts to it. I would say that if you don't know much ActionScript, you aren't going to get far with Flex. Well, in that class the ActionScript made me want to cry because we were trying to do things with the language out of any context. That is NOT the appropriate level for someone just starting.

Now I'm taking an online course on ActionScript 3 in the context of Flash. What a relief. Yes,. it still is hard. Yes, I still don't love it. However, as someone starting out it really makes more sense to hook up variables with multiple objects that I can actually SEE on a stage instead of trying to create my own application out in space with no tangible examples that I can see visually. For someone new, seeing something like,..wow, there is my button, then writing code for what it does in different states is way easier than imagining what it will be like some day.

Also, using debuggers makes me want to cry. That is the one part of Flex I hope to not see for a long, long time. I know that they are supposed to be helpful. Whatever, it's like a chattery aunt who spews 99% crap and tells you something very critical 1% of the time and you are supposed to filter her chatter. Well, there is no way to debug the code in Flash except manually, so THERE! I get to work with no aunt for awhile until I get a better feel for what I should be looking for. Her chatter was so annoying.
LinkReply

Comments:
[User Picture]From: thought1
2007-09-26 05:10 pm (UTC)
Actually, you just described a bad (aka "primative") debugger. A good debugger just shows you the pieces you want, goes right to the point you want, and then lets you drill down and explore as you feel the need. The whole point of a good debugger is to hide all the crap and only expose the stuff that directly supports to what you're doing.

That said, most debuggers aren't good. );
(Reply) (Thread)
[User Picture]From: starrynytes4me
2007-09-26 05:19 pm (UTC)
I am sure if you asked those who wrote the debugger, the issue is my lack of ability to use it correctly ;)

It may have many wonderful options which I am unaware of, but the defaults sure suck.
(Reply) (Parent) (Thread)
[User Picture]From: shonao
2007-09-26 07:45 pm (UTC)
However, as someone starting out it really makes more sense to hook up variables with multiple objects that I can actually SEE on a stage instead of trying to create my own application out in space with no tangible examples that I can see visually

*giggle* The hubby is a robot that sees everything in code, so he would be baffled at this statement ;)
As for me, I'm with you...I work/learn better with a visaul to go along with what I'm trying to figure out!!!

Good luck!
(Reply) (Thread)
[User Picture]From: starrynytes4me
2007-09-26 08:01 pm (UTC)
I've heard that from other people who already know object oriented programming. You have to understand though, I was a graphic design major. Writing code for a living was not in my plans (ever).
(Reply) (Parent) (Thread)
[User Picture]From: shonao
2007-09-26 08:39 pm (UTC)
I do understand, which is why I laughed! It's the hubby that is the robot, not me! *lol*
(Reply) (Parent) (Thread)