WriteRoom 4.0 (Preview 413)

WriteRoom guide is much updated.

WriteRoom product page is much updated.

  • Added completion of attached files after ](
  • Added opening RTFD files as text bundles
  • Added RTFD export when a document has attachments
  • Changed pictures and diagrams to show rendered by default
  • Changed find text to be shared with other apps (⌘E)
  • Changed find to highlight matches only while its panel is open
  • Improved Split Editor speed in large documents
  • Improved pictures under the overview zoom
  • Fixed some .textbundle files failing to open
  • Fixed a crash when quitting with Quick Look open

3 Likes

Let me know if bugs come up, but feeling close. Big remaining task is figuring out App Store submit.

I may be misunderstanding how images should be handled but I expected the following type of link to work, instead I see “JPEG Missing File” image.

An example is below with both the link and the image shared from a website.

![](upload://7dp6pIdr26g1eOH9cAtuDyGMyya.jpeg)

Ah, that’s a reasonable way to think they should work.

But currently the way they work is you drag and drop an image or file into your WriteRoom document. Then it should show up as an image. So it’s for local images that are stored as part of your document.

Reference links:

I added www.john.de to a fresh markdown file with WriteRoom and the link in the therefrom exportet .html links to this:

file:///Users/myusername/www.john.de

Displaying the file in iA Writers preview shows an even longer link.

Thanks, but I’m not able to reproduce this yet. When I start with:

[hello][1]

[1]: www.john.de

And export to HTML I get:

<p dir="auto"><a href="www.john.de">hello</a></p>

What are you doing differently?

OK, thanks for explaining.

I don’t know. Is it maybe a system setting?

The md. ist

# Testdabei für Reference Links

Die ist ein Referenzlink [John][1]
 

[1]: www.john.de


and the HTML is

<!DOCTYPE html>

<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Untitled 2</title>
<style>
:root { color-scheme: light dark; }
body { font: -apple-system-body; font-family: -apple-system, system-ui, sans-serif; line-height: 1.5; max-width: 42rem; margin: 2rem auto; padding: 0 1.5rem; }
h1, h2, h3, h4, h5, h6 { line-height: 1.25; }
ul, ol { padding-inline-start: 0; }
li { margin-inline-start: 1.6rem; }
li > p { margin: 0.15rem 0; }
blockquote { margin: 0.5rem 0; padding-inline-start: 1rem; border-inline-start: 3px solid currentColor; }
pre { overflow-x: auto; }
code { font-family: ui-monospace, SFMono-Regular, Menlo, monospace; }
img { max-width: 100%; height: auto; }
table { border-collapse: collapse; }
th, td { border: 1px solid rgba(127,127,127,0.4); padding: 0.25rem 0.6rem; }
dt { font-weight: 600; }
dd { margin-inline-start: 1.6rem; }
dd > p { margin: 0.15rem 0; }
span.smallcaps { font-variant: small-caps; }
.task-list-item { list-style: none; }
.task-list-item input { margin-block: 0; margin-inline: -1.3rem 0.4rem; }
#title-block-header { text-align: center; margin-bottom: 2.5rem; }#title-block-header .title { margin-bottom: 0.25rem; }
#title-block-header p { margin: 0.25rem 0; }
#title-block-header .subtitle { font-size: 1.25em; }
.abstract { text-align: start; margin: 1.5rem 2rem 0; font-size: 0.95em; }
.abstract-title { font-weight: 600; text-align: center; }
@media print { @page { margin: 1in; } }
</style>
</head>
<body>
<h1 id="testdabei-für-reference-links" dir="auto">Testdabei für Reference Links</h1>
<p dir="auto">Die ist ein Referenzlink <a href="www.john.de">John</a></p>
</body>
</html> `

Oh, I see. I always test this with Edit > Copy > HTML

I get your results when I File > Export > HTML… that also includes some styling that I had forgotten about. But in that one (and now that I look, in yours too) the link is correct <a href="www.john.de">, not the initially reported file:///Users/myusername/www.john.de.

I need to decide on the extra styling, but in the meantime do you remember how you got file:///Users/myusername/www.john.de in the export? That’s the part that seems buggy to me.

I do not, sorry. I created the file within WR, saved it in /username and exported it there. I will check if this keeps coming up.

413 is feeling very solid. I don’t have any bug reports, but I think you should consider the default settings before a general release. The current approach pushes far from WR OG’s feel for a first-time experience. I just gave the original a spin and was amazed how completely it got out of my way. I opened a doc, put it in full screen and really was in a “write room”.

For WR4, I “reset all settings” but I am not sure if I really got the fresh download experience. A few observations follow. Everything is just IMHO.

  • The green-screen default, especially with distortion makes the program feel like a retro terminal emulator, not a writing environment. When I go to full-screen the cursor is on the top-left and the text itself is getting maximum distortion. I say this as someone who likes the clean version of the mode and use it generally.
  • For the WriteRoom experience, the default needs to typewriter mode and a set line wrap. I don’t have strong opinions about 66 or 80 or any number for the characters, but having the lines pinned hard left feels so wrong, that at first I thought this was a bug.
  • The sounds on by default was jarring and gimmicky.
  • Having a mini-map on by default also chipped at the sense that I am in a closed writing environment.
  • Text size is handled differently across the two applications. 100% on the previous WR is larger on my screen (with my system settings) than with WR4.

All of this really comes down to what you want the product to be especially for the long-time WR users. I really like the application as I have it set up, but do think you should consider the first impression for people who are just looking for a version of WR that “just works” on upcoming versions of macOS.

1 Like

I do think “reset all settings” gets you back to defaults, minus licensing. So that is the baseline to compare against.

My thoughts are:

Markdown apps are a dime a dozen. WriteRoom has all sorts of technical and feature advantages over a generic Markdown app, but I need to visually represent that somehow. It needs to look and feel different on first launch.

Also I really do like the DEC theming and sounds as my own default, blank page just write. I do agree that for editing longer documents, especially with more markdown syntax, it’s not the right choice.

I go back and forth on minimap. Reason for showing is just differentiation. But now that the website has some videos that include it, I’ll turn it off again.

Oh, I would very much agree on line-wrap, the default should be 66? You don’t see that when you reset settings and create a new document? If you have existing documents open where the line width has been customized your Settings > Typography changes won’t effect them.

I’m less certain about Typewriter mode on by default. I normally have it off. But if the consensus is on, I could do that.

I haven’t thought much about this… I guess you are saying a larger default size is good? Related, what do you think about the “Scale text with window…” setting. I always wonder if I should have that one/off. Generally I like it on for my laptop sized screen (makes text a little bigger in fullscreen mode). On the other hand on my 27" external, it makes text a bit too large.

Edit Another default that I wonder about is the General > New Document > Open documents in full screen mode setting. Currently off, but on would get new users quicker to the WriteRoom experience, at the cost of maybe confusing some.

Would love to get more general feedback on these defaults from others.

1 Like

This is really is a hard product marketing problem. I don’t think you want a modes for WR classic or whatever, but different users will have very different first reactions here.

I am quite sure that after I reset last time, I opened a new document into full screen and it was in window-width. Now after an application re-start it is as expected. No idea if this was a user issue or a subtle sequencing problem, but the default does look to be 66.

For text size, I was surprised that WR4 doesn’t seem to respect the Accessibility setting for text size. It might be that older versions did not either, but happened to more closely match my default setting (which is kept at one or two notches over the system default.) There is no one right anwwer for text size, but macOS does have one place to set a user default.

I think I’m likely to just tweak the defaults at this point, such as distortion off.

I am trying to address this problem (at least related problem) on the product page also. Where I have two stylized DEC screens and then a standard presentation for the last one. I’ll tweak that last one to put keyboard sounds farther into background.

And, really, thanks for the feedback.

1 Like

Could you implement the Dracula color theme in WriteRoom 4?

I will, but not for initial release. But before too long. I will also open up the theme system eventually so you can make your own tweaks. A month or two after initial release bring this up again if I haven’t done it.

1 Like

There might be a slight visual bug in full-screen mode + typewriter mode. This is present in all typewriter position settings (top, center, bottom), but it’s most apparent in center and top mode.

  1. Open new empty document
  2. Go full screen
  3. Paste in a wall of text or just press return >17 times
  4. Cmd+A and delete everything

Result is that the editor won’t scroll back up to starting position, making caret disappear from view (or place it in an awkward position in center mode). Wouldn’t have noticed except if I’m in windowed mode or have <18 lines, I’m taken neatly back to start, and now it’s bothering me :smiley:

I was thinking about this in the train. What do you think about a time-locked-focus mode? It could be connected to the word goal counter. You set your target, you press go and then you are locked down to a very constricted, opinionated and very much feature reducted mode.

I don’t expect too soon, but maybe once WriteRoom 4 is out and Bike 2 is out I’ll start thinking about what’s next.

I meant as a feature to cater to the WriteRoom experience, not as another app. :slight_smile: