color: #000;

I get an error when I try to open a Twine file I created with 2.0.4, Harlowe 2.0.0 beta:

I'm thinking of going back to 1.1 and releasing it as a minor (mandatory) update, not just because of that, but also because there isn't any real infrastructure in TwineJS to allow two versions of th…

I've made a thing for automating this process, though it's still not so much for the faint of heart. It should work on Windows or Mac and generates Windows, Mac, and Linux apps.

Hello,

Not pressingly important, but a question:

Actually, it looks like my project became irrelevant at some point, as now the twinejs repo includes a build process for NW.js apps by itself.

node-webkit can make a nicely packaged Windows, OS X, or Linux app, but I think for iOS or Android you'd want to look at Phonegap as already mentioned.

Sorry about this falling off my radar for so long - real life stuff has had me awfully distracted for a while.

The only problem with that is it doesn't animate the UI in Firefox, which I find totally weird, since that same code animates passages in Firefox.

Thanks a lot Claretta and Inspector Caracal. I'l test both suggestions as soon as I can and tell you about the results.

After turning off the background images I'm still getting that slow step-in opacity jittering. (the opacity filter that gets applied to the whole screen when the ui options open).

That's a good thought, I'll give it a go.

Claretta wrote:

I managed to smooth it out by inserting this monster of code: <br />#ui-bar, #ui-body {<br />-moz-transition: none;<br />-webkit-transition: none;<br />-o-transition: color 0 …

The other problem I am finding with the Chrome bug is that the default transitions for the save/load and restart screen look like crap now.

That's unfortunate. Maybe I'll redo my story in 1.4 then. It should be easy enough to copy paste stuff across.

Claretta wrote:

My situation is a little weird from what I've seen on the forum and from googling.

Neoroman wrote: