Comments for Ziray Studio Labs

Comment on Handling Your Initial View Controllers for iPhone by Luc Juggery

Luc Juggery — Sun, 05 Feb 2012 20:35:00 +0000

Hello again,

I think I figured it out, I had a bad UIWindow / MainViewController as I though. But do not hesitate to tell if you see something strange in the gist

Cheers,
Luc

Comment on Handling Your Initial View Controllers for iPhone by Luc Juggery

Luc Juggery — Sun, 05 Feb 2012 09:09:41 +0000

Thanks Mike, that clarifies things.

In my current iOS app project, I am doing the switch of views (login / tabbar) in the app’s delegate, I know that is not clean and that really bugs me
Reading your article I started changing this to use a MainViewController object because your approach is really clean (thanks).

I have a problem though as I do not see my views anymore (black screen) when is app is ran, there is a link I probably missed somewhere

I do not have any MainWindow.xib file so I’ve done the linking programmatically (pretty user this is this part causing problem). I’ve written the main stuff in this gist: https://gist.github.com/1744267

Would you have any idea of what is missing ?
Thanks a lot for your help.

Luc

Comment on Handling Your Initial View Controllers for iPhone by Mike

Mike — Fri, 03 Feb 2012 18:36:26 +0000

A sign up view is just another view on the stack of other views. For usability reasons, I would include it as a subview or subcontroller of the login view. This is because it’s likely a new user would not be logged in, thus shown the login view. The login view would then have a link to a signup view. The login view would thus be responsible for login and signup. I would probably break this out into a UserAccountController that will handle communication with the server to handle login/authentication, signup and any other account tasks you need to handle. Under the UserAccountController you could have your ViewControllers to handle display and control of the appropriate views (Login, Signup, Edit Account).

I hope that made sense. Thanks for the comment!

Comment on Handling Your Initial View Controllers for iPhone by Mike

Mike — Fri, 03 Feb 2012 18:32:16 +0000

The Window object itself is the one and only Window in your application. The Window needs a root view to begin displaying content and maintains a pointer to its root view. The tab bar controller’s view needs to be that root view to work properly, in some cases. However, your Root View Controller class can set the Window’s view to any other view it has access to. So, you use your root view controller to handle what view becomes the Window’s view and swap it out according to your needs.

Great question! I hope that cleared it up for you.

Comment on Handling Your Initial View Controllers for iPhone by Mike

Mike — Fri, 03 Feb 2012 18:26:13 +0000

Storyboards affect it a lot. In the method I used, I usually add my Views and ViewControllers programmatically. I actually don’t do a whole lot in Interface Builder unless it’s an actual and complex interface. If you want to use the new Storyboards method, you can setup your storyboard to handle the different view controllers, depending on the organization of your storyboards. However, that’s up to you and you can always choose to do anything programmatically to get things up and running and then switch over or vice versa.

Comment on Handling Your Initial View Controllers for iPhone by Luc Juggery

Luc Juggery — Fri, 03 Feb 2012 08:59:52 +0000

Hello Mike,
just another question.. if you were to add a signup view, how would you add them in the picture ?
Thanks again,
Luc

Comment on Handling Your Initial View Controllers for iPhone by Luc

Luc — Thu, 02 Feb 2012 14:58:23 +0000

thanks for this great tutorial. I managed to have the loginView / tabBArcontroller switch in my apps but I was sure I did not do it in a right way. Stacking the views makes things a lot clearer.

One thing I’m still not confortable with is the rootViewController object, I do not really understand when you said (talking about the tabBarcontroller) “It needs to be the root view of your window, but that doesn’t mean it needs to be the root view controller.”. Would do you mean ?

thanks, that’s great stuff,
Luc

Comment on Handling Your Initial View Controllers for iPhone by LM

LM — Wed, 01 Feb 2012 08:39:43 +0000

how do storyboards affect this

Comment on Corona Game Template in Lua by Jolxy

Jolxy — Wed, 18 Jan 2012 12:04:06 +0000

