The Irish Penguin Watching Open Source unfold across Ireland

9Oct/100

Will there be a red carpet for Nokia at The Appys?

Just heard about this new awards ceremony The Appys! It will hand out the accolades to what it judges to be best mobile applications out there for a range of devices. As a long time Maemo fan and now MeeGo fan I'll be interested to see many apps are submitted for Nokia and its Ovi store.

Alas, my own humble efforts developing Qt on Rails apps aren't quite ready for entry. If you want to send in your own or vote on an app then today's deadline day! I just hope there's not too much in the way of gushing winners doing emotional acceptance speeches when the curtains come down on this one!

24Jun/100

Developing a simple Match Schedule N900 App for the group stage of World Cup 2010 via Qt on Rails

Today we're going to take a quick look at how to create a N900 app by taking a simple existing Ruby on Rails application and turning it into a Maemo app using Qt on Rails. The main thrust of this blog post is to show how you would tweak the skeleton app generated by the Qt on Rails framework into something that might be useful in the real world. The Match Schedule app is very basic and only shows the upcoming fixtures for the day. But most iPhone apps are simple thin wrappers around a data layer anyway; and this is really only a proof of concept app, so I'd don't feel to guilty about my humble achievement.

When the World Cup kicked off, I really wanted to have a schedule app on my N900 and couldn't find one so hence the motivation. Bear in mind that in 2 days this app will be completely useless as the group stage will be over! Warning: it currently requires a level of technical ability to install this app on N900 as it has no installer. You should check out this related blog post on deploying your Qt on Rails apps on the n900 (Maemo) before tackling this one.

The application (source code) is available for download. Note: I haven't stripped out unnecessary skeleton code from the application, which would exist immediately after generating the Qt application off the Rails codebase. The unnecessary code is related to Create/Edit/Delete functionality which we won't need in our simple Match Schedule viewer. I left it in to show the minimum amount of work needed to tweak the generated app into a useful real world program. All in all (blog posts and stuff aside), it took about an hour to do. If I had to do it again I'd imagine it would take less than half that time.

All the following steps are done on your dev machine. At the end of the guide you'll see how to deploy to your N900.

First we create a Rails app.

rails WorldCup

cd WorldCup

./script/generate scaffold Fixture when:string group:string match:string

rake db:migrate

Then I fired up the web server ./script/server and manually entered the fixtures (stupido! I know!). The 'When' field has the date formatted as '24/6 - 15:00'.

Next up, we turn the Rails app into a Qt app using Qt on Rails. We are still in the WorldCup directory.

./script/plugin install git://github.com/theirishpenguin/qtonrails.git

./script/generate qtify Fixture

This generates the skeleton Qt app. Now let's bend it into shape, starting with the UI. From now on we'll be working in the qtonrails/ plugin directory.

cd vendor/plugins/qtonrails

designer-qt4 app/qdesigns/qmainwindow.ui
Once Qt Designer appears, remove the File menu, Commandlink navigation buttons and Action buttons (by more or less right-clicking on those widgets and deleting)

Then regenerate a Ruby code version of the ui files (every time you change the .ui file using Qt Designer you need to do this)
rbuic4 app/qdesigns/qmainwindow.ui -x -o app/ui_proxies/qmainwindow.ui.rb

./run # or it that doesn't work try: ruby run
Then I got errors :-) . Based on these errors, I changed the following..

From app/qpresenters/main_window_presenter.rb I deleted

connect(@ui.viewButton, SIGNAL('clicked()'), self, SLOT('view_clicked()'))

connect(@ui.newButton, SIGNAL('clicked()'), self, SLOT('new_clicked()'))

connect(@ui.editButton, SIGNAL('clicked()'), self, SLOT('edit_clicked()'))

connect(@ui.deleteButton, SIGNAL('clicked()'), self, SLOT('delete_clicked()'))

connect(@ui.fixturesNavLinkButton, SIGNAL('clicked()'), self, SLOT('fixtures_nav_clicked()'))

connect(@ui.actionQuit, SIGNAL('triggered()'), self, SLOT('close()'))

Now let's try again.
./run

Hey it worked! Cool! There's more stuff we could now delete but we won't as we're focusing on doing the bare minimum.

In order to allow a column to be correctly resized and to provide row select behaviour (as opposed to having individual clickable cells), I added the following line just before the end of the initialize() method in app/qpresenters/main_window_presenter.rb

@tableview.resizeColumnsToContents()
@tableview.setSelectionBehavior(Qt::AbstractItemView::SelectRows)

The resizing of columns to fit their contents will probably become the default in a future Qt on Rails release.

Due to silly bug in Qt on Rails that tries to pull an unnecessary KDE library into generated applications (Issue 2 on the GitHub Tracker), we need to remove the line require 'korundum4' from vendor/plugins/qtonrails/app/ui_proxies/qmainwindow.ui.rb and vendor/plugins/qtonrails/app/ui_proxies/fixture_qform.ui.rb

In order to display just today's fixtures, we can change the index action in app/qcontrollers/fixtures_controller.rb (again under the qtonrails/ plugin directory)

def index
accept_current_fixtures_from Fixture.all
end

