npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

joplin-plugin-code-section

v1.0.6

Published

Inserts a piece of code from code source

Downloads

23

Readme

Code Section Joplin Plugin

This plug-in displays a piece of source code. It reads this source code from a source file which is appended to the note. The code is selected by supporting a code definition inside a code definition block.

The code definition looks as follows:

```codesection
{
"lang": "python",
"src": "CODE-SOURCE-APPENDIX",
"begin": 1,
"end": 50,
"expandTabs": true,
"tabSize": 4,
"lineNumbers": false,
}
```

Several entries can be omitted and will be replaced by their defaults. The source language and the source itself are mandatory.

The inserted code will be displayed using the default renderer for that language including syntax highlighting.

This could look like this:

Python Source Code

Procedure

  1. Append a code source to the note
  2. Immediately following it add a codesection describing the code to be displayed
  3. The description has the shape of a JSON string
  4. The "src" attribute identifies the code source (its id followed by extension)
  5. Alternatively you could copy and paste the code insertion into the quotes of src

Problems

  1. ~~The resource folder is not recognized after the start of Joplin. Workaround: Invoke the settings and then leave them~~
  2. Only local sources in the resource folder can be displayed, no web content
  3. The plugin uses synchroneous file access to read the source, no asynchroneous access

Release Notes

1.0.4

  • Fixed the bug where resource folder was not recognized. Workaround is no longer needed (see Problems 1.).

1.0.5

  • Added a context menu command to insert a template of a code section
  • Added a few properties to the code section description:
    • scale: a scale factor in percent as 80% or absolute font size
    • spacing: the line spacing, default is 130% of the font size
    • height: the height of the code section window, may be "auto", "fill", a value in pixels ("400px") or a factor in percent relating to the window height

1.0.6

  • Changed architecture of the plugin
  • Code Sections are printed now with export to pdf