Beta: Markdown and Form Code

[JochenL]

I have been working on two new features recently: Markdown & Form Code.

These features are in Beta stage, please use carefully and only on non-critical log entries!

Markdown

To activate markdown for an entry, start the entry with ?MD and use the CommonMark markdown syntax: https://commonmark.org/help/

Example:

?MD

# H1
**bold**

[CommonMark](https://commonmark.org/help/)

As I expected, MD isn't really working that great (yet) with auto-tagging, but see for yourself.

Form Code

To activate form code for an entry, start the entry with ?FC and use this custom syntax:

[ ] --> unchecked checkbox
[x] --> checked checkbox

[[]] --> empty single-line input field
[[some text]] --> filled single-line input field

[[[]]] --> empty multi-line input field
[[[Some Text
with line breaks
]]] --> filled multi-line input field

Example:

?FC
[x]
[[single-line]]
[[[multi-line]]]

Changing the value (and in case of input fields leaving the field) will trigger a background edit and save of that entry.
Currently, this sometimes does not work which seems to be an issue of focus and browser behavior.

 

[JochenL]

@ELF suggested a way for using Form Code:

{b|Damage}: [x][x][x][x][x][x][x][ ][ ][ ]

 

[ELF]

@JochenL, how do you see the status of the form field tagging? Are you happy enough with it so that it will become a permanent, non-beta feature?

Asking because it would be great with templates.

 

[Mjsohm]

This forum reply provides regular formatting options . I can even simply add a picture: or a table:

Initiative Tracker
Character Name	AC	HP
Goober Vanwinkle	15	35

I just don't understand why it is not a priority to provide simple input formatting in the campaign logger. I will simply never use this product regularly until it is not required to physically type out extra keystrokes, any mistake of which renders the content a jumble of nonsensensical slashes and brackets. Sorry guys. Great concept. The tagging idea is genius, but I can't imagine non programming types to be interested in this and you may be missing an entire market.

This simple reply took 5 minutes. I need a cheat sheet and then at least 10 minutes of trial and error in the desperate hope it comes out looking presentable. Please consider this for a near future feature add, beta or otherwise.

Map:

 

[JohnnFour]

Thanks for the feedback!

It's especially tricky on mobile keyboards.

It's definitely something we're looking at.

Cheers,
Johnn

 

[nhadfield]

I tried to use the multi-line input field and it works well except the formatting to make things bold, etc don't seem to work in the box

I have been working on two new features recently: Markdown & Form Code.

These features are in Beta stage, please use carefully and only on non-critical log entries!

Markdown

To activate markdown for an entry, start the entry with ?MD and use the CommonMark markdown syntax: https://commonmark.org/help/

Example:

?MD

# H1
**bold**

[CommonMark](https://commonmark.org/help/)

As I expected, MD isn't really working that great (yet) with auto-tagging, but see for yourself.

Form Code

To activate form code for an entry, start the entry with ?FC and use this custom syntax:

[ ] --> unchecked checkbox
[x] --> checked checkbox

[[]] --> empty single-line input field
[[some text]] --> filled single-line input field

[[[]]] --> empty multi-line input field
[[[Some Text
with line breaks
]]] --> filled multi-line input field

Example:

?FC
[x]
[[single-line]]
[[[multi-line]]]

Changing the value (and in case of input fields leaving the field) will trigger a background edit and save of that entry.
Currently, this sometimes does not work which seems to be an issue of focus and browser behavior.

 

[JochenL]

I tried to use the multi-line input field and it works well except the formatting to make things bold, etc don't seem to work in the box

You are right. I need to think about that.