logseq-simpread
logseq-simpread copied to clipboard
The official Logseq plugin of SimpRead.
The official Logseq plugin of SimpRead.
https://user-images.githubusercontent.com/20166026/179386714-38d2c5e0-690f-4df4-82b3-d16108350fc1.mp4
h2. Usage
注意:本页面不包含使用教程,请前往简悦的 "这条 discussion":https://github.com/Kenshin/simpread/discussions/4220 查看。
Currently the plugin contains only one function: triggering the reading list panel.
To use this plugin, you need:
- SimpRead, the browser extension installed
- A premium account of SimpRead activated
- Official 简悦 · 同步助手 installed, version >= 1.1.0
- Knowledge base configured
- Automation configured and enabled
- Markdown 模板辅助增强插件 installed and template configured
The template used in the demo video is under @templates@.
h2. Publishing
h3. Packaging
The code is written in a single vanilla HTML file. The only dependency is @lsplugin.user.min.js@. Just replace the one loaded from CDN with a local copy.
h3. Logo
Note that some objects are hidden. You can "mamage them with the Selection pane":https://support.microsoft.com/en-us/office/manage-objects-with-the-selection-pane-a6b2fd3e-d769-46c1-9b9c-b94e04a72550.
To replicate @logo.svg@, please follow the instructions below:
Open the XML file with PowerPoint
Select all elements in the slide (Ctrl+A)
Group them (Ctrl+G)
Paste the combination in SVG format (Ctrl+Alt+V)
Right click, and save that SVG as a picture
h2. Known issues
h3. @top.document@
@top.document@ may be removed by Logseq.
h3. Color of the toolbar icon looks bad in some themes
Currently the toolbar icon is in SVG format, which requires @.st1{stroke: #xxxxxx}@ to control its color. However, most buttons on the toolbar is in icon fonts, making unofficial themes like Bear use another approach to control icon colors.
h3. Scroll bar
The style of the scroll bar of the iframe does not match the official one's.
h3. Hardcoded URL
The port of simpread-sync is hardcoded to @7026@. A configuration UI will be added in the future.
h2. Roadmap
A new plugin API based highlights synchronization will be added in the future. Since Logseq plugins has no access to Node environment, it is impossible to implement the API in the same way as using Local REST API in Obsidian.