back to home

sengchor / kokraf

Collaborative 3D Modeling Application on the Web

View on GitHub
209 stars
21 forks
1 issues

AI Architecture Analysis

This repository is indexed by RepoMind. By analyzing sengchor/kokraf in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.

Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.

Source files are only loaded when you start an analysis to optimize performance.

Embed this Badge

Showcase RepoMind's analysis directly in your repository's README.

[![Analyzed by RepoMind](https://img.shields.io/badge/Analyzed%20by-RepoMind-4F46E5?style=for-the-badge)](https://repomind.in/repo/sengchor/kokraf)
Preview:Analyzed by RepoMind

Repository Overview (README excerpt)

Crawler view

Kokraf – 3D Modeling Application on the Web Kokraf is a modern, browser-based 3D modeling tool built for real-time creativity. Whether you're a hobbyist, designer, or developer, Kokraf gives you a smooth, intuitive interface to model, manipulate, and view 3D objects directly in your browser — no installation needed. šŸŽ„ **Modeling Demo:** https://youtu.be/hpA3I_OLDl4 šŸš€ Live Demo Try it live here: https://kokraf.com/ *(Best viewed on a desktop browser like Chrome)* User Manual – Learn the tools and workflow šŸ› ļø Built With • Three.js – 3D rendering • HTML, CSS, JavaScript • Supabase - for backend • GitHub Pages – for free hosting 🌟 Community • Discord: Join the community • YouTube: Jourverse Channel • X: Jourverse on X 🧰 Getting Started To run this project locally on your PC: Then open the project in Visual Studio Code. Open and use the **Live Server** extension to view the project in your browser. 🧩 Core Mesh Representation Kokraf does not edit Three.js geometries directly. Instead, it uses a custom adjacency mesh as its core data model. All modeling operations (extrude, move, split, etc.) operate on this mesh data. After each operation, the mesh is converted into a and sent to Three.js purely for rendering. This separation keeps modeling logic independent from the renderer, allows direct polygon (quad) representation, and supports real modeling workflows rather than render-only editing.