Text

Why Can’t I Switch into GIT?

GIT out-trumps SVN in almost every way. The decentralize repository is better, the branching is better, and the social aspects (through github) are incredible. However, I can’t make the transition because I am hooked on Versions and Kaleidoscope. Having a great GUI to show changed files, and side by side comparisons is more important than having an amazing command line tool. Until someone writes a great GIT client (and no, none exist right now) I probably won’t move my repositories. However, the ability to use SVN to commit to GIT Hub (here) might sway me.

Tags: svn git
Text

Recurring Billing

Most web app ideas fall under an advertisement model or a freemium model. In the later case, a great application to simplify recurring billing is Chargify. The software lets developers link to a payment form or integrate custom forms with the service through a RESTful API (or a gem).

Once integration is done, administrators can track and update subscribers through a gorgeous web interface.

Overall, the application is easy to use and offers many features over ActiveMerchant. The support team for the application is generally quick to respond and the pricing is reasonable. Looks like a big time saver.

Tags: ruby rails
Text

Must Have Services in Rails Web Design

Ruby on Rails is what it is because of all the great services that extend and augment it. Here is a quick overview of some services that make creating web apps downright cool.

Hosting

Heroku provides online “cloud” hosting for Ruby applications (Sinatra, Rails, etc.). It uses GIT to deploy and runs on Amazon EC2 servers. The service is free for small applications and reasonably priced for others. Deployment can be done in under a minute.

Databases

MongoHQ and Cloudant are “cloud” MongoDB and CouchDB data stores. According to some, these schema-less services are doing to databases what Rails did to web frameworks: revolutionizing. MongoHQ is free for 16 MB databases and Cloudant is free for 1 GB databases.

Files

Almost every application has some data that does not fit (well) into a database. Picture, video and audio files are all best placed on massive storage. For this, Amazon S3 offers good performance for amazingly low prices (around two cents per GB). Paperclip will ease the integration into a Rails app.

Encoding

Services like YouTube and Vimeo let users upload video files that can then be viewed in the web browser. Implementing this functionality in an application is easy with Panada. Pricing is expensive (starting at $100 a month), but a free developer sandbox lets you try out the service. 

Telephony

Need an application to be able to answer the phone? Want to notify your users of events by SMS? Setting up a PBX to do this is daunting. Using Twilio or Tropo will accelerate development time by giving a simple XML web service making and receiving calls or SMS. Both services offer free trial time for development.

Tags: ruby rails
Text

Thinking about Migrating?

Unlike the featured caribou, I hate migrating. More specifically, I had migrations in web development; especially in Rails.

  

Here is why:

  1. Migrations are used throughout the development process when they are only required after having deployed to production. Who cares if you loose data while developing?
  2. Migrations duplicate functionality that every good software developer uses: version control. SVN, GIT and Mercurial are all great at revision tracking and the duplicate functionality offered by migrations is unnecessary.
  3. Migrations make it difficult to identify what attributes a model has. Instead of defining everything within the model, developers need to refer to the schema.

Hating migrations leaves few solutions. My favourite is switching to a schema-less database like MongoDB (free hosting at MongoHQ) and then adding model integration to Rails with Mongoid or MongoMapper. This unfortunately is not be practical in many cases. For a less drastic solution try DataMapper.

Tags: ruby rails
Text

Non-Blocking Long Running Tasks on iPhone

iPhone and iPad applications containing long running tasks - such as HTTP requests or data processing - that block the main thread are annoying and often appear sluggish.

The following snippet fixes this issue:

Text

Cocoa Copy Paste Menu

I spent some time earlier today playing with the UIMenuController offered in the iPhone SDK and realized two thing: sometimes Apple’s examples suck and having an environment that often gives no feedback is terrible.

In this case, I implemented a copy of an example that was supposed to present a semi-modal cut / copy / paste menu. It didn’t. After spending nearly an hour trying to realize why nothing was happening, I found I had missed copying a line. Anyways, for the record, here is the concise example of how to present a UIMenuController:

Text

Cocoa Extensions

Cocoa extensions provide a great way to modify existing classes with additional functionality. Here is a good example of extensions in action:

Accessing extensions is simple: just import the header file. In the case above, easily readable dates are now at the finger tips!

Text

A Few Reasons Cocoa Isn’t That Hot

Over the past half-year I have been developing software for the iPhone (and recently iPad). Although I feel that Cocoa is excellent overall, a few rough edges prevent it from being a truly great experience:

The Language

Objective-C is the language of choice for most Cocoa developers (Cocoa can be accessed through bridges by Ruby, Python and a handful of other tools). It provides a thin layer on-top of the C program language, adding support for dynamic typing and messaging.

Objective-C’s very fast execution speeds do not compensate for the amount of code required to perform trivial tasks (especially compared with Ruby or Python). Issues such as memory management and duplicate feature sets (NSString and string, NSArray and [], etc.) can leave developers wanting something better.

