Tag Archives: Software

FileRunner 2.5


People usually fall into one of two categories on this issue. You have your hard-core command-line junkies who are quite happy typing obscure commands just to move a couple of files around. And then you have your GUI-evangelists who like pretty, drag-and-drop interfaces.

I tend to sit on the fence. I can see advantages to both, but I usually use the GUI in Windows — the command line is so poor — and in UNIX I use the command-line — I didn’t think that there were any decent GUI file managers.

And then I found FileRunner on a web site.

In use

On first use, FileRunner looks unmistakably like a Tcl/Tk program. The first thing it does is pop up a dialog telling you that it’s configuration directory is missing and would you mind if it created one. I clicked OK and found the main screen on my monitor.

First impressions: it’s trying to be like some of the original DOS file managers rather than like the Windows explorer. That is, most of the display is taken up with two identical lists (albeit independent) of files. Between the two panes are a line of buttons with straight-forward text labels such as ‘Move,’ ‘MkDir’ and ‘View.’ Many of them are not going to be much use if you’re not already a bit of a UNIX wizard — it took me a second to figure out what ‘S-Link’ meant.

The top of the screen has the menu, a number of ‘status’ lines (current directory, etc.) and a number of buttons to help you navigate around your file-system. FileRunner has a number of useful features in this last category The nicest is a ‘Hotlist,’ similar to your bookmarks in Netscape. I now have quite a list helping me jump around all over the place particularly quickly.

Another feature is FileRunners alternative to the ‘cd’ command. Clicking a picture of a hierarchy you get a list of directories, both up and down, and you can traverse the structure without actually stopping and looking in the directories. Handy when you know where you want to go but don’t have it on your hotlist. Sure, you can double click into lower directories and click the ‘up’ button, but this only moves you one level. This is incredibly convenient.

Once you found the file you want, FileRunner is good, too. Double-click a file and it will start a configurable program for you. Select an image file and XV starts up. Click a GZip archive and press the ‘UnPack’ button and it uncompresses. Click the ‘ChMod’ button and a dialog pops up allowing you to change its attributes.

But how do you copy a file?

FileRunner runs under X Windows and has a commendably GUI look about it. Unfortunately it doesn’t take full advantage of this. To copy a file between to directories, it would make sense to display the two directories on-screen and drag-and-drop the file to move it. Or perhaps that’s just me? It almost works. It’s just the drag-and-drop that doesn’t. You have to click the ‘Move’ button instead. I’d expect that to work as well, but not instead.

And how about deleting files? If a program is supposed to be easy to use I don’t think that it should punish my mistakes. But FileRunner does have a slight tendency to do just that. I can delete a file and it won’t warn me. (However, it does ask if I’m about to stupidly delete an entire directory tree.)


Over the years I’ve used a large number of applications written in TCL/TK and I have almost always been disappointed. Usually, the GUI looks good but once you get past the initial good impression the rot sets in. Bugs. Inconsistencies. And the distinct impression that it’s nothing more than a front-end for a command-line program.

I’m happy to report that FileRunner is not one of these applications. Instead, it’s fast and feature-rich — everything a file manager should be! However, it’s not going to help people who don’t already know UNIX. It’s a very useful program, but for the novice the search for a decent file manager continues.

Cooledit 3.5.3


Text editors are very personal things. I found this out when I wrote a very positive review of NEdit. I received a number of comments, nearly all by email. No-one agreed with me, which doesn’t by itself bother me. But no-one disagreed with me as such either. All the messages were from Emacs users who thought that it was the only real editor and that I was misguided thinking otherwise.

This time I think I’m unlikely to incur the wrath of Emacs users. Cooledit is just not going to appeal to the same people. If Emacs is equivalent to O’Reilly books, Cooledit is a Dummies Guide.

Look and feel

This is going to become the theme of the review: text editors are very personal things. When I say that I’m not keen on either the look or feel of Cooledit, I must also point out that there is nothing wrong with it either.

There are good bits. I like the default colour scheme. White on blue is very easy on the eyes. And the default, fixed-space typeface is very readable, too — I’m not sure what it is, though. The tool-bar down the left-hand side of the text window is useful and it would be immediately obvious what the buttons did even if it didn’t have text on the icons and ‘tool-tips.’

For a text editor with an emphasis on ease-of-use, Cooledit is actually quite powerful. In addition to the normal cut and paste, search and replace and file management facilities, Cooledit also has built in scripting and dialog-based configuration of keyboard shortcuts and the environment.

