Applications: December 2007 Archives

I continue to praise Geany, the GUI text editor in Puppy Linux.

I'm not a programmer, but I use text editors just about every day. Especially for Web work, text editors are must-have tools for writers and editors.

And for me, a text editor needs to do a few things -- and do them well.

Here is my list:

It needs to start up quickly.

It must open ALL files, not just those with .txt suffixes.

It must have word wrap but NOT actually wrap the lines in the text file itself (i.e. wrap for display purposes only).

It must have a search/replace function.

It must have word count.

It must change upper-case to lower-case ... and lower-case to upper-case.

Not an extensive list, but many, many text editors cannot do these simple tasks. Mousepad in Xfce can't (though it is fast), Gedit in GNOME can't. Beaver in Damn Small Linux also doesn't do all of these things.

What I use in Windows: The free EditPad Lite -- a great text editor.

Mac OS X: the default GUI text editor in OS X (I think it's called TextEdit, or something like that) is pathetic. Sorry Mac people. I'd love to have someting better for when I use the Mac, which is often.

Do I use command-line editors? Yes, I do, but it's just much easier to use a GUI editor when I'm working in a GUI. Half of the time, I'm cutting and pasting type from Web pages, e-mails and the like, and it's just too hard to do with console editors. I tend to stick to Nano (Pico in the OS X console) because I just don't use vi enough to keep my skills fresh. And I don't want to get anywhere near Emacs -- I just don't have the desire or the time. Give me Nano, and I'm happy at the console.

Again, I don't program -- I just write, so my requirements for a good text editor are probably very different than the usual crowd at which text editors are named, meaning coders.

I've had Debian Etch with the Xfce desktop on the $15 Laptop for a couple of weeks. It took up a lot less space than Slackware 12 with Xfce (and NOT KDE), so I left Debian on the computer, a Compaq Armada 7770dmt with 64 MB of RAM.

I had a trick to get the ALSA sound working in Damn Small Linux, but it wouldn't work in Debian. I don't have the soundcore module installed, and that's the next step in getting the sound working.

I also found out that doing a Google Docs session in Debian on this box is ... frustrating. The screen moves way too slow.

So I went in a different direction. I popped in the Damn Small Linux 4.0 CD (I know they're up to 4.2, but I haven't downloaded and burned the new ISO yet ... I plan to soon).

Already the box seems much snappier. I'm using the toram boot code, which means the whole OS pretty much loads into RAM, but DSL does use the Linux swap partition on the hard drive. I find this to be a good compromise because I'm not committing to even a "frugal" install on the hard drive, and whenever I want to upgrade, I can just burn a new CD and use it -- I'll be using the same swap space when needed, but I won't have to upgrade any files on the hard-drive install because I'm not doing one.

As I've said before, for Linux distributions designed to be used as live CDs -- like Puppy, DSL and Knoppix -- I find that it's best to use them as they were intended and not to do full installs, or even frugal installs (although I've violated my own "rule" many times).

I'm going to run DSL 4.0 for awhile on the Compaq. I might switch it out for DSL 4.2 sooner rather than later because I use MtPaint -- a new app in DSL 4.2 but a longtime Puppy Linux image editor. Once I get a chance to run a Google Docs session in Firefox on DSL, I'll be able to see if it goes better than with Debian ... and how much better. I'll do the same with Puppy Linux before committing to anything, but if I'm using live CDs, there's no reason why Puppy and DSL can't coexist very well on this box.

I still need to do the actual tests, but I get the feeling that I'll be wiping Debian Etch off of the hard drive and leaving just a Linux swap partition and empty ext3 partitions for Puppy and DSL. We'll see.

I've been using IrfanView heavily on my Windows box. And yes, I love it more than ever. I've been using it to process screen grabs (I use the Print Screen key to copy the screen image, then I start the new image in IrfanView, paste it in and crop what I need).

And I love the "create custom selection" feature, which I have preconfigured with the exact pixel dimension I need for one of the images I have to cut regularly. First I size down the image to a little bigger than I want it, then I go to "create custom selection" in the menu, and a box the exact size I want it is superimposed on the image. I can then crop right there, or right-click with the mouse to move the box exactly where I want it.

Now that I have Wine on my Ubuntu 7.04 install (yes, IEs4Linux did work), I need to start trying to run IrfanView under Linux. If it works, I will be a very, very happy camper indeed.

I've decided to go all in with Google Docs.

Since it's easy to upload files to Google Docs from the app itself or via a unique e-mail address provided to each user, I'm throwing everything up there I can find on my office hard drive. The only "problems," so far are that i have quite a few documents in AbiWord format that aren't recognized by Docs. I didn't expect it to work, but I tried anyway and got the error message, "Sorry, we do not currently support '.abw' files." Does that mean they might do so in the future?

Not a big deal either way, as I can re-save them in .doc format and upload if I need to. The "critical" files that I made in AbiWord are all in .doc format (since I tend to e-mail them to people who don't use AbiWord), and those went up fine.

It's a good feeling to a) have a backup of everything and b) have the ability to access the files from any Web-connected computer.

As I say every time I write about Google Docs, I've set my browser to NOT print the customary headers and footers so I could print a clean-looking file on paper if I wanted. But I haven't really been printing out anything lately, and that's probably one of the biggest non-secrets of Google Docs -- we so rarely print stuff, and the more accessibility we have to docs on the Web, the fewer reasons we have to commit them to paper in the first place.

I saw an ad for Google Apps, which links to this page containing a video of what Google Apps can do for the business world. Here you can compare the various versions, meaning why you should spend $50 per person per year rather than nothing.

I already solved my biggest problem with Google Apps by killing out the headers and footers in Firefox's printed pages: go to File -- Page Setup -- Margins & Header/Footer and set everything to "blank" under Header/Footer.

Since the insidesocal.com domain on which this blog lives has had so many problems with DNS-type attacks, with the solution being blocking the whole of Europe, I've been spreading my technological cheer around some other blogs.

It gets confusing. And in an attempt to actually spend a little time on the entries before they're published, I've been writing in Google Docs. Actually, testing gOS, which relies heavily on using Google services through the Firefox browser, made me take another look at Google Docs, which I've used on and off for awhile.

The whole idea is to have all my writing stored in one place, accessible from any network-connected computer, so things aren't left to die in one /home directory or another on the six or so computers I use during any given week. And as I say, maybe writing and not immediately publishing will make for better entries overall. Later but better.

And while on the subject of Europe, there's a rumor floating around that the IP block for the continent has been removed. So if you see this entry and happen to be a European, please send me an e-mail and tell me the country from which you hail. Thanks.