This morning Paula asked me to create a demo project for Particle Playground so users can simply import their emitters and see how it will look on the device. This should be especially interesting for heavy-duty emitters (
birthRate > 500 or high
velocity). Naturally I created a small Xcode project for you to download and play with.
For my latest app I wanted
UICollectionView to behave like a
UITableView in respect to its headers sticking to the top of the screen. Well, actually I wanted my collection view to scroll horizontally and therefor have the header cells stick to the left side of the screen.
I spend quite a few bucks on the image assets of my apps and most of the time I spend these bucks at iStockphoto. The site has loads of great content and you can find good quality images for virtually any intended use. There is only one thing I would like them to improve – the preview area for images is way too small.
Since I am in the process of finishing my first Mac App now is the time to create the image resources for the app. Along comes the old problem/annoyance of manually resizing and renaming app icon files. After a little googling i got some solutions but most of them were just for iOS, so I had to adapt one of them to my needs.
In my new Mac App I have an image well where the user can drop images and – at a later time – export the whole project to code. I was rather surprised to find out that the
NSImageView does not (to my knowledge) save or communicate in any way the filename of the dropped file.
Let’s say your app needs a custom struct. Maybe for upper/lower bounds of some values. Let’s also assume that you – like me – don’t like the thought of abusing
NSPoint just because ‘It fits the problem’. Yes, you could store your two values in both structs, but the names would be wrong and in general: doing it would be wrong.
I updated KSLabel (a
UILabel subclass) to be more versatile and reusable. You can read about KSLabel right here. I added support for dynamic outline and gradient colors and uploaded it to github. Take a look and drop me a line if you like it or have issues with it. Continue reading
UPDATE: I changed a few things in KSLabel and uploaded it to github. This post is still relevant, but a little outdated. KSLabel now supports dynamic outline and gradient colors. Be sure to read the updated blog post after reading this post.
I have run into this problem a couple of times before. My friend and designer creates a beautiful image of an interface for me and I take a look at it and immediately realize that there is text with an outline and/or gradient.
I sigh on the inside because I know it can’t be inserted in the app as an image. The text needs to be localized and IMHO it’s not nice to localize images. I know that text outlines are the most basic thing for someone who is used to Photoshop and the like, but creating those for an iOS app can be a pain.
Just a quick tip I found out to make better use of space in my iPhone app. Consider the following situation: You have a Highscore View with a couple of stats of the game you just finished. Naturally you would like the user to be able to enter his nickname.
The input box is so far down in the view that it gets covered by the keyboard as soon as its activated. Now the user can enter his nickname but he can not see what he is typing. That is just not acceptable.
For a little side-project I wanted buttons to look like they’re being pushed ‘inside’ the interface when active. To match the overall look of the project the first step was to create two embossed images in Photoshop. One with emboss direction ‘up’ and one with emboss direction ‘down’. Then assign these images to the relevant control states of the button. Simple enough – and already looking the way I want it to. (Hover over the image to see what I mean.)