Yosemite Finder sidebar separators. Nice. Edit: doesn’t work for me. I get the separators but the .app extension still appears.
Lots of beta 4 changes. Look at Airspeed Velocity and Erika Sadun’s lists. To me the major changes are finally getting an equivalent to #pragma mark with //MARK: and changing how C strings are handled. As ever the language is still changing a lot so if you don’t want to keep up with all the changes I’d probably wait a few months.
Strings in Swift. Completely rewritten to account for all the changes in beta 4. I’ve not touched Swift after my initial bought of learning. I’m waiting for it to mature a bit before diving in it again. The problem of string indices and O(N) searching seems to remain a big problem though. Obj-C was always a lousy text processing language IMO. I wish Swift had more of the capabilities of Python in that regard. (Again – get me iterators and the yield statement)
- 41I’d mentioned in passing in one of my Swift posts about using it as a scripting language. Someone on Twitter asked me if I’d convert from using Python to Swift for my scripts. It’s an excellent question that I really can’t answer fully at this stage. The language is still very beta. Most of the…
Clever Python script to make an Emoji clock. If you were really geeky you could add it to your shell prompt.
Nice Launchbar action to do a Spotlight search. Why would you want to do it here rather than in Spotlight? It’s just a little easier as you can write out the query. If you haven’t looked, there are a lot of interesting Launchbar stuff upon on github.
On adding Applescript support to your app. (HT: Brent Simmons) I wish, wish, wish more apps added Applescript support. It makes things so much easier. If you’re doing small business software you absolutely should do this. Not because your clients will write Applescript but because they’ll get people to do it for them for automation. Especially to do repetitive actions with Keyboard Maestro. (I wish Daylite has better scriptability)
Nice list of what’s changing in Swift. (HT: Michael Tsai) I don’t think most changes will affect people’s existing code, but even so I’d be cautious about using it until things settle down a mite. And of course there are lots of improvements needed in Swift — especially in strings. The biggest flaw I see is the ambiguity about float sizes. The biggest change in beta 3 that will affect existing code is the change of the token for half-closed range operator. However that was so bad I’m still glad they changed it.
Could have sworn I’d linked to this before. But I guess not. It’s well worth reading. Reactive Cocoa in Swift. The biggest issue right now is that Swift can’t see macros in ObjC/C. Given some of the problems that introduces I’ll hold off until things get more mature. The linked article goes through workarounds but it’d be nice to have a Swift interface done for you. There’s at least one being worked on. An other post discussing Reactive Cocoa in Swift is here. For those just curious about Reactive programming this is a good defense.