Hear you loud & clear. All the best with the challenges ahead. Thanks for all that you are doing for this community. The new capabilities sound awesome. Can't wait.

Any news?

I'm having a lot of problems with it and doing a hard work on it. I'm thinking on releasing it only with the bug fixes and postpone the book feature. What do you think about it?

Hi Ricardo, sorry to hear about the trouble but I know how it goes. I think releasing a bug fix update that covers all the stuff that you've been fixing along the way and leaving the book feature for later is an excellent idea! Hope you can make it happen. Thanks much!

+1

Done!

http://developer.anscamobile.com/code/director-class-10

Thanks Ricardo :)

Amazing!!! Thats was real quick! Thanks much. Getting it now.

Please let me know if you find any issue.

Please let me know if you find any issue.

Many thx for the release.

Sorry, but I haven't found the release infos, to see what you have changed.

I have also noticed big changes in your samples codes (main, screens and template) : could you explain thoses ?

All the major updates were at the memory management and cleaning scenes.

1 - Now you don't need to modify Director to use the clean function, Director will search for it and if it find then will execute it.

2 - Cleaning scenes are divided in 3 steps:
2.1 - Execute the clean() function if it exists
2.2 - Remove all display objects inserted into the localGroup
2.3 - Unload the module and call the garbage collector

3 - I added a "safe time delay" to start transitions without crashing.

4 - You can change the effects time and safe delay via programming.

5 - There are 3 new transitions on changeScene:
5.1 - moveFromTop
5.2 - moveFromBottom
5.3 - crossfade

6 - A lot of people asked me about changing scenes like a book. I tryed to do it on this version but it is very hard to do. So, I put on the sample a little slider to see how to use moveFromLeft and moveFromRight to feel like a book.

7 - All the files on the sample are better structured and have the initVars() function to show how to start your variables values and use it on a pause or restart function.

8 - There is a boolean variable to prevent change scenes while it's still changing a scene.

Thx for the answer.
Looking at your template.lua :
- I don't see anymore the "--Put your code here--" : your new organisation let us put page code anywhere ?

You can follow the comments! The only things that you have to do is a new() function returning a localGroup and insert all your display objects into this localGroup.

With this new template, I'm suggesting a good structure to code your games. If you don't want all those comments, you can cut them off without any problem. This is a common practice at big enterprises to have a clean code that anyone can see and understand easily.

EDIT: Never mind. I hadn't clicked your link yet, so didn't realize you were updating the official Director page.
-----------------
Hi! Any way for you to create a "sticky" forum topic so that we can go to one topic at the top to find your latest update (or find any "official" comments you've made about your great product)?

Thanks for all your hard work!

I'm thinking on doing other video with some tricks to build an app with Director, any suggestions?

This is a common practice at big enterprises to have a clean code that anyone can see and understand easily.

It's exactly because of this, that I want to understand your template.lua :)

Your experience is a gem, and I'd really like to understand and follow the code structure you - so kindly- hint.

Moreover, director class deals with scene management, aka page organisation, aka code structure !
Therefore, I really think following your advice is a good thing.

Though, I must admit that the new template.lua is harder to understand than the previous. I guess I'll have to test/sample code to better understand initvars stuff and other things (like the listeners at the beginning of the code page).

Anyway, thx for your work ! (I'm one of those who would pay for this class :)

Thanks Antheor!

The new template is not so different of the other, it's just separated in "blocks". Let's go block-by-block.

1 - GROUPS

Here you can declare all groups that you will be using on the scene. Imagine if you have a game scene and you have a pause screen. You can divide them into 2 groups. All objects of the game you have to insert into the gameGroup and the objects of the pause menu into the pauseGroup. Also, these new groups must be inserted into the localGroup.

1
2
3
4
5
6
7

---------------------------------------------------------------
-- GROUPS
---------------------------------------------------------------
 
local localGroup = display.newGroup()
local gameGroup = display.newGroup()
local pauseGroup = display.newGroup()