Introduction

If there are any regular readers out there, you may recall that one of the first reviews that I did was of tkCVS. The more astute of you will have noticed that recently it has vanished. Somewhat ironically, I managed to delete it while using my ‘mirror’ program and didn’t have a copy held safely in a backup or version control.

If this has taught me anything, it’s that CVS, although very powerful, is not very easy to use. If it was, to use a cliche, as easy as falling off a log then I would have had no hesitation in using it. However, it’s not and I didn’t.

What is it?

First, what’s CVS? It’s an advanced client-server version control system. Unlike many other systems, CVS works with entire projects or directories rather than just individual files. It also allows many users to edit the same files and merge the changes back together later.

However, with twenty-four commands, each with a large number of options, CVS isn’t exactly what you’d call easy to use. (Since most people don’t bother with configuration management at all, this extra hurdle can’t help.)

tkCVS is a much needed TCL/TK-based front end.

In use

First impressions are good. tkCVS looks good. A menu is at the top of the screen, a tool bar is at the bottom and in the middle is a list of the files in the current directory. On the left are the filenames, on the right are their status: ‘ok’ if the file is up to date, ‘????’ if the file is not controlled and ‘{Locally Modified}’ if your version is newer than that in CVS. (I assume that there’s also a ‘modified by someone else’ descriptor, but since I used this on my own single-user machine, I didn’t test this functionality.)

All very straight-forward.

Marginally less straight-forward, now I come to look at them, are the buttons on the toolbar. Sure, they look decorative, but you can only find out what many of them do by waiting for the tool-tip to appear. (Having said that, I’m not entirely sure what a suitable icon for ‘re-read the current directory’ should be. They’ve used a pair of glasses.)

tkDiff

Bundled in the same archive as tkCVS is a graphical ‘diff’ program called tkDiff that’s worth, if not a review of its own, at least a mention.

It does just what it says. Given two files, it finds the difference between them and highlights the differences in various colours. You can flip between the differences using Next and Previous buttons, which is useful if you’re used to the standard GNU diff.

Best of all, it’s integrated with tkCVS allowing graphical diffs between different versions of the same file. However, although it’s easy to get a diff between your copy and the latest copy in CVS, it’s not entirely clear how to get a diff between versions in CVS or your copy and an older version.

Conclusion

Like many TCL/TK applications, it looks good but falls down on its implementation. The UI, although infinitely easier to use than the CVS command-line, is not quite as intuitive as it could be, and there are a number of glitches and bugs.

Fortunately, these glitches are just that. They are annoying but don’t get in the way of what is, fundamentally, a sound program.

Introduction

On the subject of emulators, there are two main factions. The first says that they are a good way of using all the software that you had for your previous computer when you upgrade. The second say that an emulator is a sure sign that a platform has no software. Why, they say, would you have an emulator if you could get as good or better software for your new machine? (They seem to forget that there are loads of emulators for DOS and Windows.)

I was first introduced to a useful emulator when I still had my old 386. A 386 has roughly enough power to run Sinclair Spectrum software at full speed. This was great: I could bring Bomb Jack, Manic Miner and Nebulous with me! And I could save levels and I could load complete games in a split second rather than ten minutes. The emulator was better than the real thing!

But my Amiga software just sat in the box. I had no way to bring that with me. Until now. PC’s are just about getting to the point that they are able to emulate and Amiga at full speed (and if they’re not then I can run them on my HP K box at work!).

Installation

The long and the short of it is that I’m lazy. If I can download an RPM archive of a program, I will. It’s not that Ican’t build programs — most work days I’m up to my arm-pits in C and Makfiles — it’s just that I want to use a program straight away. Okay, that makes me impatient too.

I’ve not been able to find an RPM of UAE, so I downloaded the latest stable version I tried to build it. Normally these GNU ‘configure’ scripts are straightforward: type configure; type make; and everything is ready. Configure usually goes away and finds the various bits and pieces without any trouble. The UAE configure script, however, couldn’t find my GTK library (I have the correct version according to the documentation) and it couldn’t see that I had the SVGA library, and the DGA support, which it did find and claimed to be using when I started UAE up, didn’t give full screen support.

So to summarize, I couldn’t get a nice user-interface and I couldn’t get full screen support in console or X. I wasn’t impressed.

Does it work?

It shows how long ago it is that I used a real Amiga. Like all the various kinds of memory that a PC can have (EMS, XMS, conventional, high), the Amiga has a number of different types too. I used to be able to remember all of them, what they are, what they do and why they’re there — on both the PC and Amiga — but I can’t now!

That’s to say, some of the programs that I couldn’t get working might, in fact, work fine if you can get the right combination of memory and video settings. This isn’t a criticism of UAE as such, more of the Amiga. It might be possible for the UAE team to add hints, though. (I never programmed my Amiga much, so I don’t know whether that would be possible.)

