How autodesk-forge/forge-bim360-clashpdfexport works
Project Type and Main Components
a. Frontend Layer (www folder):
• Static web interface
• Forge Viewer integration
• Clash visualization components
• PDF export functionality
b. Backend Layer (server folder):
• Authentication services
• BIM 360/Forge API integration
• Data processing and analysis
• PDF generation services
c. External Services:
• Autodesk Forge Platform
• BIM 360 Services
• Model Coordination API
Component Relationships
[Client Browser] ←→ [Frontend Components] ←→ [Backend Services] ←→ [Forge/BIM360 APIs]
Detailed Component Breakdown
• Main UI (index.html)
• Forge Viewer (ForgeViewer.js)
• Clash Views (breakdown, matrix, raw views)
• PDF Generation Interface
• OAuth Authentication (oauth.services.js)
• Data Management Services (dm.*.services.js)
• Model Coordination Services (mc.*.services.js)
• Analysis Engine (analyze.js)
• Forge Authentication
• BIM 360 Platform
• Model Coordination API
• Data Management API
Data Flows
• User authentication flow
• Model set data retrieval
• Clash data processing
• PDF generation and export
Specific Implementation Details
Technical elements:
• Node.js backend
• Express.js server
• Forge Viewer integration
• jsPDF library for PDF generation
• REST API endpoints
┌─────────────────────────────────────────────┐
• Client Layer (Browser) │
• ┤
• Application Layer │
• ┌─────────────┐ ┌─────────────┐ │
• Frontend │ │Backend │ │
• Components │ │Services │ │
• ┘ └─────────────┘ │
• ┤
• External Services Layer │
• (Forge APIs, BIM 360, Model Coordination) │
• ┘
Technical Notes
Annotations for:
• Authentication requirements
• API version dependencies
• Critical data processing points
• Performance considerations
Remember to include version numbers for key components and APIs as mentioned in the README (e.g., Forge Viewer v7.25, Node.js v10+).