Monthly Archives: June 2011

A UI Revolution is Coming. Are we Ready?

This topic has been brewing in my mind, and in this blog, an in my tweets for months now. And one final event made me certain it is going to happen. And that event was the introduction of Windows 8. Not that Windows 8 is really that big a deal. But it confirms for me a trend that’s going to change the way we interact with the desktop applications we use daily, including Eclipse. Yes, a UI Revolution is coming. And we need to make sure we’re ready, or Eclipse is going to look old very quickly.

What am I talking about? Well, let’s start at the beginning. There is no question that Apple started the revolution with the iPhone and iPod Touch. Yes, there’s an app for that. There’s an app for everything. Apps are small, easy to create with a simple UI that was¬†intuitive¬†even for “regular” people (and, no, computer people aren’t very regular). The rest of the world outside the walled garden got their fix thanks to Android and Windows Phone and a few others. Smartphones have revolutionized how we think of applications.

Of course, once we have smartphones figured out you want to see if the same ideas scale upwards. The next big hole to fill was tablets. Tablets have been around for a long time albeit with the old UI borrowed from the desktop. It didn’t work. But could the smartphone UI scale up to tablet sizes. Indeed. iPad is gigantically successful and Android and Playbook are following behind. We’ve finally figured out how to make tablets commercially successful by using UI that again was intuitive for everyone.

Now, as I’ve been wondering here and there, what about the desktop? Does it make sense to bring these same principles to machines with larger and multiple screens with keyboards and mice and fast CPUs and GPUs? Well, I think we hit a tipping point. And that point happened when someone got the bright idea to slap a keyboard and trackpad onto a tablet, i.e., the Asus Eee Pad Transformer. Watching the videos people have posted onto YouTube of the Transformer in action, I am convinced that a tablet UI would work just fine on a desktop platform.

And apparently, so is Microsoft, which brings us back to Windows 8. Early videos of it show off exactly that. It’s the Windows Phone 7 UI, scaled up for both tablets and the desktop. And I think it looks pretty sharp. And I don’t see any reason why Android couldn’t do the same. And with the work Nokia/Trolltech are doing with Qt version 5, I can see how we can do the same for Linux. We all love the usability of our mobile devices, I want to love my desktop just as much.

But there’s problem. Watch the Windows 8 demo when they bring up Excel. It’s revolting, but in the wrong direction. You finally see how bad the old time UI that we’ve had for decades and that has been replicated on every desktop OS we know really is. We really need to invest in upgrading the UI and potentially reinventing those applications if we want to keep them around.

And, yeah, that includes Eclipse. Unfortunately, the old technique of putting a common API over the native UI frameworks isn’t going to work. The new frameworks are just too different. And making them common looses the gains they bring individually. We got away with it before because they used to be so similar. Not any more.

So what are we going to do? There’s many ways, I suppose. The itemis guys gave a great presentation at EclipseCon on one of the strategies they used. They use a DSL that implements the logic and general layout and generate code for each of the UI frameworks they support. It was cool but I’m not sure how complex of an app you can build that way.

But I do think they are on to something. You need to program the UI in the language and technique that the framework supports. But the core logic of the application should be able to stay the same. You know, Model-View-Controller, and you only need to swap out the View part? And we should be set up for that, no? Isn’t that why we broke things up into ui and core plug-ins? Or do we have so much logic in the ui plug-ins that this won’t work?

So this is an area I’m going to try and prototype. And I’ll start with Qt5 with their QML Javascript-ish UI language and see whether I can hook up Eclipse services through some sort of QObject C++ to Java bridge and make them dance. I have a feeling it’s going to be a dismal failure. But you have to start somewhere. Doing nothing doesn’t leave me feeling very comfortable about Eclipse’s future after the revolution.

Build for All

OK, when a thought spreads out more than two tweets, it’s time to write a blog entry instead. Ed Merks tweeted from the Eclipse board meeting (I presume) about the board’s concern that if Kim Moir got hit by a bus, we’d all be screwed, or something to that affect. And it’s true. Kim is a most valuable person at release time for getting the Eclipse train out the door. Without her for the Eclipse Platform, or David for the p2 site aggregation, or Markus for the EPP builds, we’d be scrambling.

So while I don’t want to take anything away from the great work they do, I do think it’s time to move to a better system where anyone can easily jump into their shoes. Not only that, but I’d like it to be easy for anyone to be able to checkout all the Eclipse projects they need and build their own product from it. I often get questions on the recommended approach to do such a thing and I don’t have an easy answer for them.

But there are two technologies that we are currently deploying that can improve the situation immensely. And I am working on bringing both to the CDT. The first is git and the second is Maven with the help of the Tycho plugins. As an example, I’d like to checkout all the source that feeds into the Eclipse C/C++ IDE package and then from the root directory, type ‘mvn clean install’ and have the zip file come out at the end.

Better yet, I’d like to clone all the source, commit any bug in any of that source on a branch, and do a build to get a test package, or a package I can send to my downstream customers. That scenario happens all the time in open source and git is making it a lot easier to manage your local branch, while making it easier to push changes upstream. And Maven/Tycho can make it easier to send builds downstream.

But it only really works if all Eclipse projects buy in. Maven can be done in parallel with whatever build system they are using so that’s not a huge problem. Getting them all to move to git is a bigger challenge. But I see the momentum starting, especially with the Eclipse Platform project discussing moving. So I’m confident we can get there. We just need to show the value the community gets from the significant work that is required to make these changes. And then we can leverage that good work ourselves and build the EPPs at using the same technology.