1
0
mirror of https://github.com/laurent22/joplin.git synced 2024-12-12 08:54:00 +02:00
joplin/ReactNativeClient/lib/joplin-renderer
2020-03-06 18:57:46 +00:00
..
assets Desktop, Mobile: Fixes #2638: Improved Mermaid rendering on small viewports 2020-03-04 01:55:48 +00:00
MdToHtml All: Fixes #2667: Fixed sanitize function so that it does not break HTML 2020-03-06 00:54:21 +00:00
tests Moved the Joplin renderer back to the main repository to make development easier 2020-01-30 21:05:23 +00:00
Tools Desktop, Mobile: Fixes #2477: Add new Katex fonts to improve rendering (#2478) 2020-02-11 22:53:12 +00:00
vendor Moved the Joplin renderer back to the main repository to make development easier 2020-01-30 21:05:23 +00:00
.gitignore Moved the Joplin renderer back to the main repository to make development easier 2020-01-30 21:05:23 +00:00
assetsToHeaders.js Desktop, Mobile: Fixes #2357: Fix slow rendering and memory leak issues with Katex notes 2020-02-08 11:11:04 +00:00
defaultNoteStyle.js Moved the Joplin renderer back to the main repository to make development easier 2020-01-30 21:05:23 +00:00
HtmlToHtml.js All: Security: Fixed potential Arbitrary File Read via XSS 2020-02-13 23:59:23 +00:00
htmlUtils.js All: Regression: Fixed issue with style embeded in notes 2020-03-06 18:22:40 +00:00
index.js Moved the Joplin renderer back to the main repository to make development easier 2020-01-30 21:05:23 +00:00
MarkupToHtml.js All: Security: Fixed potential Arbitrary File Read via XSS 2020-02-13 23:59:23 +00:00
MdToHtml.js All: Fixes #2667: Fixed sanitize function so that it does not break HTML 2020-03-06 00:54:21 +00:00
noteStyle.js All: Fixed top margin issue on note rendering 2020-03-06 18:57:46 +00:00
package-lock.json Desktop, Mobile: Resolves #2001: Added Mermaid diagrams support 2020-02-11 22:28:43 +00:00
package.json All: Fixes #2667: Fixed sanitize function so that it does not break HTML 2020-03-06 00:54:21 +00:00
pathUtils.js Moved the Joplin renderer back to the main repository to make development easier 2020-01-30 21:05:23 +00:00
publish.sh Moved the Joplin renderer back to the main repository to make development easier 2020-01-30 21:05:23 +00:00
README.md Desktop, Mobile: Fixes #2374: Fix rendering of certain letters in Katex. Fixed printing when note contains Katex code 2020-02-08 00:15:56 +00:00
stringUtils.js Moved the Joplin renderer back to the main repository to make development easier 2020-01-30 21:05:23 +00:00
urlUtils.js Moved the Joplin renderer back to the main repository to make development easier 2020-01-30 21:05:23 +00:00
utils.js Moved the Joplin renderer back to the main repository to make development easier 2020-01-30 21:05:23 +00:00

Joplin Renderer

This is the renderer used by Joplin to render notes in Markdown or HTML format.

Installation

npm i -s joplin-renderer

Certain plugins require additional assets like CSS, fonts, etc. These assets are in the /assets directory and should be copied to wherever the application can find them at runtime.

Usage

const { MarkupToHtml } = require('joplin-renderer');

const options = {};

// The notes are rendered using the provided theme. The supported theme properties are in `defaultNoteStyle.js`
// and this is what is used if no theme is provided. A `theme` object can be provided to override default theme
// properties.
const theme = {};

const markdown = "Testing `MarkupToHtml` renderer";

const markupToHtml = new MarkupToHtml(options);
const result = await markupToHtml.render(MarkupToHtml.MARKUP_LANGUAGE_MARKDOWN, markdown, theme, options);

console.info('HTML:', result.html);
console.info('Plugin assets:', result.pluginAssets);

When calling render(), an object with the following properties is returned:

  • html: The rendered HTML code
  • pluginAssets: The assets required by the plugins

The assets need to be loaded by the calling application. For example this is how they are loaded in the Joplin desktop application:

function loadPluginAssets(assets) {
	for (let i = 0; i < assets.length; i++) {
		const asset = assets[i];

		if (asset.mime === 'text/css') {
			const link = document.createElement('link');
			link.rel = 'stylesheet';
			link.href = 'pluginAssets/' + asset.name;
			document.getElementById('joplin-container-styleContainer').appendChild(link);
		}
	}
}

Development

### Adding asset files

A plugin (or rule) can have any number of assets, such as CSS or font files, associated with it. To add an asset to a plugin, follow these steps:

  • Add the file under /assets/PLUGIN_NAME/your-asset-file.css
  • Register this file within the plugin using context.pluginAssets[PLUGIN_NAME] = [{ name: 'your-asset-file.css' }]

See katex.js for an example of how this is done.

Adding inline CSS

A plugin can ask for some CSS to be included inline in the rendered HTML. This is convenient as it means no extra file needs to be packaged. Use this syntax to do this:

context.pluginAssets[PLUGIN_NAME] = [
	{
		inline: true,
		text: ".my-css { background-color: 'green' }",
		mime: 'text/css',
	},
];