Not using director or storyboard a bad idea?

#1

Sorry in advance for making so many posts, hopefully this is my last in which I require advice =(

For my app I have not used director or storyboard since the beginning. I have often checked my textureMemory and never saw a problem. As of my latest version I have:
4.4 system memory and
26.4 texture memory

I figured this is nothing at all. I heard 3GS starts having problems at around 25~ but that’s quite the old device and figured it wouldn’t be that big of a problem. Anyway my main concern is. I got an iPod 5th gen touch and have been testing my app for the past few days. From what I gather the 512 MB should run this app like nothing. But I have had 3 bugs in 2 days. Two of them my friend on his android has never had and he’s been testing it for weeks for me. Never happened in the simulator either. Let me explain:

Bug #1: Some icons would not have touch event listeners respond at all. No matter how I clicked the icon it would not do anything. The main problem here is that the icon loads from the very beginning and right after the icon is called the event listener is added as well. It doesn’t make sense that the listener would not work. Again this is only on the iOS from what I can tell, never happened on the android in weeks of testing for my friend.

Bug #2: Same as #1 except this time a new icon was loaded from a different icon but for some reason the listener was not added and I could not use the back icon to get out of that screen, therefor I was literally stuck on that screen because the listener didn’t load. Rebooted app worked fine.

Bug #3: My app froze on me when I clicked an icon and after a few seconds it loaded twice ( I clicked it mul;tiple times till I found out it froze).

My question is, could this be because I am not using director or storyboard to change scenes and have just one big layout? Here is my app (4mb picture):

http://img441.imageshack.us/img441/9587/lolapp.png

The first screen starts on the middle row, second picture. From there every single other block is it’s own screen except the top green picture which the size it specified. I figured since there are huge RPG’s out there it shouldnt matter if I create it like this but the bugs on the iPod had me wondering. I only ask this question because it would take some time to create storyboard for all of this and don’t want to waste the time if it in no way has to do with this.

If you need a live demonstration of the app here it is:
http://www.youtube.com/watch?v=6vli3bHocC4&feature=youtu.be

The listener thing just has me confused, it doesn’t make sense why something so simple would not load when it’s called most of the time right after the icon is created. Is it possible to have too many variables loaded at once? So my question is, do you think storyboard would be a better idea? The thing is people change screens often in my app. I’m worried if it takes 1-2 seconds to load each time, or more for slower devices(if it would even take that long), then it would get annoying to wait for load time. Any advice is much appreciated, feel free to ask me anything if you might have any ideas for improvements. Sorry again for the wall of text and thanks so much for any help [import]uid: 77199 topic_id: 36218 reply_id: 336218[/import]

#2

I never use Director or storyBoard. I don’t feel the need for this and find coding these things myself pretty easy and lean. [import]uid: 70134 topic_id: 36218 reply_id: 143878[/import]

#3

Thanks for the input [import]uid: 77199 topic_id: 36218 reply_id: 143980[/import]

#4

Heh :slight_smile:

You’re welcome and I’m sorry my reply was so short, but there’s not too much to say about it in my opinion. I just never felt the need to use Director or storyBoard.

Basically in my main.lua file I put a couple of short statements (e.g. to hide the statusbar) and then I just call something like:

local startMenu = require("startMenu")  
startMenu.popIntroScreen()

The function “popIntroScreen” in the module startMenu opens op the menu screen with a couple of options, and if for example the user chooses “play” from this menu I just close the menu, remove all sprites (preferably with a nice transition) and call another new function from another module like so:

local gameEngine = require("gameEngine")  
gameEngine.startGame()

This all seems so basic and logical to me that I don’t understand why people would need an extra layer of complexity on top. Changing scenes and all that… Sheesh… I just code everything so one screens pops up, and at the choice of a user, this screens dissolves, properly removes all display objects and eventListeners, and then the next screen pops up. It’s so simple that I don’t feel the need for extra frameworks.

Good luck!
Thomas [import]uid: 70134 topic_id: 36218 reply_id: 143983[/import]

#5

No no, it really did help even if it was a short message. I was just glad others don’t use storyBoard or director and that they don’t have any problems in doing so. I guess I kinda already knew there shouldn’t be a problem but than again this is my first programming language so it’s always nice to hear stuff from more experienced users. Thanks again for taking the time to reply and for the examples. Have a great weekend. [import]uid: 77199 topic_id: 36218 reply_id: 144056[/import]

#6

I never use Director or storyBoard. I don’t feel the need for this and find coding these things myself pretty easy and lean. [import]uid: 70134 topic_id: 36218 reply_id: 143878[/import]

#7

Thanks for the input [import]uid: 77199 topic_id: 36218 reply_id: 143980[/import]

#8

Heh :slight_smile:

You’re welcome and I’m sorry my reply was so short, but there’s not too much to say about it in my opinion. I just never felt the need to use Director or storyBoard.

Basically in my main.lua file I put a couple of short statements (e.g. to hide the statusbar) and then I just call something like:

local startMenu = require("startMenu")  
startMenu.popIntroScreen()

The function “popIntroScreen” in the module startMenu opens op the menu screen with a couple of options, and if for example the user chooses “play” from this menu I just close the menu, remove all sprites (preferably with a nice transition) and call another new function from another module like so:

local gameEngine = require("gameEngine")  
gameEngine.startGame()

This all seems so basic and logical to me that I don’t understand why people would need an extra layer of complexity on top. Changing scenes and all that… Sheesh… I just code everything so one screens pops up, and at the choice of a user, this screens dissolves, properly removes all display objects and eventListeners, and then the next screen pops up. It’s so simple that I don’t feel the need for extra frameworks.

Good luck!
Thomas [import]uid: 70134 topic_id: 36218 reply_id: 143983[/import]

#9

No no, it really did help even if it was a short message. I was just glad others don’t use storyBoard or director and that they don’t have any problems in doing so. I guess I kinda already knew there shouldn’t be a problem but than again this is my first programming language so it’s always nice to hear stuff from more experienced users. Thanks again for taking the time to reply and for the examples. Have a great weekend. [import]uid: 77199 topic_id: 36218 reply_id: 144056[/import]

#10

I never use Director or storyBoard. I don’t feel the need for this and find coding these things myself pretty easy and lean. [import]uid: 70134 topic_id: 36218 reply_id: 143878[/import]

#11

Thanks for the input [import]uid: 77199 topic_id: 36218 reply_id: 143980[/import]

#12

Heh :slight_smile:

You’re welcome and I’m sorry my reply was so short, but there’s not too much to say about it in my opinion. I just never felt the need to use Director or storyBoard.

Basically in my main.lua file I put a couple of short statements (e.g. to hide the statusbar) and then I just call something like:

local startMenu = require("startMenu")  
startMenu.popIntroScreen()

The function “popIntroScreen” in the module startMenu opens op the menu screen with a couple of options, and if for example the user chooses “play” from this menu I just close the menu, remove all sprites (preferably with a nice transition) and call another new function from another module like so:

local gameEngine = require("gameEngine")  
gameEngine.startGame()

This all seems so basic and logical to me that I don’t understand why people would need an extra layer of complexity on top. Changing scenes and all that… Sheesh… I just code everything so one screens pops up, and at the choice of a user, this screens dissolves, properly removes all display objects and eventListeners, and then the next screen pops up. It’s so simple that I don’t feel the need for extra frameworks.

Good luck!
Thomas [import]uid: 70134 topic_id: 36218 reply_id: 143983[/import]

#13

No no, it really did help even if it was a short message. I was just glad others don’t use storyBoard or director and that they don’t have any problems in doing so. I guess I kinda already knew there shouldn’t be a problem but than again this is my first programming language so it’s always nice to hear stuff from more experienced users. Thanks again for taking the time to reply and for the examples. Have a great weekend. [import]uid: 77199 topic_id: 36218 reply_id: 144056[/import]

#14

I never use Director or storyBoard. I don’t feel the need for this and find coding these things myself pretty easy and lean. [import]uid: 70134 topic_id: 36218 reply_id: 143878[/import]

#15

Thanks for the input [import]uid: 77199 topic_id: 36218 reply_id: 143980[/import]

#16

Heh :slight_smile:

You’re welcome and I’m sorry my reply was so short, but there’s not too much to say about it in my opinion. I just never felt the need to use Director or storyBoard.

Basically in my main.lua file I put a couple of short statements (e.g. to hide the statusbar) and then I just call something like:

local startMenu = require("startMenu")  
startMenu.popIntroScreen()

The function “popIntroScreen” in the module startMenu opens op the menu screen with a couple of options, and if for example the user chooses “play” from this menu I just close the menu, remove all sprites (preferably with a nice transition) and call another new function from another module like so:

local gameEngine = require("gameEngine")  
gameEngine.startGame()

This all seems so basic and logical to me that I don’t understand why people would need an extra layer of complexity on top. Changing scenes and all that… Sheesh… I just code everything so one screens pops up, and at the choice of a user, this screens dissolves, properly removes all display objects and eventListeners, and then the next screen pops up. It’s so simple that I don’t feel the need for extra frameworks.

Good luck!
Thomas [import]uid: 70134 topic_id: 36218 reply_id: 143983[/import]

#17

No no, it really did help even if it was a short message. I was just glad others don’t use storyBoard or director and that they don’t have any problems in doing so. I guess I kinda already knew there shouldn’t be a problem but than again this is my first programming language so it’s always nice to hear stuff from more experienced users. Thanks again for taking the time to reply and for the examples. Have a great weekend. [import]uid: 77199 topic_id: 36218 reply_id: 144056[/import]