Joplin-vscode-plugin roadmap

I'm really sorry, I wasn't able to test it successfully, I don't know what went wrong.
My procedure is as follows.

  1. Upgrade joplin to 2.88, upgrade vscode to 1.67.1
  2. Install the joplin-vscode-plugin0.7.9 you gave in vscode
  3. Use the excalidraw in vscode to draw a diagram and save it as SVG on the desktop
  4. Drag this SVG diagram into joplin's test notes
  5. open this test note in vscode, ctrl+mouse click on the attachment
    But there is no response. There is no prompt.
    I think it should be a wrong operation, but I don't know where the problem is, I hope to be corrected. Or you can write a simple tutorial if it is convenient, thanks.
    VeryCapture_20220611230815

Try the shortcut keys ctrl+j, ctrl+l to list the resource list of the current note, and then select one to edit it, this error that occurs from time to time is the main reason why I released 0.7.8

can also be triggered by entering the command joplin show resources in vscode

Also, it looks like your markdown preview is not showing the image correctly, refer to the faq: FAQ | Joplin Utils

Yes, it's great, the preview problem is solved, the solution is to un-disable the upper right corner in the previous illustration.
But the problem with opening with excalidraw I still can't figure out.
Clicking still doesn't jump to the interface of excalidraw.
Rest early, I will test again tomorrow if I have time.

VeryCapture_20220611235311

I added some logs and rebuild, can you reinstall this version and try again?

  1. Open note
  2. Use ctrl+j,ctrl+l to display the resource list
  3. Select Open Resource
  4. Enter the command joplinNote.showLogFileDir to open the log resource directory
  5. Send me the two log files as a zip

joplin-vscode-plugin-0.7.9.vsix (761.1 KB)

Looks really cool! Could work well until proper drawing support is added to Joplin itself. Thanks!

1 Like

0.7.9 has been synced to the vscode extension store

1 Like

Release 0.7.10, mainly to fix the inconsistency with the behavior of joplin in external editors when there is a first-level title in the note content, related issues: [Bug]: Note name breaking · Issue #47 · rxliuli/joplin-utils · GitHub

Released 0.7.11, glad someone is using it and asking questions

2 Likes

Released 0.7.13

3 Likes

Pre Released 0.8.0

With the development of vscode itself, the previous drag and drop api is now supported, this major version update resolves 3 known issues

  1. Drag and drop the file into the note file
  2. Drag and drop notes and notebooks from the sidebar
  3. Drag and drop notes from the sidebar into the text to create citations

related issues

This version requires vscode version ^1.71.0, it is recommended to update to the latest version, not yet published to the vscode plugin store, please manually download vsx to install

  • feat: support dragging the sidebar notes into the text
    Drag and drop notes to body
  • refactor: rename FolderOrNote => JoplinTreeItem
  • feat: remove cut and paste commands that are no longer needed
  • feat: implement the drag and drop function of the sidebar
    Notes and Table of Contents Drag and Drop
  • feat: support drag and drop file upload from file manager to joplin
    Drag and drop files to notes
3 Likes

Pre Released 0.8.1

  • fix: restore cut and paste function
  • chore: replace esno => tsx
  • feat: register markdown languages together to avoid processing md files of non-joplin notes
  • feat: Change the log storage location to avoid the problem that the vscode log directory changes frequently and the logs are not concentrated in one directory, and save possible error messages to the log when the command execution fails
  • chore: update engines.vscode

Pre Release 0.8.2

  • fix: fix the bug that the title is not set correctly when creating an attachment
  • chore: build.js => build.ts

ref: Release joplin-vscode-plugin@0.8.2 · rxliuli/joplin-utils · GitHub

1 Like

joplin-vscode-plugin is now published to the open-vsx service, which is used by the open source alternative to vscode, the plugin can now be seen from here

Thanks to publish-extensions

4 Likes

Published to the vscode addon store, requires vscode@^1.71.0

1 Like

Pre Released 0.9.0

  • feat: support three new commands, show currently referenced note, show referenced note, insert note link
    mpte links
  • feat: support audio and video display in joplin
    image
  • feat: upgrade joplin-api, no longer rely on node-fetch/form-data, and fill in by itself

Thanks to the update of vscode@1.72, now vscode can view audio and video again, but there are still some problems, including mp4 video without sound, the progress bar cannot be dragged and so on, waiting for the follow-up vscode to solve, ref: https://code.visualstudio.com/updates/v1_72#_builtin-preview-for-some-audio-and-video-files

ref: https://github.com/rxliuli/joplin-utils/releases/tag/joplin-vscode-plugin%400.9.0

3 Likes

Released 0.9.1, sync to vscode marketplace

  • fix: fix the issue that uploading a file without specifying a filename will cause a mime error
  • feat: update dependency nodejs to 18, no longer include fetch/FormData polyfill

ref: Release joplin-vscode-plugin@0.9.1 · rxliuli/joplin-utils · GitHub

Now, after 47 versions, I think the integration of joplin in vscode is basically complete, and it should only require some maintenance, so 1.0.0 is released


ref: Release joplin-vscode-plugin@1.0.0 · rxliuli/joplin-utils · GitHub

9 Likes

Excellent plugin! Belongs to my daily drivers!

1 Like

Released 1.0.1


By the way, joplin-api released 0.5.0 with support for esm/cjs (esm first)
ref: joplin-api - npm

At the same time, the documentation is regenerated, and now it looks a little more comfortable

3 Likes

The number of installations exceeded 10k ヾ(≧▽≦*)o

6 Likes