preface

It’s been 5 months since the last update (V1.6.2), so sorry for the late 2.0 release. The original plan was to release version 2.0 in December 2018 (PicGo’s first anniversary), but unfortunately, it was during the graduate study period and took a lot of time, so the big release came late. But starting with this release, the plugin system is officially supported, and PicGo can be an extremely efficient tool if you can imagine.

In addition to the release of PicGo 2.0 ontology, picGo-Core (the underlying layer of PicGo 2.0, supporting CLI and API calls), as well as VSCode PicGo plug-in VS-PicGo, etc.

Plug-in system

The underlying Core of PicGo is actually Picgo-core. This core is primarily a process system. (It supports global installation in Node.js, uploading image files from the command line, and calling the API from the Node.js project.)

The picgo-core upload process is as follows:

Input is usually a file path. Transformer reads information, Uploader Uploader Uploader Uploader Uploader Uploader Uploader, and finally Output results. The plug-in can access three life cycles (beforeTransform, beforeUpload, afterUpload) and two parts (Transformer and Uploader).

In other words, if you write the right Uploader, you can upload it to different platforms. If you have written the right Transformer, you can download the file through the URL before uploading it to Uploader and so on.

Alternatively, if you don’t want to download PicGo electron, you can install PicGo via NPM for a quick one-click image upload experience from the command line.

PicGo gives GUI plug-ins some autonomy in addition to the Core functionality provided by PicGo-Core.

For example, plug-ins can have their own menu items:

In addition to taking over the upload process provided by PicGo-Core, the GUI plug-in can also use PicGo guiApi interface to implement some functions in the plug-in page that were previously impossible through the upload area:

For example, you can open an InputBox to get input from the user:

You can perform other functions (other than just uploading files) by opening a path:

You can even upload directly from the plug-in panel by calling the API.

In addition, the plugin can listen to the event of photo deletion in the album:

This feature allows you to write a plug-in that synchronizes photos from the album and removes them from the remote storage.

Now I can even think of some interesting plug-ins that the plugin system can make.

Such as:

  1. In conjunction with GitHub’s new free private repository, PicGo’s photo albums and profiles can be synced through plug-ins.
  2. TinyPng and other tools to achieve the image before uploading thin. (It may affect the upload speed though.)
  3. With some Canvas tools, you can watermark images before uploading them.
  4. By specifying a folder, the image address in markdown inside the folder is transferred.
  5. And so on.

I hope this plugin system can bring more power to PicGo, and I hope it can become your ultimate efficiency tool.

Note that to use the PicGo 2.0 plug-in system, you need to install it firstNode.jsEnvironment, because PicGo’s plug-in installation dependsnpm.

2.0 Other updates

In addition to the plug-in system described above, PicGo 2.0 also has the following updates:

  • Some map uploads failed after the underlying refactoringbase64Value will increase the speed quite a bit. Such asSM.MSBed etc. And it’s already passedbase64The speed of the uploaded graph bed remains unchanged.
  • Add some configuration items, such as open profile (including the list of uploaded images), mini window top, agent Settings, etc.
  • In the album page you can choose to copy the link format, no longer have to upload the page to change.
  • Add fade in and out animations for different page switches.
  • MacOS version color matching has been slightly updated. (Windows version color matching update Fluent Design effect is expected to be available in version 2.1)
  • The electron version has been updated from 1.8->4.0 with faster startup and better performance.

Bug Fixed

  • Fixed: Wrong location when opening details window on macOS with multiple screens.
  • Fixed: Multiple image uploads with consistent renaming.
  • Fixed: Dragging an image into the software will automatically open the image inside the software.
  • Fixed: A bug where a renamed window appears in the center of the screen instead of following the main window.

The PicGo plugin for VSCode is vS-Picgo

Shortly after picgo-core was released, someone wrote a VSCode version of PicGo plug-in based on the picgo-core API. It is also very convenient to use:

  • Upload screenshots

  • File browser Selects file upload

  • Enter the file path to upload

The configuration items are basically the same as those of PicGo’s graph bed. Search PicGo in the VSCode plugin bar to download, install and experience!

conclusion

PicGo supports macOS, Windows, Linux three platforms, open source free, beautiful interface, has been recognized by many friends. If you have any comments or suggestions about it, please feel free to point them out in Issues. If you like it, you might as well give it a star. If it really helps you, why not buy me a cup of coffee (PicGo’s GitHub homepage has a sponsored QR code)?

Download: github.com/Molunerfinn…

For Windows users, download the. Exe file. For macOS users, download the. DMG file. AppImage file.

Happy uploading!