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() - More questions and answers

Browse source
This commit is contained in:
Tal Wrii 2025-01-07 21:05:23 +01:00
parent 0ef0d9f9f0
commit 0cc63bee5f
1 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
questions.md
View file

@ -28,5 +28,13 @@ Alternatively, you might start having enough code that you want a type system to
Or, you might start wanting to use lots of javascript libraries. At which point it might make more sense to switch over to a plugin.
# What is the difference between Plugin REPL and dataview and Templater?
In a sense all computers do is "proccess data". The input takes different forms. Some forms are more general like programming languages, some forms are far more specific like some checkboxes in settings. Dataview, Templater and Plugin REPL all allow the execution of arbitrary Javascript and give you some access to bits of the Obsidian plugin API.
Dataview and Templater have both mean "stretched" to do interesting things.
Dataview is nominally a query language for your pages - but people have added Javascript to it; it has access to an app object; and it has the ability to render code. Templater was additinally intended do templating, but there is a "start up" that does not render and people use templtaes to run code.
The difference is how the code is run and what is made easy. Plugin REPL is good if you just want to run some code now once. It is good if you want to define commands and bind them to keys. It is good if you want your code to be in one place. It is good if you want to debug and adapt code. It is good if you want to do straight forward things in the editor.
Dataview is good if you want some code in a page and renders something. Templater is good if you want a template.