I’m just wondering when Apple will be shipping the SDK for the ipod touch/iphone. Just being nosey really. I’ve veered away from jailbreaking it simply because I don’t want to end up with an expensive brick next firmware update.
They say February, but of course remembering that the Leopard launch being the end of the month it could be anywhere up to the 29th.
Another thing I’d like to see is the UI guidelines. I’m a bit of a nerd when it comes to reading design guidelines, simply because there are a lot of good points in them. Mind yo, you should not be slavishly obeying them, as, after all, they are only guidelines, and not commandments.
On guidelines, I’m get miffed with applications that require the use of the mouse to accomplish things. Vista’s keyboard usable everywhere is a charm to use, even while it’s gobbling up all those cpu and disk resources with the indexer.
Samba, passwords, permissions and leopard
Sometimes when people are using old painful versions of samba you can’t use the encrypted passwords to talk to the remote server. You just get a complaint that the password is incorrect all the time, even though you keep typing the damned thing in correctly.
What you need in this case is an nsmb.conf file in ~/Library/Preferences/. It needs to contain a stanza:
[host you care about] minauth=none
For every host that is not using high-falluting authentication. It would be better to not use a default entry here, as we want to ensure that the default attempt is not to try with unencrypted communications.
Whaddya mean no https
Leopard is not spiffy:
$ lwp-request -x https://mail.google.com/mail/ LWP::UserAgent::new: () LWP::UserAgent::request: () LWP::UserAgent::send_request: GET https://mail.google.com/mail/ LWP::UserAgent::_need_proxy: Not proxied LWP::Protocol::http::request: () LWP::UserAgent::request: Simple response: Internal Server Error 500 Can't connect to mail.google.com:443 (Invalid argument)
Update 2008-05-06: How I got it working for me. It’s not the cleanest, but it works!
In their rush to get the product out to the customers…
Apple have obviously made some significant backwards compatibility errors. Firstly, there’s the firewall – altering the on-disk content of applications to make them signed when you accept them. Its an interesting approach, but it’s complete pants. You don’t go around altering binaries on disk. You create a detached signature! It’s not really bloody difficult.
On Vista, you can see *every* rule that exists for the firewall. On Leopard, you only get to see the exceptions you created yourself.
I’ve been having random application crashes. They seem to be related to drag and drop operations that went wrong.
the calendar application does not want to talk to my instance of davical properly (all the calendars disappear after restarting, and I get an error every time I create a calendar).
Then there’s the ‘the application terminated unexpectedly’ – no, it didn’t, I used the <Apple>Q menu item to quit the application.
Context sensitivity on the mail application is kinda limited – It doesn’t detect URL links properly – I have a site that’s called http://foo4/…, and all the link comes up with is http://foo. As I said, a bit limited.
Overall, though, the experience is positive. I would have preferred if apple had simply spent some more time testing the damned thing against anything other than their own applications and services.
And, as soon as they allow a replacement for .mac that can be replaced with an external, non-proprietary service I’ll be a happier person