... and add the private method

def accept_current_fixtures_from(fixtures)
fixtures.reject do |fixture|
dt = fixture.when.split(' - ')[0] # Get date from string
date_args = (dt.split('/') + ["2010"]).reverse.map &:to_i
Date.new(*date_args) < Date.today
end
end

Note: The application source code available has the accept_current_fixtures_from() call commented out. This is because once the World Cup group stage is over in a couple of days the list of fixtures would be empty. I have decided that the value of this app as a useful demo in future outweighs the needs of my users over the next two days :-) . In the source code you can simply add the call back in yourself if you wish.

Finally, we make the grid readonly. Because it was late when I did this, I skipped any fancy meta-programming and simply reopened the QtrTableModel to do so. Add this to config/environment.rb

class QtrTableModel
def flags(index)
return Qt::ItemIsSelectable | super(index)
end
end

Phew! Done! To deploy the app to your N900, read the instructions at deploying your Qt on Rails apps on the n900 (Maemo).

Well, hopefully you've gotten a flavour of how to use Qt on Rails in a simple real world N900 app. If you've any feedback then please get in touch! Until the next time, enjoy the World Cup and I hope your country does well!

21Jun/100

Deploying your Qt on Rails apps on the N900 (Maemo)

Qt on Rails is a framework to let you turn your Rails sites in desktop applications and harness the power of Ruby! It's not at production level yet but it's certainly possible to have a good play with it and a bit of a hack! If you're not familiar with Qt on Rails then a good place to start is this blog post covering the v0.1 release. Also, check out the github repo for more info on installing Qt on Rails on your desktop and building an application with it. Here we show you how to deploy Qt on Rails based apps on your N900. One of the goals of Qt on Rails is to provide an easy way for you to develop apps faster for Maemo and, down the road, hopefully MeeGo too!

Note: This blog post may help you figure out how to install any QtRuby application on the N900, not just Qt on Rails apps. Also, this QtRuby Maemo wiki article was particularly useful when I was stumbling along this path!

One thing you will need to install as part of this guide is Easy Debian. Easy Debian greatly expands what you can do with your Maemo device. It basically sticks a full-featured version of Debian on your device. This means 2 things - firstly, for the uber-geeks out there it let's you fire up a Linux desktop on the N900; though it's important to note that your normal Maemo desktop isn't affected by Easy Debian. Secondly, having a full-on Debian available let's you run Linux apps such as Open Office! Sweet! And what rocks is that you can even run these programs without invoking the Easy Debian Linux desktop - in a seamless manner. It's important to note that the user interface to these Easy Debian-based apps behave a differently to a typical native Maemo program; rather they work like a traditional desktop application with a mouse pointer on screen.

Install Steps
  • Note: For simplicity, this guide assumes you are installing an application which stores data using sqlite3. Also, the steps here have been tested against the N900 firmware update PR1.2. If you are using an older version of the firmware you may want to consider updating it.
  • Firstly, install Easy Debian with the N900's Application Manager
  • Install the Easy Debian image via the new Deb Img Install application added to your list of applications
    • Note: This is a 1 gig download, but comes with cool stuff like OpenOffice and intergrates pretty seamlessly with your desktop
    • Takes an hour or so to download and then extract itself
  • Open the Debian Chroot terminal (not the usual N900 terminal), which should now be in your list of applications
  • Install rubygems, qtruby and  sqlite3 with ruby bindings
    • sudo apt-get install rubygems
    • sudo apt-get install libqt4-ruby
    • apt-get install libsqlite3-ruby
  • Install the bits we need need from Rails (without installing documentation)
    • sudo gem install activerecord activesupport activeresource --no-ri --no-rdoc
  • Zip up your Qt on Rails application and copy to any directory on to the N900. Note that the Qt on Rails application consists of the entire Rails directory directory including the vendor/plugins/qtonrails directory intact and  a sqlite3 database already created under the db directory).

    If you don't have your own Qt on Rails application to hand then you can create the RadRadio app discussed in the "Make it so, Jim!" section of the v0.1 release blog post

    In the Qt on Rails v0.1 release there is a bug that accidentally introduces a dependency on a korundum library, which is not needed in this case. An issue is logged against this in the Qt on Rails Issue Tracker As a workaround, find and remove any occurrences of require 'korundum4' in files under the vendor/plugins/qtonrails/app directory

  • Once transferred, simply unzip it on your device. Note: If you saved the zip to the Documents folder on your N900, this can be found under /home/user/MyDocs/.documents when poking around the filesystem
  • Finally, via the good ol' Debian Chroot terminal, change directory to the vendor/plugins/qtonrails directory of your app and execute

    ruby1.8 run

  • Boom! You should see your Qt on Rails app in all it's glory!

Note there is a bug where you cannot input into a text field when running a Qt on Rails app on the N900 using above technique (seamless mode). As a workaround, open the Qt on Rails app inside of the Debian LXDE desktop (rather than in seamless mode). You can find Debian LXDE in the list of applications on your device. Inside Debian LXDE, open a terminal and run the application as above. Just a quick heads up, sticky keys don't work like you'd expect - you have to hold down the Shift and Fn keys to use them.