Aw_Shucks saidI’m also making the move from timeline coding to OOP . I totally agree with Ben, moving away from the timeline gives you unparalleled coding freedom. It’s a more… elegant way of coding ... my point is, Paul, let OOP be your best friend
Enabled saidActually, I found out that accessing particular objects on stage is much easier when using OOP in comparison to timeline coding. Things like “parent” and “addChild” are more complicated when trying to accomplish targeting objects than with the more convenient structuring of a well organized external class.
Do you think the method I am applying is a good one ? I’ve made templates for customers, but that is a whole other thing. As for external classes they are not quite my thing yet. I am still learning OOP , there are a lot of things that don’t quite come out as I want them too. Plus, OOP or Timeline, the end result can still be the same. The difference, and I agree is in the speed of coding and code re-usability but for the rest, same result can be achieved with OOP as with timeline coding
Sooner or later, yes. At the moment, I am quite satisfied with timeline coding I know what OOP can do, but for the time being, I am still at my beginnings.
No offense taken. Our wiki was fine when there wasn’t much info, but now that there’s so much more, it’s a mess. We’re in the final stages of creating a new, easier to use, one.
Regarding your question about PHP , any PHP functionality must be stripped out for the preview. For example, if your file calls dynamic content from a database, for the preview, call static content instead. In those very rare cases where this can’t be done, you can put your file on your own server. If you feel that you really need to do this, just explain to the reviewer why you’ve done so.