You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 9, 2018. It is now read-only.
This issue belongs to the create / edit post epic: #5.
If possible, we should use the exact same Markdown implementation that Ghost uses. Ghost uses Showdown.js, which we might want to use, but it's likely to be quite slow on large blog posts. I'll try the options below first.
There are a couple of possibilities for a native Markdown implementation here:
anddown: Pros: fast (NDK), has support for fenced code blocks, pre-built libs available. Cons: generates raw HTML, which makes it harder to use a native TextView with Spannables.
bypass: Pros: fast (NDK), partial fenced code block support, used and co-maintained for Android by Trello, produces native Spannables directly, which means it'll be even faster and easier on the eyes than anddown's output. Cons: gfm support is buggy.
pegdown: Pros: supports fenced code blocks (among many other extensions). Cons: apparently does not work on Android and / or is slow.
At this point, anddownbypass seems like the best option overall.
The text was updated successfully, but these errors were encountered:
Note for posterity: Quill switched to Showdown.js long ago and renders the output via a WebView for 100% compatibility with Ghost (footnotes, fenced code blocks, etc). It's a bit slow to render initially (~1 sec delay), but quite acceptable nonetheless.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue belongs to the create / edit post epic: #5.
If possible, we should use the exact same Markdown implementation that Ghost uses.Ghost uses Showdown.js, which we might want to use, but it's likely to be quite slow on large blog posts. I'll try the options below first.There are a couple of possibilities for a native Markdown implementation here:
TextView
withSpannable
s.Spannable
s directly, which means it'll be even faster and easier on the eyes than anddown's output. Cons: gfm support is buggy.At this point,
anddownbypass seems like the best option overall.The text was updated successfully, but these errors were encountered: