armortools
component-model
armortools | component-model | |
---|---|---|
30 | 33 | |
3,061 | 828 | |
1.2% | 3.3% | |
9.5 | 8.2 | |
5 days ago | 6 days ago | |
TypeScript | Python | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
armortools
-
3D and 2D: Testing out my cross-platform graphics engine
I am glad people are working on it!!
Have you seen Kha by any chance? It has similar goals. I find it quite awesome, but it won't gain mass adoption for a bunch of reasons. https://github.com/Kode/Kha
Someone built an immediate mode renderer on top https://github.com/armory3d/zui, which is utilised by ArmorPaint https://armorpaint.org. I also use Zui for my own bespoke 2D game engine.
I find this tech and tooling really quite amazing (just look at how little source code Zui has) given just how small the ecosystem around it is. I think Kha really illustrates what can be achievable if the lower levels have robust but simple APIs, just exposing the bare minimum as a standard for others to build upon.
For the kind of project I work on (mostly 2d games), I think it would really awesome if your framework also supported low level audio, and a variety of inputs such as keyboard, mice, and gamepads. If it also had decent text rendering support it would basically be my dream library/framework.
-
Best practice workflow for importing objects from Blender to Unreal
A lot of people use Substance Painter (or other tools - thinking of trying out Armor Paint at some point) to make the textures separately after making the mesh and UVs in Blender. It's definitely possible to do texturing and so on within Blender as well, but I personally haven't found a good workflow for this yet for producing high-quality results.
- ArmorPaint | 3D PBR Texture Painting
- ArmorPaint and ArmorLab: Open-Source Alternative To Adobe Substance
-
ArmorPaint and ArmorLab: open-source alternative to Adobe Substance
This is the first large piece of (GUI) desktop software I've seen written in Haxe. Not that I've seen all software ever of course, just thought it was interesting.
Source: https://github.com/armory3d/armortools
-
[Question] Free (or cheap) texture painting program like Procreate but for windows? Basically something that allows for more artistic freedom.
May I suggest Armory Painter (https://armorpaint.org)
-
KDE and GNOME seek $100k to turn Flathub into a store for the Linux desktop
One of the best examples of this is Armorpaint an open source texture painting tool.
-
Texturing Programs
ArmorPaint - haven't used that one, but it looks promissing
- Armorpaint: Cross-Platform 3D PBR Texture Painting Software
component-model
-
Tree-shaking, the horticulturally misguided algorithm
I don't think that's a very good goal. Jettisoning the DOM means jettisoning accessibility and being able to leverage everything that the browser gives you out-of-the-box. You have to render to a canvas and build everything from scratch. I think Wasm is great for supplementing a JS app, not replacing it (e.g. using a Wasm module to do some calculations in a Worker). I like to use the right tool for the job, and trying to use something other than JS to build a web app just seems a little janky to me.
At one point, there was a Host Bindings proposal that would enable you to do DOM manipulation (it looks like it was archived and moved to the Component Model spec [1]). That would probably be the ideal way to avoid as much JS as possible. However, browser vendors have been heavily optimizing their JS runtimes, and in some cases, Wasm may actually be slower than JS.
I've been following Wasm's progress for several years, which has been slow, but steady. Ironically, I think the web is actually the worst place to use it. There's so much cool non-web stuff being done with it and I'm more interested to see where that goes.
[1] https://github.com/WebAssembly/component-model?tab=readme-ov...
-
3D and 2D: Testing out my cross-platform graphics engine
Well the great thing about WebAssembly is that you can port QT or anything else to be at a layer below -- thanks to WebAssembly Interface Types[0] and the Component Model specification that works underneath that.
To over-simplify, the Component Model manages language interop, and WIT constrains the boundaries with interfaces.
IMO the problem here is defining a 90% solution for most window, tab, button, etc management, then building embeddings in QT, Flutter/Skia, and other lower level engines. Getting a good cross-platform way of doing data passing, triggering re-renders, serializing window state is probably the meat of the interesting work.
On top of that, you really need great UX. This is normally where projects fall short -- why should I use this solution instead of something like Tauri[2] which is excellent or Electron?
[0]: https://github.com/WebAssembly/component-model/blob/main/des...
[1]: https://github.com/WebAssembly/component-model/blob/main/des...
[2]: https://tauri.app/
-
Missing the Point of WebAssembly
While I don't necessarily agree with the unnecessary, unsupported casual, & cheap contempt culture here ("unshackle the web from the mess that is JavaScript", "places that don't really need these problems to be solved")...
WebAssembly component-model is being developed to allow referring to and passing complex objects between different modules and the outside world, by establishing WebAssembly Interface Types (WIT). It's basically a ABI layer for wasm. This is a pre-requisite for host-object bridging, bringing in things like DOM elements.
Long running effort, but it's hard work and there's just not that many hands available for this deep work. Some assorted links with more: https://github.com/WebAssembly/component-model https://www.fermyon.com/blog/webassembly-component-model https://thenewstack.io/can-webassembly-get-its-act-together-...
It's just hard work, it's happening. And I think the advantages Andy talks to here illuminate very real reasons why this tech can be useful broadly. The ability to have plugins to a system that can be safely sandboxed is a huge win. That it's in any language allows much wider ecosystem of interests to participate, versus everyone interested in extending your work also having to be a java or c++ or rust developer.
-
Steel – An embedded scheme interpreter in Rust
A. Sure, but it isn't sufficiently beneficial for the cost.
B. WebAssembly is immature for developing a plugin system because of the lack of a sufficient ABI: https://github.com/WebAssembly/component-model
C. There aren't any other languages that meet the criteria. Lua was a no-go from the start. The maintainers did not like the language, and it necessitated adding more C code to Helix which could complicate building even further. https://github.com/helix-editor/helix/discussions/3806#discu...
-
Bring garbage collected programming languages efficiently to WebAssembly
AFAIK GC is irrelevant for "direct DOM access", you would rather want to hop into the following rabbit hole:
- reference types: https://github.com/WebAssembly/reference-types/blob/master/p...
- interface types (inactive): https://github.com/WebAssembly/interface-types/blob/main/pro...
- component model: https://github.com/WebAssembly/component-model
If this looks like a mess, that's because it is. Compared to that, the current solution to go through a Javascript shim doesn't look too bad IMHO.
-
Rust Is Surging Ahead in WebAssembly (For Now)
The wasm idl (called WIT) is actively being worked on here: https://github.com/WebAssembly/component-model/blob/main/des...
Being able to access DOM is definitely an objective. It's just taking a lot longer than folks guessed to build a modular wasm ABI.
-
Reaching the Unix Philosophy's Logical Extreme with WebAssembly
The WASM Component Model
https://github.com/WebAssembly/component-model
- WASI: WebAssembly System Interface
-
Introducing - Wasmer Runtime 4.0
Take a look at the python abi to see what the structure looks like for calling into components https://github.com/WebAssembly/component-model/tree/main/design/mvp/canonical-abi
- How WebAssembly Is Eating the Database
What are some alternatives?
material-maker - A procedural textures authoring and 3D model painting tool based on the Godot game engine
wit-bindgen - A language binding generator for WebAssembly interface types
Meshroom - 3D Reconstruction Software
bartholomew - The Micro-CMS for WebAssembly and Spin
mypaint - MyPaint is a simple drawing and painting program that works well with Wacom-style graphics tablets.
spin - Spin is the open source developer tool for building and running serverless applications powered by WebAssembly.
jspaint - 🎨 Classic MS Paint, REVIVED + ✨Extras
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
nixos-configuration - Nix(OS) system and user configurations
spec - WebAssembly specification, reference interpreter, and test suite.
Kha - Ultra-portable, high performance, open source multimedia framework.
proposals - Tracking WebAssembly proposals