What is wrong with spacing text from borders? padding for tabs, padding and margin text blocks? why so many lines? well, I can answer that: if you put two elements two close and you don't want to separate them you need a line between.
IMHO is fitts-law abuse, but is having everthing stuck together a functionallity I fail to recognize? Both in Cheese Paper and in Manustkript are designed using a compressed UI.
In ancients times when they needed to fit more text within physical boundaries they invented scrolling, pages, chapters, volumes. They even folded maps and other illustration inside books.
It has scrollbars, but there's benefits to having more on an individual page at once. The tradeoff point seems unclear but everyone must recognize some tradeoff there.
Foldable maps allow for getting everything on one view by having the final display area be enormously larger, which isn't an option on laptop screens.
I don't get why we get all these kinds of things to support writing in markdown when org-mode already exists and can support pretty much any use-case. Its not that difficult to master.
It's hard to tell about "looks better": the link for "screenshots" takes you to the #team anchor on the page, which is actually the "latest news" section.
Better documentation (well, actually, more like documentation at all), 100+ contributors, 10 years of contributions.
There's a lot of general hand-waving about its featureset and whatnot - and an odd jab about non-English support - but no explanation of how non-English language support is lacking in other projects and why hers is better. And am I really supposed to believe that her project has better non-English support than than something that has 100+ contributors over ten years?
Cheese Paper is written in rust. That's reason enough to give it a try. Manuskript may have more features if you need them, but it's written in python+js, and has a more obtuse file format.
There's also novelWriter which is also python but at least it uses pyqt.
"Is the text too readable? Colors too pleasant? Not enough whimsy?"
I found text in the theming section quite funny. I think most custom themes for many different pieces of software manage to provide solutions to at least the first two of those questions.
Is "Unexpected Failure Mode" the name of the current story/document or a feature of the editor?
The author already added theme randomization, I'm slightly worried that they could also add a mode that intentionally crashes at random times to encourage people to save often...
I recently picked up writing short stories again. I briefly looked at different editors, but ended up just doing it in vscode (daily driver). I'll make sure to look at cheese paper for the next one, looks like it has some cool features!
A feature that I have been dreaming about is making an editor that treats each paragraph like a unit of work, and the full text is created by linking together different paragraphs. That way you can easily try different ways without deleting any text. Sort of like nodes in a graph.
or you could come up with a notation that works in any editor. I have [1].
> That way you can easily try different ways without deleting any text.
Sorry I haven't yet read your story. Here is how I would explore alternatives with my notation. I do this when designing software/algorithms etc.
```
Elias performed at this level for about a year. He was up for a well-deserved promotion to staff engineer. I sent him a meeting invite to go through the updated leveling framework to make sure we didn't miss anything.
#{
#{ Elias declined the meeting. }
#{ Elias went to the meeting but he went late.}
...
}
I'm not sure exactly what you mean by "unit of work" but I really like writing in Bike[1] for this reason, it's a hybrid text editor/outliner. It is simply my favorite rich text editor and the outliner functions provide really good affordances for organizing and reorganizing paragraphs.
Is this deliberately borrowing from Herman Melvile's "Bartleby the Scrivener"? If so it might be worth mentioning, rather than just referring to it as "my short story", since it's a nearly identical retelling of it.
“Ah humanity!” Ya, knowing this would have shaped my own reading a lot. I wonder though, if it wasn’t intentional, if the structure came from AI which would have had this in its training data. Asking one for help with outlining a story feels pretty innocuous.
> A feature that I have been dreaming about is making an editor that treats each paragraph like a unit of work, and the full text is created by linking together different paragraphs. That way you can easily try different ways without deleting any text. Sort of like nodes in a graph.
You could vibecode it. It's great for prototyping features you've been dreaming about.
Another version of this idea that's been around for a while is CherryTree. I would use it a lot more, but there's not really a way to use your notebook on mobile due to it using a special database format that nobody cares about. I love the idea of this program's data instead being a regular folder of regular plaintext files that you can do anything with. In a perfect world everything would be like this, where your files are just your files, and client programs just help you use those files in more effective ways.
Maybe it would explain itself better if that said "specifically designed for writing fiction"? (lots of other sorts of writing don't have characters, for example...)
The first sentence of the first non-bolded paragraph of the webpage is:
>Cheese Paper is a text editor specifically designed for writing, particularly fiction.
I don't think the HN submitter is the author of the software, but if you're just referring to the HN submission title then maybe they'll take you up on your suggestion.
I think it would explain itself better if it explained precisely what makes it better or different from what already exists; Manuskript (open source) and Scrivner (closed source.)
IMHO is fitts-law abuse, but is having everthing stuck together a functionallity I fail to recognize? Both in Cheese Paper and in Manustkript are designed using a compressed UI.
Foldable maps allow for getting everything on one view by having the final display area be enormously larger, which isn't an option on laptop screens.
I'm saying this as an Emacs user.
It's hard to tell about "looks better": the link for "screenshots" takes you to the #team anchor on the page, which is actually the "latest news" section.
The "How to use" link in the download for 0.17 takes you to https://sourceforge.net/u/gedakc/profile/
This does not inspire confidence :-/
https://github.com/olivierkes/manuskript#manuskript
There's a lot of general hand-waving about its featureset and whatnot - and an odd jab about non-English support - but no explanation of how non-English language support is lacking in other projects and why hers is better. And am I really supposed to believe that her project has better non-English support than than something that has 100+ contributors over ten years?
There's also novelWriter which is also python but at least it uses pyqt.
I found text in the theming section quite funny. I think most custom themes for many different pieces of software manage to provide solutions to at least the first two of those questions.
(I find that a refreshing perspective.)
The author already added theme randomization, I'm slightly worried that they could also add a mode that intentionally crashes at random times to encourage people to save often...
A feature that I have been dreaming about is making an editor that treats each paragraph like a unit of work, and the full text is created by linking together different paragraphs. That way you can easily try different ways without deleting any text. Sort of like nodes in a graph.
And here's my a corporate themed short story: https://dahl.dev/capacity
or you could come up with a notation that works in any editor. I have [1].
> That way you can easily try different ways without deleting any text.
Sorry I haven't yet read your story. Here is how I would explore alternatives with my notation. I do this when designing software/algorithms etc.
``` Elias performed at this level for about a year. He was up for a well-deserved promotion to staff engineer. I sent him a meeting invite to go through the updated leveling framework to make sure we didn't miss anything.
#{ #{ Elias declined the meeting. } #{ Elias went to the meeting but he went late.} ... }
```
[1] https://github.com/pratikdeoghare/brashtag
The linebreaks will be added much better by any typesetting algorithm anyway. Like LaTeX.
That's it, no need to overcomplicate things with nodes that are probably the internal memory representation in the text editor anyway.
[1] https://www.hogbaysoftware.com/bike/
You could vibecode it. It's great for prototyping features you've been dreaming about.
>Cheese Paper is a text editor specifically designed for writing, particularly fiction.
I don't think the HN submitter is the author of the software, but if you're just referring to the HN submission title then maybe they'll take you up on your suggestion.