- TypeScript 60.8%
- Rust 38.1%
- Python 0.4%
- CSS 0.4%
- JavaScript 0.1%
|
|
||
|---|---|---|
| .github | ||
| .helix | ||
| .husky | ||
| assets | ||
| docs | ||
| e2e/playwright | ||
| openapi | ||
| packages | ||
| public | ||
| rust | ||
| scripts | ||
| src | ||
| types | ||
| .env.development | ||
| .env.production | ||
| .envrc | ||
| .gitattributes | ||
| .gitignore | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierignore | ||
| .tool-versions | ||
| _typos.toml | ||
| babel.config.js | ||
| biome.json | ||
| CONTRIBUTING.md | ||
| electron-builder.yml | ||
| eslint.config.mjs | ||
| flake.lock | ||
| flake.nix | ||
| forge.config.ts | ||
| forge.env.d.ts | ||
| GLOSSARY.md | ||
| index.html | ||
| Info.plist | ||
| INSTALL.md | ||
| interface.d.ts | ||
| LICENSE | ||
| Makefile | ||
| package-lock.json | ||
| package.json | ||
| playwright.config.ts | ||
| playwright.electron.config.ts | ||
| playwrightProcess.mjs | ||
| postcss.config.js | ||
| PRINCIPLES.md | ||
| README.md | ||
| release-notes.md | ||
| tailwind.config.js | ||
| tsconfig.json | ||
| tsconfig.node.json | ||
| vercel.json | ||
| vite-env.d.ts | ||
| vite.base.config.ts | ||
| vite.config.ts | ||
| vite.main.config.ts | ||
| vite.preload.config.ts | ||
| vite.renderer.config.ts | ||
| vitest.config.ts | ||
| vitest.workspace.ts | ||
Zoo Design Studio
A CAD application from the future, brought to you by the Zoo team.
Design Studio is our take on what a modern modelling experience can be. It is applying several lessons learned in the decades since most major CAD tools came into existence:
- All artifacts—including parts and assemblies—should be represented as human-readable code. At the end of the day, your CAD project should be "plain text"
- This makes version control—which is a solved problem in software engineering—trivial for CAD
- All GUI (or point-and-click) interactions should be actions performed on this code representation under the hood
- This unlocks a hybrid approach to modeling. Whether you point-and-click as you always have or you write your own KCL code, you are performing the same action in Design Studio
- Everything graphics has to be built for the GPU
- Most CAD applications have had to retrofit support for GPUs, but our geometry engine is made for GPUs (primarily Nvidia's Vulkan), getting the order of magnitude rendering performance boost with it
- Make the resource-intensive pieces of an application auto-scaling
- One of the bottlenecks of today's hardware design tools is that they all rely on the local machine's resources to do the hardest parts, which include geometry rendering and analysis. Our geometry engine parallelizes rendering and just sends video frames back to the app (seriously, inspect source, it's just a
<video>element), and our API will offload analysis as we build it in
- One of the bottlenecks of today's hardware design tools is that they all rely on the local machine's resources to do the hardest parts, which include geometry rendering and analysis. Our geometry engine parallelizes rendering and just sends video frames back to the app (seriously, inspect source, it's just a
We are excited about what a small team of people could build in a short time with our API. We welcome you to try our API, build your own applications, or contribute to ours!
Design Studio is a hybrid user interface for CAD modeling. You can point-and-click to design parts (and soon assemblies), but everything you make is really just kcl code under the hood. All of your CAD models can be checked into source control such as GitHub and responsibly versioned, rolled back, and more.
The 3D view in Design Studio is just a video stream from our hosted geometry engine. The app sends new modeling commands to the engine via WebSockets, which returns back video frames of the view within the engine.
Technology
- UI
- Networking
- WebSockets (via KittyCAD TS client)
- Code Editor
- Modeling
Get Started
We recommend downloading the latest application binary from our website. If you don't see your platform or architecture supported there, please file an issue. See the installation guide for additional instructions.
Developing
Finally, if you'd like to run a development build or contribute to the project, please visit our contributor guide to get started. To contribute to the KittyCAD Language, see the dedicated readme for KCL.