The Controls

Interface builder is one of the best GUI designers available. That said, the iPhone and iPad controls are not nearly as verbose as the Mac desktop application controls. The lack of support for grids, checkboxes, colour pickers, and even good looking buttons does not make any sense. It is obvious that Apple had to exclude tools that will not work on the mobile platform, but their over-zelous axing of features ultimately ended up increasing the workload for developers.

Although Cocoa offers great customization of controls, developers must revert to code to get certain core features working. A great example is creating form elements within a table (something done in thousands of applications, including the ‘Settings’ app). Developers will need to setup delegates, protocols, and data-structures for something that should be drag-and-drop. For static forms, this is wasteful and time consuming.

The Ecosystem

Having recently spent some time developing in Ruby on Rails, I feel confident stating that the Cocoa ecosystem is terrible. Although a few great libraries and extensions exist (Three20, BWToolkit and Pinch Media), the non-existence of a package manager (such as RubyGems) means that third-party software is few and far between.

Installation of almost anything introduces dependency headaches and is completely non-strandard. A look through the 10-20 step guides required for any framework will make some cringe and others cry.

Conclusion

Given Apple’s reputation, it is a wonder better options are not available for Mac and iPhone development. The benefits of releasing a 25 year old language on brand new mobile devices or not upgrading existing SDK’s with new languages (Microsoft has gone through at least four) are very limited. Further support for projects like MacRuby are required, and hopefully existing open community frameworks can be better integrated with Cocoa in the future.

Text

Snow Leopard Rails Development Environment

A good Ruby on Rails development environment needs a few things: SSL, image processing, text editor, version control, etc. These notes explain how I setup rails development environments for Mac OS X 10.6 (Snow Leopard).

Step 1. Updating Gems

Before doing anything, it is important to ensure that you are running on the latest gems. To do so:

sudo gem update --system
sudo gem update

Step 2. Enable Web Sharing

Enabling web sharing will startup Apache. To do so ensure System Preferences > Sharing > Web Sharing is selected.

Step 3. Configuring Passenger

Passenger allows for ruby applications (and more specifically rails applications) to be deployed to a Apache and Nginx. Since we just enabled Apache, we can now install it:

sudo gem install passenger
sudo passenger-install-apache2-module

This command will print instructions for finishing up the configuring of passenger. Follow them. You should then be able to run the following command as a test:

sudo apachectl configtest

If everything is good, it should print out “Syntax OK”.

Step 4. Enabling SSL

Apache does not have SSL enabled by default. To enable it uncomment ‘#Include /private/etc/apache2/extra/httpd-ssl.conf’ in ‘/etc/apache2/httpd.conf’. Next we need to generate our certificate:

cd /etc/apache2/
sudo openssl genrsa -out server.key 1024
sudo openssl req -new -x509 -key server.key -out server.crt
sudo chmod 600 server.key server.crt

Again run:

sudo apachectl configtest

And look for “Syntax OK”.

Step 5. Install Port and Image Magick

ImageMagick is required for image processing in some ruby gems (paperclip). To setup, first download and install the latest version of MacPorts from here. Then:

sudo port install ImageMagick

This command takes a long time to run (thirty minutes to an hour). Once it is finished, Apache needs to know about the new binaries. This is done by creating a new file ‘/etc/apache2/other/port.conf’ with contents:

SetEnv PATH /opt/local/bin:/opt/local/sbin:$PATH

Again test apache.

Step 6. Setting Up Hosts

We made it! Now to create our first application. First, we want to map the host name for our application to our development computers IP. The sample ‘/etc/hosts’ file shows the settings required for setting up ‘http://dev.ksylvest.com/’ and ‘http://dev.kwik.ly’:

Next, browse to the directory ‘/etc/apache2/users’ and open the current user’s configuration file (for me ‘/etc/apache2/users/kevin.conf’). Attached is a sample configuration file for the above two applications stored in ‘/Users/kevin/Sites/ksylvest.com’ and ‘/Sites/kevin/Sites/kwik.ly’ respectively:

Again run:

sudo apachectl configtest

If you don’t already have a rails application setup, you can create one in a few steps:

cd ~/Sites
rails ksylvest.com
cd ksylvest.com
rake db:create
rake db:migrate

Then restart the web server:

sudo apachectl restart

Open a browser and test the web application by browsing to the URL specified in the hosts file. The server should also respond to SSL connections after you accept the certificate.

Step 7. Tools

Developing rails on a Mac is great because of the large number of tools available. My favourites include: TextMate, Versions, Git, CSSEdit and Adobe CS4. Some online services exist to help with version control (see GitHub and BeanStalk) so don’t setup local repositories if you can help it! Finally, ruby has many great gems and plugins for simplifying complex tasks in rails: