11–20 of 21 posts
Nice work. Keeping animation in the presentation-layer makes sense for 90% of the projects. Any reason for the iOS 7 requirement?
For anyone building the sample project getting _vImage related compiler errors, link Accelerate.framework. I can't figure out why that's an issue though — URBImageMediaViewController (dependency where the error comes from)'s sample project doesn't link against Accelerate.framework either, but it builds fine.
Hey Max, are you talking about the Ripple demo or the Canvas one? I'll definitely look into that. :)
Canvas one.
Nice work. Keeping animation in the presentation-layer makes sense for 90% of the projects. Any reason for the iOS 7 requirement?
Never tried that component, but not being able to set a custom font for a text view is such an obvious miss for an OS that claims to be so much text oriented. I can't count the number of times i've had to bind a UILabel into my code just to set the font. I know, UIApparence should be the way to set fonts everywhere, but that defeat the purpose of rapid prototyping IB is made for.
Can't you just use an attributed string? Xcode lets you pick a font using the standard system font picker then.
Never tried that component, but not being able to set a custom font for a text view is such an obvious miss for an OS that claims to be so much text oriented. I can't count the number of times i've had to bind a UILabel into my code just to set the font. I know, UIApparence should be the way to set fonts everywhere, but that defeat the purpose of rapid prototyping IB is made for.
(but yes, I agree, that it has taken this long is crazy)
Nice work. Keeping animation in the presentation-layer makes sense for 90% of the projects. Any reason for the iOS 7 requirement?
Nice work. Keeping animation in the presentation-layer makes sense for 90% of the projects. Any reason for the iOS 7 requirement?
Using the new keyframe animation API by the looks of things.