How about having one layer that includes all .as files on stage?

[3Dimitri]

I don't write in classes and I thought, to orginize code well, (I write everything on timeline, moviclips and so... I don't have classes and stuff in my programs), wouldn't it be a good idea to just have one layer on timeline, that says:

     include this.as

     include that.as ....

And the files are written as it would be written on main timeline.

Rather than having lots of class files, what requires (for me) more knowledge, isn't it a good idea to include those .as or .txt whatever files and have things orginized like that?

Also does it slow down the running process?

[Ned Murphy]

What is the problem with having more knowledge?

[3Dimitri]

I am limited with the time for the project I'm working for now.Thank you for your cool answer, but that does not satisfy me. Point is,  I need to now, if including code slows down the program lot. If it does, I will have to do as I did before, Mr. Ned.

And I'm talking about the benefits between classes and this type of writing...

[Ned Murphy · Accepted solution]

When you are running a file, the running of it is independent of where you put the code.  Whether it is internal or external beforehand, it is all rolled into one file (the swf or executable) after compilation.

While it can depend on the size of the project, working with class files is considered the more efficient approach.  In any case, whatever meets your needs and abilities should be sufficient.  It is not really a matter of where you put the code, but the quality of the code that you put.

[3Dimitri]

OK, I'll keep that in mind. Thank you for your explanation.