From c4881d5129f73fb235a29f04f49f0f9670ec1604 Mon Sep 17 00:00:00 2001 From: Tal Wrii Date: Mon, 30 Dec 2024 01:07:11 +0100 Subject: [PATCH] doc() questions and answers --- README.md | 3 +++ questions.md | 4 ++++ 2 files changed, 7 insertions(+) create mode 100644 questions.md diff --git a/README.md b/README.md index 4fd9422..5cdbc1f 100644 --- a/README.md +++ b/README.md @@ -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 diff --git a/questions.md b/questions.md new file mode 100644 index 0000000..e66489a --- /dev/null +++ b/questions.md @@ -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.