Read more of this story at Slashdot.
There’s a meeting this Thursday at 7 pm at Omni. I’ll be doing a talk about Vesper syncing. I suspect that the talk may take a turn into a general discussion about CloudKit, Swift, and other WWDC announcements.
Afterwards we’ll go the Cyclops, as normal.
We don’t use a regular UINavigationBar with Vesper. (We don’t even use a UINavigationController.) What appears to be the navigation bar is a custom view that doesn’t descend from UINavigationBar.
The reason for that is that we have transition animations that I don’t know how to do using a UINavigationBar. Here’s a screenshot of the navbar as you’re swiping back from detail to timeline view.

Note that the < and + buttons are at full opacity and don’t move, while All Notes and the icons are in mid-fade. (And All Notes is moving from left to the middle of the navbar.)
The reason for this is that the leftmost and rightmost buttons appear in both timeline and detail view, and in those same locations, so it’s nice that they don’t animate at all.
My question: is there a way to accomplish this using a real UINavigationBar? I like custom UI and our design, but I’m much happier when the implementation can be based on the standard stuff.
I think I made the right call — the only call possible. But I’d love to be wrong.
Read the full article at TidBITS, the oldest continuously published technology publication on the Internet. To get a full-text RSS feed, help support our work and become a TidBITS member! Members also enjoy an ad-free version of our Web site, email delivery of individual articles, the ability to make long comments with live links, and discounts on Take Control orders and other Apple-related products.
Read the full article at TidBITS, the oldest continuously published technology publication on the Internet. To get a full-text RSS feed, help support our work and become a TidBITS member! Members also enjoy an ad-free version of our Web site, email delivery of individual articles, the ability to make long comments with live links, and discounts on Take Control orders and other Apple-related products.
Read more of this story at Slashdot.
JavaScript is nobody’s first choice of language. (Almost nobody, maybe. There’s always a language you like better.)
But it’s everybody’s second choice of language — for the simple reason that everybody thinks that it’s everybody’s second choice of language.
(Maybe this is too clever to be true. Working on it.)
JavaScript is nobody’s first choice of language. (Almost nobody, maybe. There’s always a language you like better.)
But it’s everybody’s second choice of language — for the simple reason that everybody thinks that it’s everybody’s second choice of language.
(Maybe this is too clever to be true. Working on it.)
Instead of diving right into Swift by writing Vesper for Mac, I’m tempted to do a warm-up project first, just to get the hang of the language.
Of course Swift supports #! scripts, you can immediately execute a swift script with "xcrun swift -i".
What’s the obvious thing to do? I could replace my Ruby-based static blog generator with Swift code.
I probably won’t do this. But I’m tempted — and I bet somebody does this.
Instead of diving right into Swift by writing Vesper for Mac, I’m tempted to do a warm-up project first, just to get the hang of the language.
Of course Swift supports #! scripts, you can immediately execute a swift script with "xcrun swift -i".
What’s the obvious thing to do? I could replace my Ruby-based static blog generator with Swift code.
I probably won’t do this. But I’m tempted — and I bet somebody does this.