But I did have a number of successes. Workbench 1.3 seems to work fully (I’d forgotten how bad it looked), as does AmigaBasic and Deluxe Paint. With the windowed version of UAE, it is normal to have the Amiga mouse-pointer being completely independent of the X pointer. I find this annoying, but you can switch it off.

Perhaps more impressively I managed to get some games working. Arkanoid 2 works flawlessly; International Karate+ seems to work okay, albeit from the keyboard; Populous ran; as did Pacmania. However, all ran somewhat slowly. Arkanoid was fine unless the sounds was switched on. This slowed down the game, and the sound kept breaking up. Probably the worst was Pacmania, which was far too slow. The documentation does warn that some of the scrolling effects are the most processor intensive, and this is obviously the problem here.

As I mentioned before, there were a number of games that I couldn’t get working at all. Chase HQ gave me nothing more than a black screen. Rampage crashed. Paperboy didn’t work. Simulacra didn’t start. Maybe these will work if you twiddle with the memory settings?

In use

While it’s true that the performance and sounds problem can be overcome by throwing extra hardware at it, I think it’s fair to mention that most games are unplayable on a mid-range Pentium (120). Many application are probably okay, maybe even faster than the real thing, but I can’t see why anyone would want to run Amiga productivity software on a PC. Microsoft Word or LyX would be far better than anything on an Amiga.

UAE is supposed to come with a GTK-based front-end. I never managed to get this working, so all I was left with was the command line. This left no way to switch disks — they are emulated by files on your hard-disk — after the emulator had started, and no way to edit display or sound settings without resorting to obscure command-line directives.

Overall

I get the feeling that the UAE team may have bitten off more than they can chew. The Amiga was always considered a powerful machine, and trying to squeeze it into a ‘well behaved’ operating system like Unix was always going to be difficult. (One of the best Amiga emulators, Fellow, runs under DOS which is a far better option. There’s no chance of you being preempted by another process or user and you have full control over the screen.)

Maybe I’d have been more impressed if I’d managed to get the user-interface and full-screen mode working. And maybe I’d have been more impressed if I could install Linux on my PII at work. But I wasn’t and I haven’t, so, for now, I’m going to leave UAE well alone.

Introduction

I remember when I was at school I sometimes got bad grades when writing essays. This, the teachers claimed, was because I’d used an unconventional structure. Rather than start with an introduction, continue with the discussion and finish with my conclusion I’d often start with a rather long introduction, which included my view, and then argued my case in the rest of the text. I guess it weakened my argument a little to do it like that, but people did remember it!

I’ve still not learned my lesson. One of the first things I do with the review — not quite an essay but along the same lines — is say that I think that WindowMaker is the best window manager that I’ve used. In fact I like it so much I’m seriously considering changing from AfterStep, the window manager that I’ve used practically since I had a PC that could support X.

What’s so good?

Superficially WindowMaker is not that different to AfterStep. That could be part of the reason I liked it so much. (And after my disappointing experience with the new version of AfterStep last week I was most definitely open to suggestion.) Just like AfterStep and the NeXT, WindowMaker has a dock, or a wharf or whatever you want to call it, down the right hand side of the screen. This time there is also a paper-clip icon in the top left of the screen. This is WindowMaker’s method of moving between its virtual desktops. It’s a lot less fiddly than AfterStep’s mini-map but only slightly less intuitive.

Windows are handled in, more or less, the same way as AfterStep, they even look similar. The title bar is nicely gradiated, the top left has the minimise button, the top right has the close gadget. At the bottom of the window is the resize bar. A nice touch is the ‘technical drawing’ lines that are used to show where and how big the new window will be. It’s good to know that an xterm is eighty characters wide.

So far we’ve found that WindowMaker and AfterStep are pretty much the same. It’s when you try and configure things that the differences appear. To add an icon to the AfterStep dock you must open a text configuration file and try and interpret the syntax. Not hugely difficult, but someone used to Microsoft Windows isn’t going to be too happy. The WindowMaker method: open the application you want to dock; drag one of the icons, the one without the title at the top, to the dock. That’s it.

Unless you’re just skim-reading, you should have found something odd with the last paragraph, even if you ignore my English: “…drag one of the icons…” An explanation is in order here. WindowMaker does not just have an icon to indicate that an application has been minimised. If you launched a program any way other than from the dock then you get an extra icon, just as if you’d minimised the window but without a title at the top. Until I figured what it was for I was incredibly confused! The first one is the application — use it as you would in any other window manager. The other can be dragged to a dock. It’s a waste of screen real-estate and I can’t help but think that there must be a better way of doing it.

