New posts Mondays and Thursdays (usually). RSS.
Tell me what to install next: writingonlinux@gmail.com

WikidPad on Ubuntu

The other day I was bumming around on IRC, decidedly not doing any sort of writing at all, when I happened across a conversation between several Internet folk about nothing other than writing software! One of these fine IRC-persons mentioned that they found a program called WikidPad most useful in keeping their thoughts straight. WikidPad, in a similar fashion as my note-keeping program of choice, Zim Wiki, acts as a personal wiki for your thoughts. It has an advantage over actual server-side wiki software, such as MediaWiki, in that it is easy to set up and everything is kept locally on your computer. However, the main advantage of using a wiki – being able to create separate pages and link them together at will – is preserved.

Doubtful I would find a program to replace my beloved Zim, I decided to give it a whirl anyway. Unfortunately WikidPad isn’t the most straightforward of installs, which is why I’ve chosen to spend this post talking about the actual steps I took to get the program up and running.

For Windows users, WikidPad comes with a single binary installer that takes care of anything for you. But if you’ve so much as read the title of this fine blog, you know we’re not dealing with something so simple as that. No, we Linux users get treated to a lovely little zip file of python code!

The first thing to do, of course, is to grab the zip file from WikidPad’s home page and extract it somewhere. Be careful, though, as this is one of those zip files you’ll want to unzip into a separate folder, lest the source files scatter everywhere in your Downloads folder. (Alas, I speak from experience.)

Next you’ll need to download one of WikidPad’s dependencies – wxPython. Open up a terminal and type in the following:

sudo apt-get install python-wxversion

After that, you can start up WikidPad by using cd to navigate to the folder you extracted its files to and running the command

python WikidPad.py

But let’s be honest, that’s pretty lame. We’re in Unity here with a fancy launcher and dashboard – we can do better than running a command every time we want to it up! So instead, open your favorite text editor and let’s make a really simple script called WikidPad.sh:

cd ~/Downloads/WikidPad
python WikidPad.py

With the first line modified to reflect wherever you dumped the WikidPad files, of course. Once you save it, don’t forget to make the script executable:

chmod +x WikidPad.sh

Now let’s add this to the Unity dashboard. Search for a program called “Main Menu.”

If, for whatever reason, you don’t have it, you can also find it in the Ubuntu Software Center. Open it up, click “New Item,” and write the full path to your bash script under “Command”.

Press “OK,” and WikidPad will be available in the dashboard.

Magic!

And now, having gotten this far, I might just see what the program’s actually like. Who knows!

Advertisements

Suggestion box and PostAWeek

Thanks to everyone who’s commented and recommended programs this week. I’ve been able to try out a fair bit of new stuff – Tomboy Notes, Synapse, and FocusWriter, to name a few – and really, discovering new Linux software is a major part of what this blog is about. So again, thank you.

I’ve put up a suggestion box of sorts if you have something you love to use and you’d like to recommend it. Don’t take it as a reason not to recommend stuff in the comments though – comments are always preferable since it usually provokes some interesting discussion down there. But if you have something you’d like to recommend, and it’s totally unrelated to whatever nonsense I decided to post that day, pop it in the box and I’ll give it a go.

Also, I’m joining PostAWeek. Why not PostADay, even though I’ve been posting every day? Because I’m not sure if I will make a post a day. I’m only posting so long as I have something about which to post. Every post I make, no longer how long or short, is something I want to share because I think someone will find it useful. I might be wrong, but at least that’s my intention. I don’t want to force myself to keep posting if I’ve run out of stuff to talk about. Cluttering everyone’s feeds and inboxes with useless junk wouldn’t get any of us anywhere, would it?

But I do want to write. That’s why I’m writing on Linux, after all, and why I’m posting part of what I’m working on every Sunday. I can’t make it my goal to post about Linux every day, but I can make it my goal to post a bit of what I’m writing every week.

So consider this my official PostAWeek announcement. Maybe a couple weeks late, but there it is.

In the meantime, keep suggesting programs – no matter how trivial you might think they are. I don’t care if you flood the suggestion box with requests; it’s always a treat to have new software to try.

As always, thanks for reading,

awkisopen


Saturdays are now meta.

Told you I’d be doing something different today. It occurred to me that while I’m blogging about writing on Linux, blogging itself is a form of writing, and you can certainly do it on Linux – so why not blog about blogging, too? Besides, I’ve been meaning to blog about my experience with WordPress so far and I didn’t want to shoehorn it into some random post.

So instead, Saturdays are going to be my metablogging days, and I’ve successfully used the word “blog” enough times that it now looks weird to me. Blog. Blog blog blog.

Anyway, similar to how this isn’t my first time on Linux, this certainly isn’t my first time on WordPress. This is my first time “blogging with a purpose,” though – everything before this had been a random collection of whatever interested me at the time. Instead this blog is about one specific subject, and I have to tell you, writing it is a lot more enjoyable. It’s easier to write when you’ve narrowed your scope, for one thing. And for another, I like to think I’m helping out future Googlers looking for writing software.

