Trying to install the Ace plugin for Sigil
Oh, neat! (I said to myself): Within Sigil (an ePub checking/editing tool), you can add a plugin to run Ace (an accessibility checking tool)!
…What’s that? (I said to myself.) The plugin doesn’t work on Mac? OK, fine, I’ll try it in Windows under Parallels.
[Insert lengthy process of getting Parallels to run on my new computer here. It worked fine on my old computer, but you know how these things go.]
OK, Parallels is running. I’ll install Sigil in Windows.
Sigh, Windows says that not many people download the Sigil app, so (Windows says) it’s probably malware. I have to click in several places to confirm that I really do want to download and run it.
OK, Sigil is running. Now to get the plugin.
I go to the Sigil plugins directory and follow the link to the site where I can download the Ace plugin.
…Which says that before I can run the plugin, I need to install the core Ace code, because the Sigil plugin is just a way to connect the core Ace code with Sigil. OK, that’s kinda inconvenient, but I guess it makes sense. I’ll go download Ace.
Hmm, the Ace site tells me that in order to install Ace, I need to first install Node.js.
I follow the link to Node.js. It wants me to make decisions about whether I want to install it using Docker. Sigh.
…Oh, wait, there’s also a download button for a Windows installer. That looks promising. I click that.
Now I’m running the Windows installer. It launches a command-line window and runs some code that apparently launches a command-line PowerShell window and runs some more code. Many many lines of installation-related messages are scrolling by. For several minutes. Some of them are error messages.
The PowerShell window reaches a line about Authenticode verification, and then it stops responding.
OK, I guess that didn’t work. Fortunately, the Node.js install page also provides the option of just downloading a Node.js zip file instead of downloading a Windows installer. So I download the zip file, but it’s not clear to me what to do with it after I’ve downloaded it.
Then Windows Security pops up a dialog box telling me that it has found a threat. I click to find out more. It briefly shows a “Virus and threat protection” window saying that there’s a virus. Then that message goes away and it tells me that there are no threats.
And I could go on, but at this point I don’t see the point.
See, the reason I wanted to install the Ace plugin inside of Sigil is that it seemed like it would be more convenient/easier than running the separate graphical-interface Ace App. In particular, I wanted to be able to tell relatively nontechnical people who are creating and testing ePub files that they could just use Sigil and install this plugin and they wouldn’t have to bother with a separate app for accessibility checking.
But given that installing this plugin requires installing Node.js and (if you manage to do that) running an nvm command on the command line, I feel like this is not the relatively-nontechnical solution I was hoping for.
I suppose it’s nice to see that Unix-like software isn’t the only kind of software that’s prone to this kind of difficulty.
See also my 2014 post about that: “How to install Unix-like software: A text adventure.”
Ha! It turns out that in 2019, I tried to install the command-line version of Ace on my Mac, and ran into much the same kind of problems!
And that was on an operating system that I know reasonably well. I suspect that there is no way that I’ll be able to get it working on Windows. And I suspect it’s even less likely that relatively nontechnical people will be able to get it working on Windows. OK, back to the GUI app.
(I’m doing all this a day or two after I spent much too long trying to install other Sigil plugins, because the documentation about how to install Sigil plugins is hard to find (it’s in the user guide, but doesn’t come up in a Google search, and isn’t linked to from anywhere obvious), and the Sigil plugin installation system interacts badly with a default Safari setting.)