There are those who defend coding outside of the timeline and there are those who don't... I don't. You should feel good about being able to code at all, and you can work on learning to code outside of the document as you go as well.
Another approach for having a document class or code in the timeline is to keep everything in one frame and manage it all there. This can involve dynamically adding/removing content as needed, controlling visibility, and switching child indices.
As far as converting the code to work on the main timeline, if you are familiar with timeline coding, then you might be able to see it more clearly if you remove all of the class file dressing (the "package", "public", "private", and structural braces). A number of import statements become unecessary when working in the timeline, but having them does no harm.
Thanks for the encouragement Ned. I do like coding on the main timeline because it is so much easier for me to understand what I have going on. I was however able to get my classes to load using some import statements and creating a new var and then using addChild to load it. Thanks again.
"Do, or do not. There is no try." - Yoda
Sent from my iPhone