Hi I find it very use full but i noticed you forget the buil, and the config file out of your frame work template.

Comment on What’s Wrong with this Scuba Diver? by Some Blowhard

Some Blowhard — Fri, 14 Oct 2011 11:17:38 +0000

Right on, I didnt want to come off as condesending in my observations, but is fustrating when seeing this sort of thingfor me aswell. A picture is worth a thousand words. Your pic is a perfect “dont do what donnie dont does” moment. As a rescue diver, I single these sorts out when I dive, as they stick out like a sore thumb. Wrestling your primary out of your mouth when hes OOA, or shooting straight to the top when it all goes bad, is inevitable. I suspect his buddy was not visable in the uncropped version of the photo either? Possably wandered off to do his or own thing somewhere else? That was my other point about the buddy thing. To be fair to this guy, it might not be all his fault. Here in FL you could trip and fall on three or four splash and dash dive shops almost anywhere. For $100 they toss em in the water and give them a c-card when they get out, about a dozen at a time, mass producing like a chineese nic-nac factory. He might just be a victim of casual indifference. Just my $0.02.

Comment on What’s Wrong with this Scuba Diver? by Mike

Mike — Mon, 10 Oct 2011 03:28:36 +0000

I took this photo of this diver who was from another dive boat in the area. I looked over, couldn’t believe what I saw and snapped a picture because no one would ever believe how bad this guy was. There’s a lot wrong with his dive buddy too, you’re definitely right about that!

Comment on What’s Wrong with this Scuba Diver? by Some Blowhard

Some Blowhard — Sun, 09 Oct 2011 20:16:14 +0000

Let’s see, Hmmm…., Where to start? Well, the most glaring problem must be the clueless location of the alt 2nd stage. “Walking” across the bottom is a bad idea, stiring up lots of silt, limiting vis. The “walking” effect being demonstrated is probably a by-product of over weighting/ poor bouyancy control. Tank retainer strap appears to be coming loose, so the allready low hanging tank slipping out of his bcd could be exciting for him. I will assume his “buddy” is the one taking the picture, as opposed to a passer-by. His buddy not sorting out his kit is a problem. Prehaps he’s drunk?, I don’t know.

Comment on Custom Mouse Cursor for ActionScript 3 by polo90

polo90 — Sun, 28 Aug 2011 06:16:25 +0000

I got some issue with the custom cursor and the arrow blinking together. After reading your example, It turned out that mouseChildren = false is critical to stop that blinking.

thanks man!

Comment on Photos of the Week – Summer by Photo Challenge: Summer Holiday « Sam Knapp

Photo Challenge: Summer Holiday « Sam Knapp — Sat, 13 Aug 2011 01:50:36 +0000

[...] my sister and mother who live in the area. It was time well spent. Here are Mike Ziray’s submissions. If you have a Facebook account, here is our Facebook group. #gallery-1 { margin: auto; } [...]

Comment on Naming Conventions – Why Your Code Sucks by Mike

Mike — Thu, 28 Jul 2011 21:31:39 +0000

I always appreciate people willing to disagree with me! You’re right about that SDK that uses Lua. Out of curiousity, which one was that? I’ve programmed a game in Lua, so I know the language, and I suppose what you’re saying is, because it’s not compiled and instead included with the app, the character count in the code matters. I’m not sure why you’d have that kind of restriction these days, so I’m curious.

Also, I believe you’re talking about the overhead of referencing and retrieving variables from encapsulated classes. If performance matters to you, there are ways to speed that up. One is to simply get a pointer to the object and store it locally, and another is to copy the data to a local variable and pass back the value when you’re done.

OOP does have a slight overhead in exchange for better maintainability in your code. However, it doesn’t matter how fast your code is if it’s not maintainable or buggy. But there are plenty of software engineering concepts you can use to speed up your code without making it ugly and unmaintainable.

When you program in a large team, they all have coding practices that you must follow. This is nothing new, this is just my way of doing things for people who haven’t been exposed to these concepts. So feel free to disagree, but each guideline is explained on why I use those methods.