It does, however, look a little amateurish. While the menus do have Office 97-style highlighting when the mouse point moves over them, it’s difficult to take them seriously when they drop down. They look so big and clunky that you can immediately tell that they’ve been designed by a programmer. They’re not easy to get rid of if you pull down a menu by mistake, either.

And let’s not forget Cooledit’s most unique feature: it’s multiple document interface. Inside the main Cooledit window, you can have as many documents as you like. Behind all the windows is a picture of an igloo; it’s not entirely clear why it’s there. Documents can be moved around by dragging their border, and can be resized by dragging the bottom-right corner. These inner-windows don’t have title bars, which after years of finding a documents name by looking in the title-bar is a little confusing.

The interface does not take full advantage of its multiple windows, either. The load button and the open menu item actually operate on the currently open window rather than for Cooledit as a whole. This means that to open another file you need to open a new window (from the Window menu) and then load a file into it. This kind of operation would be acceptable for a program with only a single buffer — such as vi — but for a modern, GUI editor it’s just odd.


This has been a rather short and very negative review. As I have said, there is nothing strictly speaking wrong with Cooledit, it just feels wrong. It has all the right things in the right place; functionally it’s at least as good as NEdit. But it’s idiosyncratic user interface and ‘jokey’ appearance have a tendency to distract you from your work!

If you like to be different and you liked Borland’s cartoon ticks and crosses in its Windows applications, then you might go for Cooledit. If not stay well clear.

Free Software HOWTO

v1.2, 17 January 2001

With the current Linux trend towards multi-million dollar IPO’s and “Open Source” software, much of the emphasis of “free” software has been lost leaving people new to the fold confused and not completely understanding all the implications. This HOWTO will, hopefully, reduce some of that confusion.


What’s in here?

This document talks in non-technical terms about free software, what it means and why you should care about more than just the cost of your software.

Who is this HOWTO for?

People that have been hacking for years will already be fully au fait with the content of this document. Or at least you should be!

The Free Software HOWTO is aimed at people new to Linux, Open Source or free software.

New versions of this document

The official home of this HOWTO is here. You will always find the most up to date version here.


You get what you pay for. I offer no warranty of any kind, implied or otherwise. I’ll help you where I can but legally you’re on your own.

Credits and Thanks

I welcome any constructive feedback on this HOWTO and any general software licencing issues, although my opinions are just that: a subjective view. You should understand what each licence means before committing to one for your own software or documentation..


This document is copyright 2000, 2001 Stephen Darlington. You may use, disseminate and reproduce it freely, provided you:

  • Do not omit or alter this copyright notice.
  • Do not omit or alter the version number and date.
  • Do not omit or alter the document’s pointer to the current WWW version.
  • Clearly mark any condensed, altered or versions as such.

These restrictions are intended to protect potential readers from stale or mangled versions. If you think you have a good case for an exception, ask me.

(This copyright notice has been lifted from Eric Raymond’s Distribution HOWTO.)



Until now, you’ve probably never given much thought to software licences. No-one can blame you. They’re usually pages and pages of legalese telling you what you can and can’t do with the CD you just bought. If you actually sat down and read it all, you would probably never agree to it!

Licences, however, are at the heart of what free or open-source software is all about. Let’s take a look at a number of very broad categories of licence.

Commercial software

The first type is the commercial licence, like the one that Microsoft or Lotus might insist you agree with before using their software. The basic premise is that you don’t own the software, you have an agreement with the author that allows you to use it within certain guidelines. As the copyright owner, they can impose whatever restrictions they want. Common conditions include limits on the number of concurrent users, number of copies, and what you can use it for (for example, “non-commercial use” or a ban on reverse engineering).

The emphasis is what you can’t do, and all the power is in their court!

One thing to note, and this will become more relevant later on, is that none of this relates to the cost of the software (or, more properly, the licence). You can get commercial software, such as Microsoft Internet Explorer, for no cost and still be forced to abide by the publishers conditions.


The next kind of software, shareware, is sometimes called free, although as we shall see, that’s not correct.

Shareware was started in the early eighties by Jim Button when a few of his friends started passing round some software he’d written and he started getting phone calls asking for support. Eventually he added a request for $10 to the startup screen and shareware was born.

In short, shareware authors allow you to try out their software for free but request payment for continued use. Many of the same restrictions as for commercial software remain, including the limitations on reverse engineering, concurrent use of the full version, etc, stand. Additionally, the “free” downloads are often broken in some way, perhaps limited functionality or splash screens.

