armortools VS manifold

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.

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.

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

May I suggest Armory Painter (https://armorpaint.org)

One of the best examples of this is Armorpaint an open source texture painting tool.

ArmorPaint - haven't used that one, but it looks promissing

Small in a relative sense compared to some larger codebase.

Here's a bit on Manifold:

https://github.com/elalish/manifold/wiki/Manifold-Library

and the author's blog is interesting:

https://elalish.blogspot.com/search/label/Manifold

For cad kernels I highly recommend manifold https://github.com/elalish/manifold

Our project https://github.com/elalish/manifold made use of this to speed up mesh processing algorithms a lot.

Wondering why no BRep support means it is not a CAD. It seems that OpenVSP doesn't use BRep but uses parametric surface [1]. I wonder if mesh-based modeling + some constraints solving will get you a CAD, or are there other requirements that I don't know? I only work on mesh processing library on my free-time and I don't know much about BRep.

[1] https://github.com/elalish/manifold/discussions/549#discussi...

Unhealthy relationship with keyboards? Comparing with the r/MechanicalKeyboards or r/ErgoMechKeyboards people this relationship is more like divorced...

I added python binding and ended up being on of the devs for https://github.com/elalish/manifold because OpenSCAD is too slow for my modeling (I am quite impatient). Optimizing my keyboard for months with more than 5 complete rebuilds to optimize my design (looks like this: https://i.redd.it/xtf0f54mt7ya1.jpg), and is afraid of open sourcing it because my code looks too bad :(

Now much faster and more stable thanks to the Manifold engine (https://github.com/elalish/manifold): in fact it is often faster than the last stable desktop release from https://openscad.org/.

Also much better code completion, and ships with a few examples from the various bundled libraries to get you started.

At the end, they gonna replace it with ( elalish manifold.