coreycollins

This is awesome!

I actually think it's genius. Mocking himself a little bit and other sites that display testimonials. It caught my eye and I signed up because of it.

There has been a lot of talk that these glasses will connect via 3g/4g and have different sensors to improve the augmented reality experience. Why not just have a display, power source, and bluetooth module? Then use your phone for the difficult computing.

I built it mostly because my biz partner and I wanted to know when a file changed in a shared folder. We use markdown a lot for meeting minutes, discussions, etc...and sometimes i missed (or just didn't pay attention) to growl on my mac.

This way I had a persisted copy so it reminded to check out the changes.

Dropbox only has a RSS feed for activity that I just wouldn't pay attention to either.

Any feedback is much appreciated. Just a small side project.

For not being designers, the UI/UX is fantastic! Great work guys.

I cringe at the thought of putting versioning gates all over my code, but maybe that's the easiest solution.

What about having two code bases on your production server and having your web server (nginx) route the traffic accordingly? 85% goes to the current code base and 15% goes to the new one?

If that's possible it would seem pretty easy.

The article discusses deploying to a percentage of your user base at a time. I have an idea on how to do this, but it is probably the wrong way.

Anybody know of any articles explaining this process for a rails app?

I was cringing all the way down through this article. Thank god for the last paragraph.

Were talking about iOS and the Interface Builder, not MacOS. I do not develop apps for the Mac, but I agree using Interface Builder would make sense for "larger" screens with more ui elements. To be clear I used Interface Builder for over a year until I decided it was better for ME to programmatically add ui elements.

I think during XCode3 I just really started to hate NIB's haha. They seemed slow to initiate and load. I admit that i haven't yet used Interface Builder in XCode4 and it apparently has fixed a lot of those "weird" bugs.

Your analogy doesn't really apply since you still have set the properties in Interface Builder. It's more like i'm just using a different stove. It does some, but not all. And most of the steps it does do are default for the class anyway. I like the finer grained control. If you're used to it the time difference is negligible.

I admit I did stop using it during XCode3. I got so use to it I haven't yet used it in XCode4. I meant it more as a better way to understand the iOS view hierarchy, not necessarily the faster way to build apps. But building faster apps doesn't make them better.

I find that added generated NIB files just dirty the code base. Of course this is just my preference. However, when I was a beginner, beginning to create more advanced views, I found it easier to programmably add them then to use Interface Builder. I like to be in control of my views and it helps me better visualize the view hierarchy. One example, was trying to create a UITabController with UINavigationController's for each tab. It can be done with Interface Builder, but it takes a lot of steps.

Yep, sorry. Interface Builder. Shows how much I use it haha.

The one thing I would recommend people do is not use Interface Designer. It bloats your code base and adds more complexity to the view hierarchy. It might be good to quickly mock-up a prototype, but not much else.