Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Why is the editing window so small?

So I'd like to bring up the issue of the editing window in Twine 2.
It's too small and I can't find any way to make it wider. Maybe it's just me being an idiot, maybe it's the program choosing aesthetics over ease of use in one of the most crippling ways I have ever seen.

There's enough room for exactly 63 characters in a single line. When dealing with anything more than a single nested statement, that is simply not enough space. Heck, I have individual for loops where the condition is so long it pushes the $i++>> down to the next line, no nesting at all.
Why can't we make the editing window wider? Why does it wrap at a mere 63 characters? Even Microsoft Notepad allows for 1024 characters in a single line.

I feel like allowing the editing window to be resized and increasing the wrap limit to a friendlier number, like at least 256, would greatly improve Twine's user interface and make code much easier to work with.

A small sample of my code pictured here:
RBt5FVw.png
Notice the number of times the line reaches the end and has to wrap to the next line.

Comments

  • [opinion]
    The Twine 2 application GUI was originally designed to be usable on a mobile device like a Table so certain assumptions were made by the developers, the width of the Passage Editor being one of them.

    Later a node-webkit (nwjs) based installable release of the Twine 2 application was released to solve a number of issues, one of them being the size limitation of the web-browser's localstorage. For expediency aske and so that the same code-based could be used for both the web-browser based and the nwjs-based applications the GUI was not altered.
    [/opinion]

    The GUI code is currently being changed so I suggest that you create an issue on the TwineJS project website with any suggestions you have related to improving the GUI. That way the issue and any responses between you and the developers can be tracked because topics on these forums get lost fairly quickly.
  • Good to know. I'll create an issue and see where it goes. I know a few other twine devs who've been irked by this point in the past, so I hope it's approached at some point.
  • greyelf is essentially correct, and it's something that I would like to address in the future. The tension here is between what's a comfortable width for editing written text and what works best for code. I leaned towards the former initially, but it's less than ideal for people working on code-heavy stories like yourself.
  • If you're looking for a balance to tension, perhaps an option to toggle between the two would work?
Sign In or Register to comment.