obsidian-api VS PixiJS

I really like that you commit to keep this stable and open.

Do you plan to make the TypeScript definition part of this new site?

https://github.com/obsidianmd/obsidian-api/blob/master/canva...

For me it's easier to read TS format.

The Canvas feature is a custom file format, but they published the format here: https://github.com/obsidianmd/obsidian-api/blob/master/canva...

If Obsidian goes under or you want to migrate at least your data isn't lost.

Obsidian is closed source so you won't be infringing their copyright by incorrectly getting/copying their code within your code. I don't believe they have any software patents (too small a company), and the canvas data format is available under MIT license (https://github.com/obsidianmd/obsidian-api/blob/master/canvas.d.ts). Even if you decided to reproduce their plugin APIs (so that existing Obsidian plugins could be reused with your software), you'd be fine per https://en.wikipedia.org/wiki/Google_LLC_v._Oracle_America,_Inc. (but their API definition is under MIT license anyway: https://github.com/obsidianmd/obsidian-api/tree/master)

I would start with with the obsidian api docs and the obsidian plugin docs then feed it into a gpt document loader and ask gpt the same thing you asked here. Obsidian offers a couple different “talk to your notes” plugins using gpt (all you need is an open ai api key) if you’re looking for a streamlined “ai document loader” you could just copy and paste the info into a new note once you have the plugin installed.

In any event, there are no CLI flags to do that at the moment. The canvas format is very new, and not part of the standard markdown format. There is a public specification for it, but it's up to developers to make applications supporting it.

Canvas has been an open standard since its release.

As far as I know, any API that can be used by end users and plugin developers (as described in the previous post) is considered public. You can find the API repo here and definitions in this file.

The .canvas format is a simple JSON-based format that is designed to be easy to parse. We've already seen several plugins leverage this and hope to see even more tools outside of Obsidian. You can see the spec here.

If you're into video game dev, then PixiJS is something you need to know about. It's a HTML5 game engine that provides a lightweight 2D library across all devices. This latest update has a new package structure, custom builds, graphics API overhaul, and lots more. You can read about all these changes in the PixiJS Migration Guide. Also big congrats to PixiJS for being part of the open source community for ten years now! 😮.

6. Pixi.js

https://pixijs.com/ and https://gsap.com/. All of the source code for my posts can be found at https://github.com/samwho/visualisations :)

For full web games (yeah, I come from the web, so I try to make my family proud), I will recommend PixiJS. It has great support for TypeScript and works very well with Vite. It's lighter than other game engines, so it's better for web games. But you will need to do a lot of things by yourself.

PixiJS (MIT/TypeScript) https://github.com/pixijs/pixijs

That approach works well for what I was trying to archive but I am planning on adding more functionality into the website. Hence in this article, let me rebuild the project using Pixi.js and it’s React binding, React Pixi.

https://openarena.live/

There's also a bunch of Javascript game engines: https://github.com/collections/javascript-game-engines

Of those, BabylonJS seems pretty powerful for 3D: https://www.babylonjs.com/games/

Or PixiJS for 2D: https://pixijs.com/

https://pixijs.com/ is more of a 2D rendering framework, but powerful and very fast