Other configuration parameters are also handled graphically in WindowMaker. Try to change some of the colours, or the backdrop or any other parameter in AfterStep and it’s back to the configuration file. WindowMaker has a very nice WindowMaker Preferences Utility to allow you to change them all graphically. I’ve not had the need to dig into the GNUstep directory yet it’s so complete.

The Verdict

If you don’t know that I’m impressed then you just haven’t been paying attention(!). While there are faster and smaller window managers, WindowMaker is small and fast enough. It is also very simple to use — it’s one of the first free window managers that doesn’t insist that you edit large and complex configuration files — looks superb and is fully functional.

And finally, despite dire warnings that it’s still beta software, it seems to be more stable than many commercial applications. (I only had one glitch: I loaded Netscape once and WindowMaker vanished and twm took its place. I have no idea what happened there!)

Introduction

Writing reviews of Linux programs might sound like an easy option. I mean, some developers spend fantastic amounts of time honing their latest creation, making sure it’s exactly right. And all I have to do is load it up and destroy all their hard work in a few carefully chosen words. (I assure you that, despite appearances, most of these words are carefully chosen.)

I should make it clear that I don’t take my responsibility lightly. When I decided to take a look at FreeCiv, a GPL’d clone of Civilizations, I made sure that I thoroughly tested it before passing judgment. Actually, I spent much longer testing it that I’d intended but more of that later.

Starting up

At this point I’d normally report on the problems I had with the installation. Happily there’s nothing to report this time: the RPM’s installed and worked without issue.

The only ‘funny’ is that you can’t just fire up FreeCiv and go. First you have to start the server process, add any computer players (AI’s), set their level as appropriate, and tune any other parameters. It’s not really that odd or difficult, but it is different to the original, and perhaps it could be easier. (Perhaps the client application could default to being the server if there isn’t already one?)

Once the game has been started in the server process, a familiar looking screen appears. The icons are quite well drawn and will be familiar to anyone who has played the original. My flat-mate, a more experienced player than myself, claims that the graphics aren’t as good. (But then he still plays Civilizations version 1 just in case 2 isn’t as good!)

Play the game

In the same way as in Civilizations, each player gets a turn where they can give each unit orders, create cities and alter what ‘stuff’ each city produces.

It’s all very straight-forward. You can move units around using the cursor keys. You can give them orders using the ‘Actions’ menu. You can check out the composition of a city by double-clicking on it. I’ve never played Civ ‘in anger’ but I managed to pick up the mechanics of it all just by playing around.

If I had needed documentation, by the way, I wouldn’t have been disappointed. There’s rather a lot of it and it seems thorough. However, like much of the game, and Unix in general, it does assume that you know what you’re talking about. I don’t see that as a big problem, though, as there are plenty of tutorials and FAQ’s on the web, some of which are FreeCiv specific and some of which apply to Civilizations but will still be applicable.

There are a few small niggles, however. For example, after using the menus you can’t use the cursor keys to move a unit around the screen. (You need to click back on the main window first.)

Overall

I don’t think that it would be entirely fair if I said I didn’t like it because I never did very well at it! Firstly, it proves that the computer players are of a good standard (I set them on the easy level!). Secondly, even though I was losing I was enjoying it. With each game I became more proficient and lasted longer, although whether this was due to my leadership or the geography I’m not sure.

Either way, I’m inclined to try and find out more. This is, perhaps, the highest praise I can think to give to a game.

Note that at the time of writing the beta version of 1.8.0 had just been posted to the FreeCiv web-site.

What’s here?

Welcome to “The Penguin Says,” the Linux application review site.

There are many sites providing links to Linux software, but very few that rate and review them. That is what you’ll find here. Although I fully support free software, you’ll find open and honest reviews here. If an application is a load of rubbish, or too flaky for real use, I’ll say so. But then, if it shows promise, I’ll mention that too.

You can find more about The Penguin Says here. When you read that text, bear in mind that it was written in the summer on 1998, before Linux became the ‘media-darling’ that it currently appears to be.

The reviews

Here is a list of all the Linux application reviews. Note that they are in alphabetical order rather than the order in which they were written.

• Abacus
• AfterStep
• BlackBox
• Cooledit
• FileRunner
• FreeCiv
• GIMP
• LinCity
• Linux
• LyX
• NEdit
• Netscape Communicator
• Psion Series 5
• SFM (Simple File Manager)
• Siag — Pathetic Writer
• StarOffice 4
• StarOffice 5
• tkCVS
• UAE
• WindowMaker
• WINE
• Corel WordPerfect
• WWWThreads

All reviews were performed on my Pentium 120 with 32Mb of memory, running RedHat 5.0 with all patches up to June 1998.