I started this blog a bit more than a week ago because of the disappointing search results for writing on Linux. And no, I didn’t just search for that – I’m talking about writing software on Linux, writing in Linux, freeware word processors, and what have you. Originally I was going to spit out a few posts about Linux with the maximum of a post a day (so as not to overwhelm anyone, including myself) and then take breaks when I ran out of software to talk about.

But my list of stuff to try out has exploded. Really, I thought I’d do maybe ten posts on my first run. Instead I have thirty or so separate subjects to write about, thanks to other bloggers’ posts and comments. As it turns out, there is a ton of stuff out there for writers. Now I’ve made it my mission to bring it to you.

Enough about Linux, let’s talk about WordPress. Specifically, about finding stuff to read on it.

I didn’t come here just to write, I wanted to see what other people had to say about writing on Linux too. For the past week or so I’ve achieved this by throwing a ton of keywords into WordPress’s “tag surfer” and reading whatever popped up. I found quite a few good blogs/posts from that alone, but recently it’s dried up for me.

The problem with tag surfer is, not everyone tags their posts! And those who do usually don’t tag them enough. Tags aren’t like categories, where you keep them limited to as not to turn your blog into an organizational disaster. Tags are supposed to help people find your stuff. So even if you mention a certain subject in only a paragraph of your post, please tag it! It helps out those of us who are looking for new stuff to read.

In the meantime, Google provides a nice way of supplementing the tag surfer. Go to Google and type this in:

site:wordpress.com “keyword”

Where keyword is, of course, whatever it is you’re looking to find posts about. Once you do that Google will spit out every post on wordpress.com with your keyword in it. That’s pretty useless if you’re trying to find fresh posts, so expand “show search tools” in the left column and select either “latest” or “past 24 hours”. “Latest” gives you a live feed of posts in reverse-chronological order, which is pretty neat, but if you’re catching up on stuff for the first time today I’d stick with”24 hours”.

So help me out here – what’s some other ways to find new stuff on WordPress?


Zim, your personal wiki

There isn’t a lot I can say about Zim; it’s something you have to experience for yourself.

I will say that I’ve been searching for this program for years. You see, I like wikis. A lot. I’m even an administrator on one that’s fairly well-known. There’s just something to it, something about information on a wiki that automatically makes it feel important and organized.

And it is organized – wikis give you a crazy amount of flexibility. A page could be anything from a plot outline to a character’s biography to the first draft of a chapter. Start adding pages to categories, and you’ve got a super neat hierarchy of your own personal design.

As I’ve said, I’ve been searching for Zim for a long time. I’ve tried everything from Wiki on a Stick (a single HTML file that acts as a wiki) to actually installing MediaWiki (the stuff Wikipedia runs off of). Most of these have proven to be slow and clunky, with complicated ways of storing data. Accessing your writing outside of whatever program you wrote it in was pretty much impossible. And if you had just one bad save of your wiki-on-a-stick… woo boy.

Zim, however, is nothing like that. Not only is Zim a speedy and reliable program, but it doesn’t tie you down. Every page you write is saved in an easily editable plain text format, with a little bit of wiki syntax for links and what have you. You can create as many wikis as you want with as many categories as you want in each, and even insert images. And if you don’t know wiki syntax, don’t worry – Zim is WYSIWYG with extremely simple shortcuts for useful things like checkboxes and bullet points.

Whether you’re looking for a wiki analogue or just a new way of keeping your thoughts organized, check Zim out. I don’t think you’ll be disappointed.

Update: So you know, this weekend I’m going to be trying something a little bit different for this blog… but we’ll be back to our regularly scheduled Linux blogging by Monday 🙂


Helping OpenOffice feel a little more familiar

When I start using a program that’s supposed to be a replacement for a different program, as OpenOffice Writer is for Word, there are always little differences that bug me. Fortunately, OpenOffice is very customizable, and I’ve found a quick trip into Tools -> Options easily solves most of my problems. Here are a few things I changed straight off to make OpenOffice (and Linux itself) a bit more comfortable for writing.

Feeling locked in

To start off with: that gray boundary around the text. I mean, what?

I get that it’s supposed to help me see where the margins are, but c’mon, I think I can see that easily enough from the text itself. And there’s something off about text that directly touches a border, like I’m looking at a poorly-formatted webpage.

To get rid of this claustrophobic box, untick “Text Boundaries” in the View menu. Much to my surprise, after turning the boundaries off once, they never came back to haunt me again like so many options in Word did. Nice!

A little too familiar

I couldn’t go one quotation mark without that little box in the lower-right corner popping up. Back in my days of writing on OS X, I remembered that box being a minimalistic image of a lightbulb against a purpleish background. Nowadays it is the cheesiest damn thing I’ve ever seen. Before it was just an annoyance, and I never bothered to turn it off; now it’s a borderline embarrassment. Who thought a cartoon lightbulb with a face was a good idea? And if this is supposed to be OpenOffice’s version of an “Office Assistant” – which I’ve no doubt it is – isn’t OO aware of the near-universal hatred for such a thing? If we’re starting afresh with an open-source office suite, why take the pains to replicate that which is undesired in the first place?

Whatever.

Tools -> Options -> OpenOffice.org -> General -> uncheck Help Agent. It never bothered me again.

