We’ve been trailing a new blogging engine called “Tumblr”:http://www.tumblr.com/. Technically, it is called a “tumblelog”:http://en.wikipedia.org/wiki/Tumblelog – an online scrapbook of sorts. Both Koz and I now have it up and running for our personal blogs.
Check out “Nigel’s Blog”:http://blog.wellies.org and “Koz’s Web”:http://tumble.koziarski.net/ to see the working product.
Perhaps you are an architect or a software developer working for a large company. You would like to try out using Ruby on Rails for that next project coming along at work. It would be a perfect fit, so you speak to your boss and he says *NO*.
In this paper, we will explore how to change that answer to *YES*.
h3. Risk
The main reason why your manager said “no” is because of risk. Managers are afraid of risks – in fact, it is part of their job description to mitigate any risks. Introducing a new programming language and a new application framework are two very big risks that most managers will avoid.
h3. Baby steps
To minimise the perceived risk, we need to take “baby steps”, or small increments along the pathway to introducing Ruby on Rails. If you can show the Ruby technologies being used successfully in some lower risk scenarios, then your manager may be willing to try it out for a larger project.
h3. Our experience
Some of our clients are beginning to trial Ruby for very simple tasks. Others are now using it for intranet style applications. Some have totally embraced the Rails framework, and are using it for all of their new development.
h3. Watir
“Watir”:http://wtr.rubyforge.org/ provides a Ruby API for controlling the Internet Explorer web browser. This may not sound particularly exciting, but if you combine this product with the unit testing abilities of Ruby – you have an excellent functional testing tool.
There is also a Firefox variant being developed called “FireWatir”:http://wiki.openqa.org/display/WTR/FireWatir+-+WATiR+for+FireFox
We have used Ruby and Watir for developing the functional test scripts for several clients – with excellent success.
h3. Scripting
Ruby is a scripting language. If you have a scripting task to perform, it may makes sense to use Ruby for achieve it. An advantage to scripting in Ruby (compared with shell scripts), is that they can be easily run on Windows too.
There is a new book from the Pragmatic Programmers called “Everyday Scripting with Ruby”:http://www.pragmaticprogrammer.com/titles/bmsft/index.html which may be worth a look.
h3. Scaffolding
As most Rails developers know, scaffolding is not intended to be used by end users. But, an opportunity you have is to use Rails scaffolds for data maintenance.
It is possible to devote a lot of effort in building data maintenance screens – for just one or two system administrators. What you can do instead, is to use the scaffolding approach to quickly build some basic, yet functional administration screens.
h3. Fixtures for test data
The fixtures facility that is built into Rails provides a powerful way to define and maintain test data. You can use the Rail based fixtures in combination with your Java or C# based application. All of your test data will be defined in a YAML file, and you use rake to deploy it.
You could also define your database schema with the Ruby migrations facility. And then push out your schema changes in an iterative manner.
h3. Intranet applications
Before you build a public web application based on Rails, you probably want to try it out internally first. This will allow you to become familiar with some of the non-coding features of Rails. For example, you will need to learn the appropriate way for your organisation to deploy the application, the database schema, batch tasks, load balancing, etc.
h3. Conclusion
Deploying any new technology can be a risky business. These risks can be minimised by taking small steps along the pathway towards the goal of a fun, productive web development.
h3. Further reading
Why not read some of our other “papers”:papers, or subscribe to our “Blog”:blog. Feel free to “contact us”:contacts for more information.
I have written a paper called “Introducing Ruby on Rails to your workplace”:introducing-ruby-on-rails-to-your-workplace. It covers a number of approaches to using both Ruby and the Rails Framework at your work. These suggestions apply to organisations of all sizes – from small startups through to large corporates.
So have a read. What other ways can we use Ruby on Rails to enhance our workplace productivity?
Firefox 2.0 is going to be released to the public in the next few weeks. One of the changes in this new version break some of the accessibility features of “KiwiSaver”:http://www.kiwisaver.govt.nz and many other NZ Government websites.
h3. Accessibility Requirements
The accessibility requirements of New Zealand Government websites are defined by the e-government initiative of the State Services Commission. Their “Web Guidelines document requires govt websites use the access keys feature”:http://www.e.govt.nz/standards/web-guidelines/web-guidelines-v-2-1/chapter6.html#Heading761 of web browsers to enhance usability for those people who have difficulty using a mouse.
The access keys are as follows:
bq. 0 list of access keys
1 home
2 site map
3 search
4 to 8 agency defined
9 contact us
[ beginning of main content
/ go to govt.nz
h3. Firefox 2.0 changes
Historically, access keys have been activated by the user holding down the ALT key (on Windows browsers) or the APPLE key (on Mac browsers), and then pressing the desired key. From the example above, I would press ALT-1 to visit the homepage.
Firefox 2.0 has changed the activation keys, and now requires users to press SHIFT and ALT together (on the Mac, it is SHIFT and APPLE).
But, when visiting the new KiwiSaver website, and other New Zealand Government websites – none of the mandated access keys seem to work. Yet, on some of my other web applications I have developed for Inland Revenue – they work fine.
h3. Bug or feature?
What the mandated access keys have in common is that none of them are alphabetic. They are all numerals or slashes, etc.
It appears that Firefox 2.0 is treating them as their SHIFTed equivalents. You can trial this with some simple HTML code:
On Firefox 1.5 and earlier, you’ll visit the Google homepage when pressing ALT-1. On Firefox 2.0pr3, you’ll visit the KiwiSaver website when pressing ALT-SHIFT-1.
I would suggest that this is a bug. I have created a “bug report”:https://bugzilla.mozilla.org/show_bug.cgi?id=357317 at the Mozilla website. If you are able, please “vote to have this bug fixed”:https://bugzilla.mozilla.org/votes.cgi?action=show_user&bug_id=357317#vote_357317.
Michael is speaking today at “RailsConf Europe”:http://europe.railsconf.org/ in London. His topic “Playing Nice with Others” covers application integration strategies. What technologies should you use? What ‘silver-bullets’ should you avoid? How can you structure your application to avoid common pitfalls.
We look forward to hearing how it goes, and hopefully seeing some videos of it online. We’ll post links to them when they become available.
We specialise in building professional web applications for businesses seeking:
* highly capable and experienced staff
* smart intuitive web designs
* cost effective development tools and agile processes
* shared risk development options
We can help solve your integration problems using our team’s broad and deep IT experience.
Thinking about moving to Ruby on Rails? We can offer:
* architectural and design advice
* team training and mentoring
* jump-start for your development team
Want to see where we’ve been surfing today? We’ve created a “Del.icio.us account”:http://del.icio.us/network/abletech for Able Technology. All three of us will contribute – that’s Nigel Ramsay, Michael Koziarski and Marcus Baguley.
Expect to see content such as:
* Ruby on Rails
* Java
* Web technologies
* Apple products and services
* Whatever seems cool!
Clicks on “links”:http://del.icio.us/network/abletech in the navigation bar to check it out.
There’s also an “RSS feed”:http://del.icio.us/rss/network/abletech if you’re really keen.
I signed up for the “iTalk”:http://www.italk.co.nz (internet telephone) service with “Slingshot”:http://www.slingshot.co.nz about a month ago. Here are my impressions after a month of using the service.
h3. Signup and Setup
This is probably the worst part of the “iTalk”:http://www.iTalk.co.nz experience. If you can get over this hurdle, then it’s pretty much plain sailing. The problems I experienced were:
* Unsupported hardware – I was using a Netgear VOIP box, and iTalk only support their own hardware. The forums are a good resource, but it’s pretty much a DIY approach. If you’re non-technical and you don’t have any technical friends, then I’d suggest only using supported hardware.
* Username and password issues – these are generated and then displayed on the setup webpages. They don’t email them to you automatically. Fortunately I have the foresight to have the webpage as a PDF and email it to my gmail account for permanent storage. otherwise you’ll need to call their support people of assistance.
* Customer support – you have to wait on hold forever, and the machine keeps telling you they value you call – yeah right. When you finally get through, they’re nice people and seem to know what they’re doing.
h3. Reliability
When we first started using the service, we had a few issues with calls not coming through. But those problems only lasted a few days and everything came right.
A month down the track, and the reliability seems great. Better than a mobile phone, but not quite as good as Telecom.
I’m using a answer machine at home, but I have heard their voicemail is unreliable.
h3. Call Quality
Fine. You get the odd echo every now and again, but it’s hardly noticeable. We used the service for two weeks before we told anyone we were using an Internet phone – no one had noticed.
Also, you get free caller ID.
h3. The Bill
What can I say – it’s great value. At $10 a month plus 5c a minute calling 24×7 it’s awesome. Mobile calls for 30c a minute – that’s less than half of what I was paying Telecom.
And… the format of the bill is incredible. They:
* itemise all calls, even local ones.
* give you the name of the person you called – WOW!
* date, time etc
* city called
and it’s all categorised into local, national, international and mobile sections. Great work Slingshot!
h3. The Outcome
I’m going to call up Telecom tomorrow to say bye bye. The cable will be snipped. I’ve waited a long time to do this. No longer will we be paying the $40 tax each month.
h3. My Advice
If you interested in this kind of thing, I’d suggest following this process:
# Sign up with iTalk but just get the softphone option
# Get that going first
# Try it out – if you’re happy with it, then buy a “VOIP adapter”:http://www.dse.co.nz/cgi-bin/dse.storefront/en/product/XH9440 for your regular phone
# Call Telecom and ask for their Call Diversion service
# Divert your Telecom number to your new iTalk phone number
# Start using your iTalk phone only. Unplug your Telecom phone
# Don’t tell anyone about this for two weeks or so, and see if anyone notices
# After the two week period, start telling people
# When you get your first bill from Slingshot, start telling all your friends about your new number
# Give it a week or so, and the give the Telecom number the chop