How coka/webgl-editor works
Project type and purpose
• This is a browser‐based 3D modeling editor built as a single‐page application (SPA) with a minimal Node.js/Express static server.
• It uses Polymer web components for the UI and three.js for 3D scene rendering.
File structure
• Top‐level files:
• app.js – Node/Express app serving static assets
• index.html – entry HTML for the SPA
• gulpfile.js – build tasks (bundling, minification, live reload)
• package.json & bower.json – dependency definitions (npm & Bower)
• elements/ – custom Polymer elements folder
– editor-attribute-view/ – UI for editing object properties
– editor-viewport/ – WebGL canvas for rendering the scene
– webgl-editor/ – container component orchestrating viewport & attributes
• No separate “backend” business logic or database directories—purely front-end with a simple static‐file server.
README for additional insights
• Confirms focus on simplifying 3D content creation in the browser.
• Emphasizes Polymer + three.js stack and quick start via npm scripts.
Detail
• Versioned dependencies (e.g., three.js vX, Polymer vX) if known.
• Config files (gulpfile.js, bower.json, package.json) as part of Build/CI.
• Event bus or direct method calls between editor-attribute-view and webgl-editor.
• That editor-viewport is purely rendering while editor-attribute-view is purely input.
• Don’t over-complicate—represent every folder and file group only if it contributes to runtime or build.