andymatuschak.org: archive

You are at the archive for the September, 2008

To help mitigate risks, included in the free stay by sugarland ringtone document are security checklists with guidelines and recommendations for creating and maintaining secure Bluetooth piconets, headsets, and smart card readers.The passive attack allows a suitably equipped fre ringtones and wallpapers to eavesdrop on communications and spoof, if the attacker was present at the time of initial pairing.Wi-Fi Wi-Fi is more like a traditional pay for ring tones network, and requires configuration to set up shared resources, transmit files, and to set up audio links (for example, headsets and hands-free devices).4 GHz short-range radio ringtone riot bandwidth.adam brand ringtones

Sparkle 1.5b6 (hopefully aka “1.5rc”)

published on Sunday 14 September, 2008 at 11:42 am. {6 Comments}

Alright, folks, it’s been another few weeks, and it’s time for another Sparkle release! You can grab it here. I’m frozen on new code now, and there are no known bugs left, so unless there’s something critically wrong, this’ll be the last beta before 1.5 final.

Another piece of good news is that Sparkle’s documentation is finally coming together, and in wiki form. Check it out, and feel free to contribute.

Make sure you read the release notes thoroughly; the important thing to note is that DSA signatures are now required.

I could really use help from localizers on the remaining languages! If you are or know a localizer for a language Sparkle’s missing, please let me know.

Sparkle 1.5b6 Release Notes

  • Sparkle now requires DSA signatures on your updates. Check the documentation for more information on how to set that up if you don’t already sign your updates. You can bypass this requirement if you deliver both your appcast and your updates over SSL.
  • Sparkle will no longer display release notes located at file:// URLs, since Javascript on such a page would be able to read files on your file system.
  • For security reasons, Sparkle will refuse to install updates which appear to “downgrade” the app.
  • SUUpdater now implements new keys: “automaticallyDownloadsUpdates”, “lastUpdateCheckDate”, and “sendsSystemProfile.”
  • Fixed a bug that could prevent SUProbingUpdateDriver from working.
  • Fixed a bug that prevented the updaterWillRelaunchApplication: delegate method from getting called.
  • Fixed displaying release notes transmitted “loose” in the <description> key.
  • Fixed Sparkle compilation on 10.4 systems.
  • Fixed a bug that could cause window confusion if an app changed its LSUIElement at runtime.
  • Added support for Sparkle 1.1’s behavior of disabling updates when the check interval is 0.
  • Sparkle can now handle appending parameters to URLs which already have parameters.
  • If an update’s sparkle:shortVersionString is the same as the host’s CFBundleShortVersionString, the sparkle:version and CFBundleVersion will be presented in parentheticals.

HotCocoa Is Pretty Damn Hot

published on Friday 12 September, 2008 at 8:13 pm. {14 Comments}

A few days ago, MacRuby 0.3 was released. If you haven’t heard about it before, MacRuby is an implementation of Ruby 1.9 running directly on top of the Objective-C runtime and CoreFoundation. So when you type [4, 5, 6], you get an NSArray. And you can make calls to Cocoa like "/Users/andym/Desktop".pathComponents. Sweet.

Version 0.3 is a huge improvement: it provides Interface Builder support; it makes Ruby calls with the Obj-C message dispatcher (a huge speed boost); and it supports RubyGems. But most interestingly, it includes a new layer called HotCocoa.

HotCocoa is a layer of mappings on top of common Cocoa classes to make them simpler and to put them in line with idiomatic Ruby.

continued…

If you're looking for something specific then give the search form below a try:

RSS Wordpress Grady (theme) Return to the Top ↑