Posted March 17, 2023 by billiam
Welcome to a small update that got out way out of hand
First, Deepdwn now supports the Fountain screenplay format: https://fountain.io/
Fountain is a plain-text, human-readable format for writing and sharing screenplays. It has a lot in common with markdown, and is a good fit for Deepdwn.
You can create a new Fountain document in several ways:
File > New file > Fountain
from the application menumy_file.fountain
If you have both Fountain and markdown files in your document library, you’ll see a new Format
filter in the filter panel on the left. As with other filters, you can use this one to select (or exclude) Fountain files, or control click to combine with other filters.
You can pin Fountain documents the same way you do for markdown documents; by either right-clicking them in the file view and selecting Pin file
, or by adding Pinned: true
to the title page.
As with markdown, you can tag and categorize your documents by storing tags and categories in the document’s metadata. For Fountain, this happens on the title page, where you can add extra fields. Like markdown, Deepdwn will look for tags
and category
fields.
Here’s an example title page with some normal Fountain fields, a category, and two tags:
Title: Fountain example
Author: Deepdwn
Copyright: Copyright © 2001
Draft date: 2/26/2023
category: Help
tags:
demo
fountain
By default, in both the editor and preview, Deepdwn uses the Courier Prime font, a typeface designed for screenplays, but this can be changed (just for Fountain files!) in font preferences.
If you’re already familiar with markdown, Fountain sections will look familiar to you. These are only used for organization, and do not appear in the rendered output, and (like markdown), but they’ll appear in your document outline in Deepdwn.
If desired, Deepdwn can display some fountain elements indented in the editor while typing (like characters, dialog, and centered elements). This is not enabled by default, as it can cause content to jump around a bit.
You can find this setting in Preferences > Appearance
.
For more information about the Fountain format, visit https://fountain.io/!
Deepdwn’s Mermaid integration has been updated, both in the editor and preview view. This adds newer features, like accessible diagram titles and descriptions, and two new diagram types.
Mindmaps are nice for displaying hierarchical information, and uses a very simple syntax based on indentation.
Also pie charts.
Diagram styles have been updated. In general, they are now higher contrast, and slightly more colorful, and a little prettier.
actor
in sequence diagrams (instead of only participant
)classDiagram
diagrams```mermaid
are now treated as mermaid correctly, for better interoperability with other markdown editors. Mermaid is still allowed in bare code blocks without the mermaid
language hintExported SVGs (by right clicking them in the preview window), do a better job of embedding their styles.
The ID attribute and style blocks have been removed in favor of inline styles. This should make them more portable and fix issues with ID collision.
accTitle
and accDescr
for supported mermaid diagramsDeepdwn’s autocomplete feature has been greatly expanded.
Previously, Deepdwn supported autocomplete in two places:
In markdown documents, autocomplete now also works for footnote references, and frontmatter keys, like title
and `description.
In fenced code blocks, many languages also support autocomplete. Most mermaid diagrams now support a basic form of autocomplete as well, including the diagram type itself.
Two new font controls have been added in Preferences > Fonts
for Fountain documents, allowing you to set their font and size in the editor and preview separately.
Additionally, there is a new setting controlling only the monospace font used in markdown documents where needed.
This option is enabled when using a variable-width default font (like Source Sans or Source Serif), or a custom font and have have enabled the Mix monospace
font option.
This is useful if you’d like to use a non-monospaced font most of the time for writing, but need to use a specific monospaced font in tables or code block.
Ignore specific folders, or folder names (or patterns) globally. This is useful if you use Deepdwn to manage blog posts, or project README documents, rather than a folder dedicated only to notes.
To ignore a specific folder, right click the folder name in the folders panel on the left, and choose “Ignore folder” from the context menu.
To unignore the folder, visit Preferences > Advanced
, and press the ‘remove’ button for that specific folder.
If you’re comfortable with regular expressions, you can also ignore folders matching a specific name or pattern globally.
To do so, add a new pattern in the Ignored folder patterns field.
This pattern is treated as a case-insensitive regular expression, and matched against the folder name (not the entire path).
Some examples:
^node_modules$
: Ignore any folder named exactly “node_modules”-private$
: Ignore any folder whose name ends in “-private”^2021
: Ignore any folder beginning with “2021”^\.
: Ignore any folder beginning with a periodPreviously, Deepdwn ignored all folders beginning with a period. With this update, this default filter is now user configurable and can be removed or modified as needed.
Use the Ctrl / shortcut when editing to comment out the current line or selected line, so that it will be ignored when previewing or exporting.
In fenced code blocks, Deepdwn will also try to use the correct comment syntax for the code language if possible.
The document template list has been updated to allow templates in multiple formats.
Templates which have been starred will always be used when creating new documents for that specific format only.
Also, a button to create a new template is now available for each format. This was only available previously if you had no saved templates in your library.
...
when too large for their containers, which makes more actual text visible when there is only room for a few charactersThere are a lot of moving parts in this update, and bugs happen. If you run into trouble, please drop a post in the support forum and I’ll try to get it solved.