How debuggings/sweethome3d-app-wiki works
Project type and purpose
• This is Sweet Home 3D, a standalone desktop Java application (with optional applet and Java Web Start variants) that provides interior-design functionality.
• Key features: a Swing-based UI, a 3D view rendered via Java3D (and optional Yafaray), project persistence (XML, obj/dae import), and a plugin architecture.
File structure
• Top-level:
• build.xml / pom.xml – Ant and Maven build scripts
• install/ – platform installers and scripts
• src/main/java/com/eteks/sweethome3d/… – Java packages (applet, io, j3d, model, plugin, swing, tools, viewcontroller)
• src/main/resources – localized properties, 3D assets, help pages
• src/test – JUnit tests
• Architectural pattern: classic MVC (model + view/controller packages), layered modules (model ↔ controllers ↔ Swing UI and 3D engine), pluggable extensions.
README for additional insights
• Confirms Java SE compatibility, Java3D and native‐lib dependencies, Ant/Maven build targets, and packaging steps.
Elements
User → UI → Controller → Model → I/O
Controller → 3D Engine → Model
• Presentation (blue)
• Business logic (green)
• Persistence (orange)
• Extensions / tooling (gray)
Final advice
• External native dependencies (Java3D binaries, Yafaray) as runtime “side-loaded” modules.