klembot
commented
4 years ago Right now no, and I think it would take a lot to convince me otherwise. Here are my reasons:
- The built-in browser engine in the app is by its nature frozen... it can never be updated short of upgrading the application itself. So if you are extending a story format, you may be doing so against a somewhat outdated browser engine.
- It locks people into using Chrome dev tools, which they may or may not like.
- It caused its share of bugs since the app and the story live inside the same browser process :)
- It makes cross-browser testing difficult, since you have to manually publish and re-open. At least with this, you can choose your browser.
- It has a happy side effect of allowing a last-ditch backup if a story gets trashed, because Twine creates temp files during the preview process.
That said, I'm still open to arguments otherwise, but I get the sense that more authors were happy about switching to previewing externally than internally.
alex-bender
Is it possible to open stories like it was in previous versions, inside of the app itself, not in default browser? After clicking play button the new tab is opened in my firefox, but I'd like to have that in app.