Kudos to the Bitrise team for creating a spot on kickass solution for Continuous Integration in mobile. All setup in less than an hour without any hassles… Using them is a must for any team!
So happy I’m joining @TheHackTrain to go #HackTheRails on the 4th of November. It’s a great honour to be invited to an event as awesome as this! I’ve already got my hi-tech travel bags packed I’m so excited…
Normally, developing a keyboard interface starts with putting a UITextField, a UITextField, or another UIResponder into your application’s view hierarchy…
And then this component becomes a statement: “From here forth, I declare this view to be a keyboard input view”. Except… Well… it isn’t, or at least doesn’t act like it. Unless you manage the layout of your content by implementing your keyboard notifications, the app’s main view will not respond or adapt to the keyboard update, and all sort of messed up situations can arise from this, like the keyboard overlaying your UITextField, UIScrollViews not being able to scroll or UITableViews not being able to display their last rows of content.
The use of subscripts in Swift has added a few nice features to its predecessor in Obj-C, not only for reading, but also for writing your own implementations.
If you are not familiar with subscripts, they define the logic that allows you to write shortcut accessors and setters for objects that can be understood as a collection, and are most commonly used in Arrays and Dictionaries:
var array = ["Hello", " ", "World", "!"] array //subscript returns "World" array = "Everybody" //The word "World" is now replaced with "Everybody" using a subscript