Permalink | Leave a comment  »

Permalink | Leave a comment  »

Although I knew that Steve Jobs would have to step down soon after he announced taking medical leave earlier this year, it is still sad to hear he has now decided to resign the post of Apple CEO.

Rarely can individuals be both as visionary and successful in achieving their vision as Steve Jobs has been.

Any flaws of his character, of which many people seem to know so much, only underline his humanity.

Steve, thank you for sharing the vision of what computing can be with us through the market.

You have inspired many more than you have angered (jealousy is a human flaw after all), and thanks to that sharing I am sure many more good things will follow from Apple and others.

Permalink | Leave a comment  »

In this 2011 Geek Day, I take price in copying and pasting the Geek Manifesto from Wikipedia. Happy Geek Pride Day to all my fellow geeks!

(Republished without permission from http://en.wikipedia.org/wiki/Geek_Pride_Day)

Rights:

1. The right to be even geekier.
2. The right to not leave your house.
3. The right to not like football or any other sport.
4. The right to associate with other nerds.
5. The right to have few friends (or none at all).
6. The right to have as many geeky friends as you want.
7. The right to be out of style.
8. The right to be overweight and near-sighted.
9. The right to show off your geekiness.
10. The right to take over the world.

Responsibilities:

1. Be a geek, no matter what.
2. Try to be nerdier than anyone else.
3. If there is a discussion about something geeky, you must give your opinion.
4. To save and protect all geeky material.
5. Do everything you can to show off geeky stuff as a "museum of geekiness."
6. Don't be a generalized geek. You must specialize in something.
7. Attend every nerdy movie on opening night and buy every geeky book before anyone else.
8. Wait in line on every opening night. If you can go in costume or at least with a related T-shirt, all the better.
9. Don’t waste your time on anything not related to geekdom.
10. Try to take over the world!

Permalink | Leave a comment  »

In a previous article, http://blog.futureshock-ed.com/2011/01/ios-ad-hock-app-distribution-for-beta...., I documented how I managed to produce a testing version iOS app that I needed to distribute to testers. To do this, I needed to create a ad-hock provisioning certificate on Apple's Developer's Provisioning Portal.

While the method I described worked back then, and I thought I had a decent undersrtanding of the certificate creation and application signing process, when I tried to repeat it last week, it all fell apart. 

I tried Xcode 3, Xcode 4, deleting and creating all certificates, editing the Xcode project configuration by text editor, and repeating everything hundeds of times over two days, the bloody thing didn't want to work. I kept getting errors like:

• Code Sign error: Provisioning profile  can't be found
• Code Sign error: Provisioning profile '2B29F6DB-B03A-4882-A405-40BB6A2377EC' can't be found
• XCode could not find a valid private-key/certificate pair for this profile in your keychain.
• profile doesn’t match Application Identifier xyz

and many others. 

I finally started suspecting that I was innocent of incompetence, and that there was something NOT FUNNY going on with Apple's signing process, especiall the part where in Xcode, you Build and Archive the app, then in the Organizer you Share the archived app by choosing the appropriate code-signing identity.

I decided to find out whether this process really worked. 

Reading the documentation (http://developer.apple.com/library/ios/documentation/Xcode/Conceptual/iphone_... discovered that there is a utility that inspects a built application and reports a few interesting statistics and settings, including the certificate used to sign the app.

This utility is called 'codesign'. I tried running it first against the .ipa file that the Organizer creates, but failed. The documentation only had examples with .app files, those produced by the Xcode build process. So I decided to just build the app in Xcode, then browsed to the build directory, and applied the tool to the new .app file. This is what I got:

$ codesign -dvv myApp.app

Executable=/Users/me/programming/iPhone/myApp/build/Beta-iphoneos/myApp.app/myApp

Identifier= myApp.

Format=bundle with Mach-O universal (armv6 armv7)

CodeDirectory v=20100 size=1900 flags=0x0(none) hashes=87+5 location=embedded

Signature size=4337

Authority=iPhone Distribution: Awesome Enterprises Pty Ltd

Authority=Apple Worldwide Developer Relations Certification Authority

Authority=Apple Root CA

Signed Time=26/03/2011 6:24:21 PM

Info.plist entries=24

Sealed Resources rules=3 files=71

Internal requirements count=1 size=144

That was interesting. The distribution certificate was correct, as specified in my testing profile. This file *should* work if I tried to install it on an iOS device with this certificate installed, as long as the device's UUID was valid for this certificate. With no time wasted, I just drag-droped the .app file onto iTunes; my testing iPod Touch with the correct certificate installed was already connected. Clicked Synced, waited for a few seconds, an there you go, app installed, no worries!

It seems that the Organizer was messing around with the certificates. I don't know exactly how, I might investigate further if time permits, but what was happening just did not make sense for a systemt that one would expect would be throroughly debbuged and working as expected. It seems like this isn't.

So lesson learned: only sign apps in Xcode, forget about archiving in Organizer. Note that the Share Archived Application in the Designer has the option 'Don't Resign". This might produce a properly working archive if in fact it doesn't touch the signing that Xcode did prior to archiving. But with what I have learned about the reliability of all this, I will be staying away from archiving via the Organizer.

Permalink | Leave a comment  »

Thanks to Cody Fauser for this list of HTTP responce codes and their Ruby on Rails symbol mappings. This table is sure to save me a lot of time when I need one of these.

Permalink | Leave a comment  »

In Ruby, I often need to format time and date strings to make them look decent. I use strftime, which aparently is used in other languages, like PHP.

In Ruby, you would do something like this:

puts (inspection.date + HOURS_FROM_UTC.hours).strftime('%e-%b-%Y, %H:%M')

The formatting parameters (starting with the percentage sign) are many and not to intuitive to remember. 

I found one post with a list of most of them here, but I also include them here for quick reference:

%a - abbreviated weekday name according to the current locale
%A - full weekday name according to the current locale
%b - abbreviated month name according to the current locale
%B - full month name according to the current locale
%c - preferred date and time representation for the current locale
%C - century number (the year divided by 100 and truncated to an integer,
   range 00 to 99)
%d - day of the month as a decimal number (range 01 to 31)
%D - same as %m/%d/%y
%e - day of the month as a decimal number, a single digit is preceded by
   a space (range ' 1' to '31')
%g - like %G, but without the century.
%G - The 4-digit year corresponding to the ISO week number (see %V).
   This has the same format and value as %Y, except that if the ISO week
   number to the previous or next year, that year is used instead.
%h - same as %b
%H - hour as a decimal number using a 24-hour clock (range 00 to 23)
%I - hour as a decimal number using a 12-hour clock (range 01 to 12)
%j - day of the year as a decimal number (range 001 to 366)
%m - month as a decimal number (range 01 to 12)
%M - minute as a decimal number
%n - newline character
%p - either `am' or `pm' according to the given time value, or the
   corresponding strings for the current locale
%r - time in a.m. and p.m. notation
%R - time in 24 hour notation
%S - second as a decimal number
%t - tab character
%T - current time, equal to %H:%M:%S
%u - weekday as a decimal number [1,7], with 1 representing Monday
%U - week number of the current year as a decimal number, starting with
   the first Sunday as the first day of the first week
%V - The ISO 8601:1988 week number of the current year as a decimal
   number, range 01 to 53, where week 1 is the first week that has at
   least 4 days in the current year, and with Monday as the first day
   of the week. (Use %G or %g for the year component that corresponds
    to the week number for the specified timestamp.)
%W - week number of the current year as a decimal number, starting with
   the first Monday as the first day of the first week
%w - day of the week as a decimal, Sunday being 0
%x - preferred date representation for the current locale
   without the time
%X - preferred time representation for the current locale
   without the date
%y - year as a decimal number without a century (range 00 to 99)
%Y - year as a decimal number including the century
%Z or %z - time zone or name or abbreviation
%% - a literal `%' character

Permalink | Leave a comment  »

In an app I'm building, I decided it was about time to start thinking about data model versioning as a way to protect user data from database schema changes. Without versioning, every time I updated the app's schema, the user's data would have to be wiped out. Not good.

Any way, I consulted various sources on how to do this, including my beloved More iPhone 3 Development and Apple's Introduction to Core Data Model Versioning and Data Migration Programming Guide.

I made the minor changes to my code in the persistentStoreCoordinator and managedObjectModel, and tested in the Simulator. Great, nothing was broken, the changes worked just as advertised.
I continued coding, and a few hours later decided it was time to test on the device.
Bummer, I got this error message:

2011-02-10 14:23:12.470 myApp[9241:307] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSURL initFileURLWithPath:]: nil string parameter' 
*** Call stack at first throw: 
( 
0 CoreFoundation 0x33ac0987 __exceptionPreprocess + 114 
1 libobjc.A.dylib 0x3347b49d objc_exception_throw + 24 
2 CoreFoundation 0x33ac07c9 +[NSException raise:format:arguments:] + 68 
3 CoreFoundation 0x33ac0803 +[NSException raise:format:] + 34 
4 Foundation 0x3362b54f -[NSURL(NSURL) initFileURLWithPath:] + 70 
5 Foundation 0x33650157 +[NSURL(NSURL) fileURLWithPath:] + 30 
6 myApp 0x00003537 -[myAppAppDelegate managedObjectModel] + 138 
7 myApp 0x000036fb -[myAppAppDelegate persistentStoreCoordinator] + 302

8 myApp 0x00003407 -[myApp AppDelegate managedObjectContext] + 62 

9 myApp 0x0000302f -[iNspectorAppDelegate application:didFinishLaunchingWithOptions:] + 78 
10 UIKit 0x3209ebc5 -[UIApplication _callInitializationDelegatesForURL:payload:suspended:] + 772 
11 UIKit 0x3209a259 -[UIApplication _runWithURL:payload:launchOrientation:statusBarStyle:statusBarHidden:] + 272 
12 UIKit 0x3206648b -[UIApplication handleEvent:withNewEvent:] + 1114 
13 UIKit 0x32065ec9 -[UIApplication sendEvent:] + 44 
14 UIKit 0x32065907 _UIApplicationHandleEvent + 5090 
15 GraphicsServices 0x33b0ef03 PurpleEventCallback + 666 
16 CoreFoundation 0x33a556ff __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 26 
17 CoreFoundation 0x33a556c3 __CFRunLoopDoSource1 + 166 
18 CoreFoundation 0x33a47f7d __CFRunLoopRun + 520 
19 CoreFoundation 0x33a47c87 CFRunLoopRunSpecific + 230 
20 CoreFoundation 0x33a47b8f CFRunLoopRunInMode + 58 
21 UIKit 0x32099309 -[UIApplication _run] + 380 
22 UIKit 0x32096e93 UIApplicationMain + 670 
23 myApp 0x00002fb3 main + 70 
24 myApp 0x00002f68 start + 40 
) 

Tried again in the simulator, it worked.
Looking at the error trace, something was happening in the managedObjectModel function, and the error message in the first line indicated that the NSURL string was nil. The offending block of code was this:

NSString *path = [[NSBundle mainBundle] pathForResource:@"Datamodel" ofType:@"momd"];
NSLog(@"path: %@", path);
NSURL *momURL = [NSURL fileURLWithPath:path];

I added the NSLog line to print out the contents of the `path` variable, and discovered that it was not nil when running in the simulator, but nil when running on the device.

I went to have a look at the application assets in

/Users/peter/Library/Application Support/iPhone Simulator/4.2/Applications/F2854B27-4750-4DC8-8CB6-A22B036F5DC9\myApp.app

by right-clicking and selecting "Show Package Contents", and noticed that the data model versioning directory was named `DataModel.momd`.
However in my code, the path variable was `Datamodel` (loading a resource of type `momd`), whereas the directory containing the model versions was `DataModel`.
Yeap, this was another case of the simulator and the device behaving differently, this time in how they handle file name cases.

Once I changed my code to
NSString *path = [[NSBundle mainBundle] pathForResource:@"DataModel" ofType:@"momd"];

and ran on the device, it worked.

Permalink | Leave a comment  »

I needed to distribute two copies of a new app I'm building to beta testers, and a process Ithough should only take 30 minutes or so, took me half a day.

Apple's iOS Provisional Portal has these instructions (https://developer.apple.com/ios/manage/distribution/distribution.action):

How to create an Ad-hock distribution

I will start from the end of the process so that you know what you should be aiming for. A bit of an anti-climax, I know, but I find it useful to know what my target is.

xCode 3.2.5 has got a very nice distribution feature, accessible via the Build menu.

Once the project is configured properly for this feature to work, Build and Archive will create an .ipa archive that can be opened by iTunes on Windows or Mac. The file can be found in the Organizer. The Organizer can even help you email it to your beta testers, save it to disk, or distribute to an enterprise (that sounds cool, but don't know exactly what it does). Before this feature was put in xCode, people had to do everything manually, and some even wrote their own scripts trying to automate the process.

For Build and Archive to work, you must build using on the device, not the simulator. If your selected target is the simulator, the Build and Archive option will be disabled. Yep, this cost me an hour.

Steps for getting your ad-hock distribution

1. You can have up to 100 ad hock deployments of your app. For each one, you need the UUID of the beta tester's iphone or ipod touch. This can be found by connecting the device to itunes and accessing its property page. See here for details. Then proceed to the iOS Provisioning Portal, click on "Devices", "Manage", and "Add devices". Fill the blanks with the information you have.

2. You will need a distribution provisioning profile. This can be obtained by going to the iOS Provisioning Portal, click on Provisioning, and then on the Distribution tab. Click on "Create new profile", then fill in the blanks ensuring that Distribution Method is set to "Ad Hock". Submit, refresh a couple of times until you see the Download link, then download the certificate and put is aside for now.

3. Start xCode and open your project. Click on the Resources folder, and with it selected, click on File, New File. Under Code Signing, select Entitlements, and click Next.

4. Name the file "Entitlements.plist", and click "Finish".

5. Find the Entitlements.plist file in Resources, and open it. Add a new row so that the file now has these contents (make sure "Can be debugged" is not checked":

6. Go to "Project", "Edit project settings" and scroll down to the code signing section. You need to edit the Code Signing Entitlements with the name of the file you created in step 5, and the Code Signing Identity rows with your valid developer certificate.

7. You are now ready to create the distribution file. Click on Build, Build and Archive. The file is created and the Organizer pops-up. Click on the file to select it, then click on Share. Select the correct distribution identity from the drop-down, and then Save to Disk (or E-mail if you prefer).

8. Attach the .ipa file you created in step 7, along with the distribution provisioning profile from step 2 in an email, USB drive, network drive, or any other distribution method you like, and sent it to your beta tester.

9. With their device connected to iTunes, your beta tester needs to drag-drop the provisioning profile on the iTunes library. Then, double-click on the .ipa file. Once the app is installed on iTunes, it's icon will be visible in the apps library. He can now sync the device to get the app installed.

This worked for me and have done a few deployments without problems. Let me know how it worked for you, or if you came across problems.

UPDATE: Checkout a related post if you are still having trouble with getting your ad-hock distribution to work: http://blog.futureshock-ed.com/xcode-ad-hock-provisioning-certificate-pains

Permalink | Leave a comment  »

After installing RVM, Ruby 1.9.2dev, and Rails 3.0.0.beta4, I followed the instructions here to update a bunch of files (assuming you are running MongoDB locally):

config/initializers/mongo.rb

MongoMapper.connection = Mongo::Connection.new('localhost', 27017)
MongoMapper.database = "#myapp-#{Rails.env}"

if defined?(PhusionPassenger)
PhusionPassenger.on_event(:starting_worker_process) do |forked|
MongoMapper.connection.connect_to_master if forked
end
end

Gemfile:

source 'http://rubygems.org'

gem 'rails', '3.0.0.beta4'

gem 'mongo_mapper'
gem 'rails3-generators'

config/application.rb
(only first 8 lines shown, not change to the rest of the file)

require File.expand_path('../boot', __FILE__)

#require "rails/all"

require "action_controller/railtie"
require "action_mailer/railtie"
require "active_resource/railtie"
require "rails/test_unit/railtie"

Then, I went on to create a model, and to do that I used kristianmandrup's rails3-generators gem:

sudo gem install rails3-generators
rails generate model Book --skip-migration --orm=mongomapper

class Book
include MongoMapper::Document

key :title, String
key :author, String

timestamps!

# Validations :::::::::::::::::::::::::::::::::::::::::::::::::::::
# validates_presence_of :attribute

# Assocations :::::::::::::::::::::::::::::::::::::::::::::::::::::
# belongs_to :model
# many :model
# one :model

# Callbacks :::::::::::::::::::::::::::::::::::::::::::::::::::::::
# before_create :your_model_method
# after_create :your_model_method
# before_update :your_model_method

end

rails generate controller Book

This creates an empty controller file. Edit book_controller.rb to look like this:

class BookController < ApplicationController
def index
@books = Book.all
end
end

Create a view for this controller and action in app/views/book/index.erb:

<% if notice %>
<p id="notice"><%= notice %></p>
<% end %>
<h1>Books</h1>
<% @books.each do |book| %>
<div class="entry">
<h3><%= book.title %></h3>
</div>
<% end %>

Inspector::Application.routes.draw do |map|
resources :books
end

rails server

book1 = Book.create(:title => "title 1", :author => "author 1")
=> true
book2 = Book.create(:title => "title 2", :author => "author 2")
=> true

Finally, make sure the rails server is running, and try to access http://localhost:3000/books. If all went well, the two entries we just made will be listed.

PS. Good resources on this subject:
http://www.mongodb.org/display/DOCS/MongoDB+Data+Modeling+and+Rails
http://blog.bitzesty.com/mongodb-with-mongomapper-and-ruby-on-rails

Permalink | Leave a comment  »

Permalink | Leave a comment  »

Permalink | Leave a comment  »

Permalink | Leave a comment  »

Permalink | Leave a comment  »

Permalink | Leave a comment  »

http://link.brightcove.com/services/player/bcpid56328629001?bclid=10175001001...

Permalink | Leave a comment  »

Permalink | Leave a comment  »

* Stopping NFS kernel daemon

...done.

* Unexporting directories for NFS kernel daemon...

...done.

* Exporting directories for NFS kernel daemon...

exportfs: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "192.168.110.0/24:/home/peter".

Assuming default behaviour ('no_subtree_check').

NOTE: this default has changed since nfs-utils version 1.0.x

...done.

* Starting NFS kernel daemon

...done.

At the Mac side

In Finder, click Go --> Connect to Server, and in the server address field type:

nfs://192.168.110.114/home/peter/

It should take less than a second to connect, and the NFS drive will appear in the list of shares in a Finder window.

Permalink | Leave a comment  »

The problem was caused by VMWare creating a new MAC address for the new (copied) VM, and a mismatch between this new MAC address and the address recorded in the Ubuntu /etc/udev/rules.d/70-persistent-net.rules file.

It took me a while to figure out how to fix it (well, it was quick after I discovered which file to edit): edit 70-persistent-net.rules so that the MAC address for eth0 matches that given by VMware:

VMware Fusion

70-persistent-net.rules

Permalink | Leave a comment  »

Start by downloading the latest Ubuntu server image. I use the 64 bit version.

Start up your virtual machine manager (I use VMWare Fusion), and create a new machine with 5-6GBytes of disk space. I am not too worried about partitioning since this will not be a production machine. I don't need too much space since development of pure Ruby apps is not too space consuming. I also like the ability to quickly copy the VM from one computer to another, and creating lots of backup snapshots for not too much extra space.

Once the new VM is ready, boot into it and log one. First update the OS before adding the development stack.

Update the apt-get sources:

sudo apt-get update

Then the OS:

sudo apt-get dist-upgrade.

Now get the development tools and libraries:

sudo apt-get install build-essential

You will also need:

* The Zlib development headers:

sudo apt-get install zlib1g
sudo apt-get install zlib1g-dev

* The OpenSSL development headers:

sudo apt-get install libssl-dev

* The GNU Readline development headers:

sudo apt-get install libreadline5-dev

Now you are ready for Ruby itself. Get the source and expand the package:

wget ftp://ftp.ruby-lang.org/pub/ruby/1.9/ruby-1.9.1-p376.tar.gz
tar -xvzf ruby-1.9.1-p376.tar.gz

Enter the Ruby source code directory and configure, make, make install:

cd ruby-1.9.1-p376
./configure --prefix=/opt/ruby1.9 --program-suffix=1.9
sudo make
sudo make install

Add symlinks to access the Ruby binaries. Symlinks also make it easy to manage multiple versions of Ruby running on the same machine:

sudo ln -sf /opt/ruby1.9/bin/ruby1.9 /usr/local/bin/ruby
sudo ln -sf /opt/ruby1.9/bin/erb1.9 /usr/local/bin/erb
sudo ln -sf /opt/ruby1.9/bin/irb1.9 /usr/local/bin/irb
sudo ln -sf /opt/ruby1.9/bin/rdoc1.9 /usr/local/bin/rdoc
sudo ln -sf /opt/ruby1.9/bin/ri1.9 /usr/local/bin/ri
sudo ln -sf /opt/ruby1.9/bin/testrb1.9 /usr/local/bin/testrb
sudo ln -sf /opt/ruby1.9/bin/gem1.9 /usr/local/bin/gem

Almost done, just update Ruby gems, and your Ruby stack is ready, albeit at bare minimum level of functionality:

sudo gem update --system

Additional resources:

You will most likely need support for Git, and sqlite3 (at least for prototyping).

For Git, install the essentials, then get the source, enter its directory, configure, make it, and install it:

sudo apt-get build-dep git-core git-doc
wget http://kernel.org/pub/software/scm/git/git-1.6.6.tar.gz
tar -xvzf git-1.6.6.tar.gz
cd git-1.6.6
./configure
make prefix=/usr/local all doc
sudo make install install-doc

For Sqlite3, you will need the binary and the development sources:

sudo apt-get install sqlite3
sudo apt-get install libsqlite3-0 libsqlite3-dev

And finally get the Ruby gem:

sudo gem install sqlite3-ruby

Happy Ruby coding!

Permalink | Leave a comment  »