A single problem

Sometime after I switched off the lightbulb I realized that, for all its fanfare about correcting double quotes, OpenOffice does not, by default, correct single quotes.

To set right that which is wrong, go to Tools -> AutoCorrect Options (it’s just above regular ol’ Options) and select the “Localized Options” tab. There you’ll find the option to correct single quotes as well as double quotes. Sanity has been restored.

That which is left behind

After changing these three simple settings I found myself warming up to OpenOffice a lot more. There is one last thing I’d like to have back from my Microsoft experience, though, and that’s the fonts.

Before I go any further, I’m going to put up a huge Disclaimer here: There are thousands upon thousands of free fonts. There are even a lot of good ones, including those that come with a fresh install of Linux Mint. I will be exploring free fonts and free font alternatives later on, because getting tied to Cambria and the like while I’m trying to get away from Microsoft Office is at best silly and at worst awfully hypocritical.

Still, I have documents that I’ve already started writing before I switched to Linux, and I’d like to see them in the proper font. Sure, I could change them, but then I have even older documents I might want to reference, and so on and so forth. Long story short, it’s easier to have these fonts available than not. I’m just not going to limit myself to them, that’s all.

As for why I had to go through the following process to get my fonts back instead of simply copying the fonts over from my Windows 7 fonts folder (after all, I am in a virtual machine): the Fonts folder in 7 won’t open up without crashing the whole system, and there’s only so many reboots one can take before one starts thinking “there must be an easier way!” As it turns out, there is.

If you want to legally(ish?) download the new fonts available in Vista and 7 (Cambria, Candara, and the like) you’re in luck – you can download and extract the fonts from the Microsoft Office 2007 Compatibility Pack. And if you don’t want to go through all that trouble, there’s a script that can do it for you instead.

(Note: As of this writing, there’s what I can only assume to be a bug in the script that forces you to run apt-get install curl before running the script itself. So do that before following these steps if you have trouble.)

wget http://plasmasturm.org/code/vistafonts-installer/vistafonts-installer
chmod +x vistafonts-installer
./vistafonts-installer

If the script executes correctly, you’ll now have a wider selection of fonts available in ~/.fonts. Unfortunately there’s one more bug I haven’t mentioned when it comes to these fonts – font smoothing doesn’t work on some of them. Again, this wouldn’t be a problem if we installed truly free fonts instead, but it’s better to have some backwards compatibility than none at all.

Oh and, if you’d like to start exploring free fonts instead of grabbing back Microsoft’s, check out dafont.com. It’s my favorite site for that sort of thing.


A word about AbiWord

I’ve only just started using AbiWord, but I’m already leaning away from it as my word processor of choice. I know I can’t expect total compatibility with Word documents, but I expected a little better than this:

I tried opening up a .doc file that I’d been editing (without incident) in Word 2010 and OpenOffice, and the strangest error occurred. A few pages in, several of my paragraphs were missing their first few words. I couldn’t find a way to recover them, so I closed it.

But before then I must’ve saved it somehow, because the next time I opened up that file in OO Writer I had random spaces everywhere.

So yeah, AbiWord. Not the greatest when it comes to Word compatibility. (And if Google is anything to go by, .odt isn’t looking so hot either.)

I’m still going to give it a go. I’ll just avoid opening up stories I’ve already started elsewhere, I guess. Maybe it performs better when you save and load documents in its own AbiWord format?


Keep documents organized with Compiz tabs

Sometimes you just gotta have several documents open at once. Whether you’re referring to an earlier draft, a page of notes, or even somewhere else in the same document, you’ll run into this situation eventually. Luckily I’ve got a fairly large (1920×1080) external monitor at my disposal, so side-by-side comparisons aren’t a problem. But for those of you who aren’t packin’ extra monitor space, I’ve got another solution for you.

Compiz Fusion, the window management software that comes with Mint 10, has a plugin that allows you to group and tab windows together. To get the plugin, you need only install the package compiz-fusion-plugins-extra.

I should warn you that by installing this package you will be installing a crazy number of compiz plugins. So if you’ve been known to play with the compiz options you have already, you should set aside an hour or so to meddle with these and get it out of your system.

sudo apt-get install compiz-fusion-plugins-extra

Once you’ve installed the package, head on over to your Compiz Settings Manager and activate the plugin (titled, quite accurately, “Group and Tab Windows Together”).

Here’s how it works:

Let’s say I’m writing a series of short stories (I am). I like to reference previous stories while I’m writing the next one. As a result, I have three windows open, one for each story, and it’s obviously taking up quite a bit of screen space:

But with the grouping plugin installed, I can select all three at once (by selecting each one and pressing Super+S) and tab them together with Shift+T.

Now I can switch between all three windows. (Note: The glowing effect is optional; you can turn it on or off in Settings Manager. I find it kinda distracting, myself.)

Tabbing windows together isn’t limited to windows of the same size or even the same program. Let’s say you were writing something in OpenOffice Writer, but you keep your notes in a different program (mousepad in this example). These can be tabbed together too:

Becomes

There you have it – a nice way to conserve screen space without doing all that desktop-switching stuff.