obsidian-plugin/talwrii_plugin-repl
1
0
Fork 0
mirror of https://github.com/talwrii/plugin-repl.git synced 2026-07-22 11:40:27 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

doc() questions and answers

Browse source
This commit is contained in:
Tal Wrii 2024-12-30 01:07:11 +01:00
parent a7f4a5cd1f
commit c4881d5129
2 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
README.md
View file

@ -132,6 +132,9 @@ I experimented with the [obsidian modules](https://github.com/polyipseity/obsidi
The approach I have used to getting access to modules when hacking on a new plugin is to create a new plugin and half that plugin set `self.MODULE = MODULE` on load. You can then access this self open from the repl.
## Some questions and answers about plugin repl
[Questions and answers](questions.md)
## Alternatives and prior work
* You can [use plugins](https://docs.obsidian.md/Plugins/Getting+started/Build+a+plugin) to do the same things that you can do with plugin-repl but this tends to mean more code.
* [js-engine](https://github.com/mProjectsCode/obsidian-js-engine-plugin) lets you evaulate javascript code in code blocks. [Execute code](https://github.com/twibiral/obsidian-execute-code) gives you code blocks in multiple languages. Neither give you access to obsidian objects to control obsidiate

4
questions.md Normal file
View file

@ -0,0 +1,4 @@
# Isn't this just reimplementing the Obsidian plugin API badly?
*Yes*, but it is reimplementing a subset that it most useful for
rapid (if ugly) procedural development so that you can get things done.