Well it been over 14 days and still no arcade game. How do I feel about this? It's more good than bad. I guess the bad part is that I haven't accomplished what I set out to do. The good part is that I've got a good understanding of the basics, and I think realistically it might take two to four weeks to pull some kind of game off. I'll post the code when I figure it out. Admittedly I haven't geeked out and stayed in a darkened room coding for the last 2 weeks. I've chilled out and done other stuff.
This what I've learnt:
1) There are alot more resources out there on learning AS 3.0 then there used to be when I first had a look around for books etc a couple of years ago. This is can only improve - even i have managed to write this blog and used open source tools to capture my screen and embed video.
2) To build even basic applications requires a very good understanding of AS 3.0
3) Workflow is important. By this I mean the approach you take in building your projects and knowledge in AS 3.0. OOP Projects require more that 1 file and this can get complicated when trying to revise code so achieves goals more efficiently. At the moment I'm using version control to keep succesful experiments.
4) Looking at step 3 means that the challenge to learn AS 3.0 would be very difficult for complete beginners to coding.
5) Get Moock's EAS 3.0, but get Learning AS 3.0 to jump right in too.
6) FlashDevelop isn't too tricky to get working and seems to do the job well (once you the trace working - i think this is easy and was just me being stupid) Couldn't get code indent to work that would have been nice.
7) Although AS 3.0 isn't something you can be expertise in in a week or two. I'm guessing that you could probably get some competence in the order of months (ok I know that remains to be seen). Contrasting this to learning a foreign language which is probably more approaching the order of years, for me, means it worth pursuing.
No comments:
Post a Comment