Interestingly, Linus Torvalds describes shareware as combining “the worst of commercial software (no source) with the worst of free software (no finishing touches).”

Public Domain software

All the licences we’ve seen until now have been designed to reduce people’s ability to do what they want with the software.

At the opposite extreme is public domain software. This is software that has no copyright and, therefore, no restrictions on its use. You can copy it onto as many machines as you like, reverse engineer it, make modifications and distribute it as you feel fit.

This is the first kind of software that we’re come across that can rightly be called “free.”

Normally, whenever you write something you automatically own the copyright, even if you don’t add an explicit copyright message. For public domain software, the author throws away these rights allowing everybody to do what they like with the software.

Unfortunately, “anything” also includes selling it. Imagine spending a huge amount of time producing your masterpiece, giving it away and then finding that someone else was able to sell it and make their fortune with all your hard work! Worse, people don’t even have to give you credit for your work; they can legally take it, replace their name with yours and distribute it.

This might be why there isn’t a huge amount on public domain software.

At this point it might be worth looking back at free commercial software. Both public domain software and a free piece of commercial software cost the same, but the freedom you’re given to use it varies. A common phrase you hear with free software is “think free speech not free beer.” The difference between public domain and commercial software show the opposite extremes.

Free software

By now it should be clear that there are many different kinds of free software and not all are equal. The version of free that this section relates to is the one promoted by Richard Stallman of the Free Software Foundation.

But first, a little history.

The Free Software Foundation was formed in 1984 when a printer manufacturer refused to give Richard Stallman the source code (the computer instructions required to make a program). It had been leading up to this for some time — the increasing number of non-disclosure agreements, new software that banned sharing of information, etc. — and the printer manufacturer was just the straw that broke the camels back.

Stallman decided that he could not, in clear conscience, sign a non-disclosure agreement or work with a company that restricted his ability to share information. While most people would have given up at this point and gone to work, for obscene amounts of money, for a big company writing proprietary software, Stallman stuck by his principles and decided to make his own operating system, free of the constraints of commercial systems.

The process leading up to this is documented in more detail in Steven Levy’s excellent ‘Hackers.’ You’ll note that Levy calls Stallman ‘the last real hacker.’ Happily he was wrong, otherwise you wouldn’t be reading this!

As we can tell from the background, “free,” in this context, relates not to the initial cost but to freedom. Stallman was unwilling to surrender the right to make modifications or improvements to any software he used — and to do this you need the source code.

This may sound just like public domain software up to this point. The difference is that there are clauses in the licence that attempt to keep the software free no matter what changes are made. The most famous free software, Linux, uses the most famous free software licence, the GNU General Public Licence. It is sometimes also called Copyleft, as it very cleverly uses the current copyright laws to do the exact opposite of its original mandate.

The way it does this is by insisting that the code and anything derived from it is also released with the GPL licence. In some senses it is ‘viral’ in nature and it is this that is central to many people’s objections.

Also, it’s worth noting that the word ‘derived’ is a little too vague. Does a library linked to a GPL’d program need to be GPL’d also? Does a program running on a free operating system need to be GPL’d?

There’s no clear, obvious answer for either of these with the current version of the GPL. The new version (3) is intended to fix some of these shortcomings, but it’s viral nature will remain.

Open Source software

Open Source software is, in many ways, exactly the same as free software, despite what Richard Stallman says!

It was started in 1997 by Eric Raymond and Bruce Perens as a response to the increasing confusion over the use of the word “free” in relation to software. (Confusion that has continued, or I wouldn’t be writing this document!)

In essence, Open Source is a marketing or PR exercise to make free software more acceptable, more understood by the general public and the big corporates that, until that point, were comforted by the money they had to pay to get commercial software.

Like “free” software, the “Open Source” trade-mark does not mandate a single licence. (Freedom of choice is important, even when it comes to giving away software!) Technically any licence that meets all the requirements in the Open Source Definition can be termed Open Source. These, in summary, are no restrictions on the use of the software, access to the source code and the freedom to make modifications and distribute them.

The two most famous are the Berkeley System Distribution (BSD) Licence, which allows distribution without the source code, and the GNU General Public Licence, although there are many more.

The Sun Community Source Licence, for example, is not compliant because Sun Microsystems demand a fee for any commercial distribution and insists that derivations are still compatible in some arbitrary ways. (This is not intended to single out the SCSL as being particularly bad. However, the fact that it purports to be “open” when it isn’t is a disturbing trend.)

The implications


