I’m currently writing a program which takes input and simulates it back out as keyboard presses.
It’s quite easy, and can be done like so.
Safari applications seem to have a different scope between your target html page and main.js end script. This means that if you wish to inject a control onto your screen which calls a function in your main.js script it will not work because the two can’t see each other.
Over the Christmas holidays I was building an app in my own time and came across a bit of a common problem I wanted to solve – multiple PNG exports all at different sizes for graphics in an iOS app.
To learn GDK, first you have to understand the basic concepts and UI components. Once you understand these, things will start to make sense. Before i start explaining anything i would like to tell you that the GDK that Google released is just a sneak peak and it has a very limited functionality. This blog
In iOS7 a view controller now positions it’s view from the top of itself compared to previously starting below the navigation bar. If you use a single scroll view you can set automaticallyAdjustsScrollViewInsets to YES to automatically handle things for you, however if your UI is more complicated then you may need to do things manually. The view controller has a topLayoutGuide property which is useful in some cases, but unfortunately doesn’t take parent view controllers into consideration, or the view’s origin inside the view controller.
Don’t know what gifts to buy this holiday season? Keep reading…
In one of my recent projects I added a content inset on the top of my table to push the start of the content down. Unfortuantely when you set the content inset the table assumes that all your sticky section headers now also start from the end of the content inset. This was not the behaviour I wanted, and instead I needed them to stick to the top of the table where the cells start to go out of bounds.
Whenever you have a couple of apps that are extremely similar, it will make sense to share the code between the two. For example, a Lite version and a Paid version of the same app, or the same app skinned differently for different clients. At first you might be tempted in duplicating the project. Don’t. If the code splits then it’s going to be a nightmare copying changes between two places, or even just having them in two separate projects.
This is a real world iOS example, but can be applied to PNGs in any scenario.
In iOS the splash screen images have to be PNGs. This works great for simple images with just a few colors, but will result in huge PNGs if you plan on having photo content, especially on the retina iPad with a screen resolution of 2048×1536.
At first I figured because PNGs are lossless that there’d be very few ways to reduce the filesize. I am going to run through the well known ways and some others that were new to me.
Something I often see with pretty much every app on the AppStore with In App Purchases is that they don’t update prices if I login with an account linked to a different store than the one the prices have already loaded for.