I’m familiar with web programming, both client and server side, and I’d like to expand a bit my knowledge in order to be able to write some desktop programs.
My problem is that I’m not really familiar with the desktop way of managing widgets. As far as I understand, in a typical desktop programs, widgets have their own life, sending signals to each other and reacting to signals with callbacks. So every widget is an object with lots of methods. This adds a further complication with respect to what I know now, and I’m not sure I want to learn this at the moment.
On the web you tipically describe the elements on the page with a markup language, usually some version of HTML, and when an event is fired you modify the elements with Javascript. I’m trying to understand if there is a way to use the web paradigm in a desktop program. I’d like to be able to describe widgets via a markup language (these will be static) and alter them based on events. If I understand correctly, XUL based applications work this way.
The problem is that the documentation I can find about XUL seems a bit outdated. Is learning XUL a good idea? Can I expect to be still using it a few years from now? Or is it becoming already an old technology?
In case XUL is not a good idea, what are the alternatives? For the most simple applications, where the widgets static, or are only slightly modified, there are some easy tools, but what about a more complex program?
EDIT: I should mention I mainly use Ubuntu, so I need a linux or OS-independent tool.
You might want to check out Adobe’s AIR technology. It lets you describe the UI using a markup language called MXML (similar to HTML, stricter syntax) and define the functions using ActionScript, a scripting language similar to JavaScript. AIR apps are platform independent as they run on AIR platform that abstracts OS specific things for you. They might be relatively slower than native apps for the same reason – but this may not be an issue for small applications. It depends on what’s more important to you – running speed or development speed.
The main downside with AIR is that users need to install AIR platform on their machine to install and run AIR applications, just like you need to install Java before you can run any application written in Java. Most of the platforms come with Java out of the box nowadays, but AIR isn’t that ubiquitous yet.
And about XUL, someone please correct me if I’m wrong, but apparently it is the markup language for describing UI in Mozilla’s applications like Firefox, Thunderbird etc and used for developing extensions for their applications. I couldn’t get any references to XUL being used for real desktop applications.