Free software has already had a significant effect on the computer industry. Free software is behind most of the critical parts of the Internet, it was used (unsuccessfully) as part of the defense in the Microsoft anti-trust trial and the spate of recent IPO’s has shown that there’s money too.

Unless you bought some shares, this all appears to be affecting other people. There is an impact, however.

I just use software, how does this all affect me?

It’s tempting to think that, if you’re not a ‘techie’ or a hacker, the difference between free commercial, public domain and Open Source software is minimal. But that’s not true, even as a user the difference affects you because the development of the software is affected.

I’ll outline a plausible scenario as an example.

Company X designs and releases a fantastic piece of software. It’s commercial software, but the publisher seems receptive to new ideas, indeed versions 1.1 and 2.0 are exactly what you were looking for and the upgrade costs were reasonable.

At this point any number of things can happen. Perhaps you find a bug in it, one critical to your business. But the publisher offers no warranty for the software and say they are not sure whether they will fix it. (Note that just because you paid for the software, you do not necessarily get better service or a guarantee of any kind. According to the licence, you can’t sue Company X if the software is not fit for the purpose it was sold for.)

Or maybe they go out of business. Or perhaps they start competing with your company and won’t sell you the next version. Or perhaps the features you want are not in the new version. There are a huge number of ‘if’s and ‘maybe’s, all outside your control.

Basically, if you use commercial, close-source software you are at the whim of the publisher. If they do something you don’t like, tough.

However, if you’d used Open Source software you’d have access to the source code and could fix or upgrade the program as you saw fit. And if you couldn’t do it, there are many programmers willing to support the new versions or you could hire someone to do it for you. In summary, you have much more control over future development of the product.

You’ll note that none of the advantages here are strictly related to cost. I think that’s something that people tend to focus on too much, possible due to the “free software” title. However, there are still advantages.

But first we need to get away from the initial cost of the software as that’s normally a small percentage of the total cost. Instead, let’s think in terms of support costs. Once you’ve installed the software, what costs are there? An obvious cost is that of upgrades. Less obvious is lost productivity due to software failure and support charges from the manufacturer.

In the case of free software, there are no upgrade costs (other than the time and inconvenience of doing it, which also applies to commercial software). Free software is usually regarded as more reliable then commercial software — see Fuzz Revisited for more information. And the support charges are optional: you can either deal with it in-house or hire any one of a number of support organisations.

I’m a developer. How does this affect me?

As a developer, you’ll already know the benefits of being able to access the source code for a program. You can fix it, see how it works and integrate bits of it into your new program. (Using parts of another program, however, isn’t quite that simple and is dependent on the licence of the original software.)

A common problem developers see is the loss of their livelihood. If everyone gives away their software, how can anyone make money? It’s a fair question and there’s no single, correct answer.

Perhaps the most common answer is that most software is developed in-house and is not distributed. None of this development will be affected, so if you have that kind of job you can rely on your salary for a while yet!

If you work for a consultancy, almost all the revenue comes not from selling software but from “professional services,” i.e., they charge for developing the software rather than the licence to use it. Again your job is safe.

Then there’s shrink-wrapped software. The Free Software Foundation would say that it should be free. So if you listen to them and you work for Microsoft your job is in danger unless they diversify into services.

The Open Source people would say that there’s nothing wrong with shrink-wrapped software, but point out that there are advantages in releasing the source.

As you can probably see, the risk to your jobs is small and there are many benefits. At least that’s the way I see it and I work writing software!

Where can I read more?

The most obvious place to read more is at the GNU website, after all they started it all.

But there are alternatives. Other important web-sites are as follows:

  • Open Source. This is the ‘official’ Open Source page. There’s lots of interesting stuff here, including a more detailed discussion on the effect of free software on different people Microsoft’s Halloween documents, their unofficial response to the Linux threat.
  • Eric Raymond’s web-site. Eric has written much about Open Source software, with much more depth and style than I can muster!
  • Slashdot. There aren’t more ‘HOWTO’s here, but Slashdot is a community of people interested in Open Source software. The discussions sometimes get childish, but you can learn a lot!

There are also a few books published (at least partially) on the subject:

  • OpenSources. Voices from the Open Source Revolution.. This book talks about all aspects of the Open Source community, including licencing. The main reference is Bruce Perens essay.
  • The Cathedral and the Bazaar. Again, this book is about general Open Source issues, but it includes a discussion on some of the non-obvious implications of the licences, particularly the reason why just because you can, you don’t frequently get many versions of a piece of software.
  • Hackers Steven Levy talks about the early days of the hacker community, including a good piece on Richard Stallman.