[_] any chance of a skillswap about flash OOP
juan kennaugh
contact at jkennaugh.co.uk
Wed Oct 17 13:54:58 BST 2007
1. Well - lots of the stuff I do have animations in movieclips and other things which can't be created with the drawing API. So lots of my stuff is taylor made to suit a particular job. So if I have to make a video player, it's easier just to stick and FLVplayer instance in a movieClip, stick some buttons in there and drop it on the stage. I could put all the code in an imported bunch of classes - but it's likely that next time I do a video player, it will by made differently - so unless I make an OOP video player that encompasses every possible use I could have for it, It would be quicker to just copy and paste some code and amend it. I don't really make applications (where I can see OOP would be really useful) 2. Am I right in thinking that those frameworks are just big sets of classes - when using them, do you just use the methods of the provided classes or do you extend the classes? Juan Jon Bennett wrote: >> Yeah - as little as possible on the timeline - but unless you've >> unlimited time and money to work on projects endlessly you can't really >> put every single thing in classes (it would be good for reusability, but >> it would take ages - I'm guessing). >> > > I dunno, for a long time now I've been doing things without any code > on the timeline, save for the odd 'this.stop()', what kinds of things > are you putting on the timeline? > > >> anyway - thanks for those links to those frameworks - but that just >> makes my life more complicated (something else to learn). >> > > ahh, well, I've found them a good route into extending my knowledge of > OOP in Flash, even if you only spend a couple of days with one. > > jb > >