It's deprecated, so no new features will be coming to it, but you're welcome to keep using it until we port over the remaining features if it works for you.

Could Dendron "ever" be kinda integrated with "external api functionality"? I don't do webdev, but I've had this idea, where we could fetch music chart info, into some sort of webpage (which Dendron can kinda do webpages). And so basically imagine Dendron here as the skeleton. And this sort of music charts project, is kinda a knowledge management sort of application. Cause it could go from just basic charts, all the way to info on who wrote the music, how it happened, etc. It's like an extensive wiki, that's updated dynamically and not manually. (But with an option to also go in and do it manually, say for some personalized descriptions of artists). Can this be done? Who can I talk to ab this? Anyone interested? We can at least start with basic functionality of fetching charts, first from Spotify, then Apple, etc. And once more people are interested they can develop the rest.

Also

A good point here, is that it could be a LOT of knowledge, and be hard to navigate. So now if we consider that Dendron is geared to navigating, hard to navigate large knowledge - this is why it made sense to me to think of it from a Dendron pov

Cause I also can't think of it any other way

Not a webdev

Hey just for my understanding, do you want to show external Information inside a Dendron note? Like you have the Hierarchy like in your screenshot, but in the Note for

Charts.Deezer.Monthly.Worldwide.2020.01.

you want to be able to show the actual Chart from where ever that is. This should already be possible, will need to test it if dendron Allows

raw Html Iframes

for the preview / publishing to be inside of notes. Ahhh.... stop reread your message, something like that could be done per Pods to import the charts, creating the Hierarchy. Like one Pod to import the Charts from Deezer for month X, running that pod once a month would add the charts of the last month to it. Since these Charts are

static

they don't change. But it could generate a Scaffold for live Charts for the Genres as example which would just link or embed the Corresponding Charts. But this would not allow for the needed editing to Link an an Artist in the Live Charts to the Notes about the Artist. This would be possible for the monthly Charts since these are Static and could be analysed to create the needed links towards the Notes about Artist’s or Albums. Interesting Idea overall.

You could use Dendron to generate the

/docs

folder for the project (How It Works, etc.) and the

README.md

file of the project's repository. But aside from that, you'd use code (JS, Python, etc) that calls API's, returns .json, then builds the website on a schedule. Example: Every 60mins --> Azure Function calls API's --> Response written to DB (or directly to GitHub!) --> GitHub Action builds index.html --> Done

I like this method. Especially using Python and Jinja2 templates. Basically your own serverless static site generator.

Hi All, loving dendron so far. I've been using the daily journal as a way of capturing meeting minutes. But now they are kind of locked into individual files. Is there any way to make them... scrollable in a single view or searchable-en-group?

you may want to look at https://wiki.dendron.so/notes/f1af56bb-db27-47ae-8406-61a98de6c78c/#wildcard-link-reference These could help

Anybody use Dendron with editors other than VSCode? I live a good portion of my life in the terminal, and I don't always want to "context switch" to VSCode

This thread might give you some ideas: There's good reason to believe that down the line, when we can do more with the LSP, integration with other editors can go much further. For now, fuzzy-finding lookup and wiki-link navigation is workable, and most of what I need for daily, ordinary use

Oh very cool! Yea fuzzy find, and maybe making new scratch notes + daily notes would be awesome for me

Thank you!

Exactly. I need it for static charts. The user would only ever request info from our website, not ever making api calls to any of the services. A lot like us just sending monthly requests (for example), for such and such new charts. But I was wondering what the "better" tool for this would be. Like.. idk. The guy below you @User mentioned that "aside from that" you could use smth else, with his "example:". Is it obvious that his idea is better? Cause like I can't tell as a non developer. I'll rewrite again here the main functions, I think we need: 1. Charts monthly. Hierarchical view (or a choice of several styles of hierarchical view, if we ever want to redo the hierarchy somehow, to test out if something else is more intuitive. to navigate) 1.2. Possibly some visual way of navigating (open to suggestions of what this could be. No idea what to do here. And I guess this obviously requires some programming language "integration", not sure if Dendron has that, or even if it does - if it's the right tool to use) 2. Search bar, and tagging of items. Combining tags to reveal which items, and parents have these tags associated with them the most. Like a % of how much of a match it is to your request (not necessarily as a %, but just to get across the idea of ranking the best to worst matches) 3. idk

If you just need to re-generate things monthly, you could write some custom code that looks up the required information and then re-writes the notes, then rebuild the website. You could then automate this with something like Github actions so it will keep automatically updating every month

If I moved to one of the new Apple computers with the ARM-based M1 chip, will Dendron still work? Visual Studio appears to (with issues last time I looked), but I'd hate to loose Dendron.

Yup, there are even Dendron developers with M1 macbooks. (Well, at least 1 I know of)

Excellent, thanks. Another piece of software to cross of the list !

What is the difference between a code workspace and a native workspace? I read this (https://wiki.dendron.so/notes/c4cf5519-f7c2-4a23-b93b-1c9a02880f6b), but I still don't understand when I should prefer one over the other.

My understanding so far is that a code workspace is like another folder with Dendron-specific files that gets created within some VSCode workspace.

I was confused as well in the beginning (I think the docs could be clearar). A code workspace is a VSCode workspace dedicated to dendron. In VSCode you can save workspace settings in a .code-workspace file. Dendron can create a VSCode workspace and save the config to a file named dendron.code-workspace

But what is the difference between this and just editing the VSCode workspace file to add a folder path to some Dendron folder elsewhere on the machine? Is that the same?

A "native" workspace when the dendron extension is active in any normal vscode workspace

I think this is what I am interested in. Because, up until now I was adding a

<name>.code-workspace

to all my projects just to be able to access the Dendron workspace from the same VSCode instance.

json
{
    "folders": [
        {
            "path": "."
        },
        {
            "path": "path/to/my/dendron/notes"
        }
    ],

    "settings": {}
}

@User Suppose you have a project independent of Dendron (i.e., a separate VSCode workspace). Then, suppose you have a Dendron workspace somewhere on your machine (i.e.,

dendron.code-workspace

). What would you do to be able to use the Lookup Bar in the VSCode workspace, assuming that the Dendron extension is globally enabled?

I don't think Dendron works that way. I tried various stuff and there seems to be some magic naming/path hierachy that the dendron looks for in order to activate. I believe dendron activates on a workspace level, i.e. not globally across VSCode workspaces. From the docs the idea is to either have workspaces that are only used for dendron, or if you want to use Dendron inside a project, you initialize a dendron workspace inside your existing project ("native workspace"). There are probably ways to make what you want work, but that is for somebody that knows Dendron better than me to answer 🙂

Well, if I just add to my VSCode workspace the path to the Dendron workspace (i.e., "path": "path/to/my/dendron/notes") then open a Dendron note and reload the window, Dendron gets activated and the look-up bar works.

Ah, thanks that's good to know!