yep 🙂 https://wiki.dendron.so/notes/c160ddce-edec-4f6e-841b-418d6030fa37.html

also: https://wiki.dendron.so/notes/32cdd4aa-d9f6-4582-8d0c-07f64a00299b.html

That's exactly what I was looking for, thanks 🙂

let see if my code worth something 😆

What I really miss is some powerful functions for creating new notes more dynamic.. Example: * Using a hotkey to create a new note from a vscode template * Display a dropdown of existing project.*.journal namespaces, where * is what I want in the dropdown so I can pick which project I want a new journal on * Create a new journal in a specific vault * populate new note with output of a command I guess many of these things might belong to what schemas can provide.. I'm not sure if hotkey support is easy to make dynamic. A hotkey to trigger a schema might be possible maybe?

Maybe I should write an issue/feature-request per thing instead...? 🙂 And we can discuss them separate

thanks for the suggestions. dendron currently has two mechanisms of extension: pods and hooks. pods let you import/export and hooks let you add custom logic during certain lifecycle events. i'm thinking of consolidating this all into

plugins

a plugin can be a

pod

, a

command

, or a

hook

. a command can have a keyboard shortcut, have access to

lookup

and full control of the output. will write an rfc for this soon but let me know if this would cover your use cases

fwiw: Pods doesn't convey to me 'import/export' I think unifying under plugins makes sense, and then you have ETL plugins and lifecycle plugins

I'm pondering how to wrap my head around that: at this point, I have a bunch of scripts for synchronizing my data with a realm database. However, someday it is possible that I would like to share this in the form of a ... plugin (/pod|command|hook). Well... it is not exactly a pod, except when it initalizes the database and sends off all notes in one go the first time; it has hook*s* (not just one) for detecting changes; not sure about a command...

@User - a realm db? Interesting. I'd be interested in knowing how/and why you're doing that?

I'm playing with two concepts that I miss from Dendron: fragments and entities. Fragments are small pieces of text attached to a tag and are meant to let me highlights parts of my daily braindump that relate to my different projects or favorite introspection subjects. Entities are mostly for my dream reporting project: people / places / themes that come up in my dreams

My goal is to be able to visualize correlations between my daily activities & thoughts and the dream patterns that ensue

happy to share what I'm doing, just not very polished at this point

For that use case, we can think of a plugin being able to have multiple contribution points. So in your case, it would register a pod (to export to realm), and multiple hooks (to do sync). It's the same model VSCode uses for extensions - we might adopt it for plugins

i think there's more value showing off a work in progress then something that is finished. you get the ability to gather feedback and make meaningful changes. this is why iteration is one of our core values -> https://handbook.dendron.so/notes/b89ba854-72fb-4ebc-a8a0-55960b89e9dc.html#iteration

right, I will try to share some code as soon as it's at least doing something

I think the second bullet is pretty doable today. Not a drop-down but I use the lookup to find the meeting of a particular customer

cust.customerName.meet

and then I have a keybinding to create a journal note from the current note. In my view os very similar

I think that's great. Opening a window to plugins is the way people start building very good things. That's what happened with obsidian

Hey everyone! For anyone interested in the progress on the graph redesign, I’ve put together an initial design document at https://wiki.dendron.so/notes/6e87249b-358f-4f4b-8049-dff6e6a8463b.html. If you have any feedback, feel free to join the GitHub Discussion at https://github.com/dendronhq/dendron/discussions/615

Thanks for that, will probably later today write some questions concerning some of the decisions to better understand why they where made.

Sounds great - I aimed to synthesize a lot of different areas of information, so I’d love to talk and refine it some more

And I'm done https://github.com/dendronhq/dendron/discussions/615#discussioncomment-771235

Is there any branch already on progress for it? Would be interested to check that out

Nothing with enough progress to be of note right now, but I'll give you a ping when there's some notable progress - I'll be working in the `feature-graph`branch (https://github.com/dendronhq/dendron/tree/feature-graph)

Hi, while doing setup after running

yarn bootstrap: build

command getting this error: Can anyone help with this? lerna info Executing command in 1 package: "yarn run build" lerna ERR! yarn run build exited 1 in '@dendronhq/dendron-next-server' lerna ERR! yarn run build stdout: $ yarn build:prod $ env CDN_BUILD=1 STAGE=prod next build && next export lerna ERR! yarn run build stderr: warning package.json: License should be a valid SPDX license expression warning package.json: "dependencies" has dependency "@types/react" with range "^17.0.5" that collides with a dependency in "devDependencies" of the same name with version "^16.9.50" warning package.json: License should be a valid SPDX license expression warning package.json: "dependencies" has dependency "@types/react" with range 'env' is not recognized as an internal or external command, operable program or batch file. error Command failed with exit code 1. lerna ERR! yarn run build exited 1 in '@dendronhq/dendron-next-server' error Command failed with exit code 1

Looks like you are missing the

env

command, what platform are you on?

windows

Where did you install node/yarn from?

npm node v14