How amanbohra7/bioarsdk works
Main Components
• Unity Engine Core: This is implicit since the project is a Unity project. Denote the Unity Engine as the underlying runtime.
• AR & Camera Components: Illustrate the AR components such as phone camera scripts (e.g., PhoneCamera.cs in ElectronDetections) and AR view controllers, which capture and process camera input, and integrate with ARCore (noting the presence of ARCoreProjectSettings.json).
• Model Generation and 3D Assets: Represent a component responsible for generating or modifying 3D models (see ModelGenerator scripts and assets like Fbx and Structures directories). These components likely handle model creation and modification during runtime.
• UI & Interaction Controllers: Include UI panels and controllers (e.g., ARviewUI.cs, EPanel.cs, and various UI folders) that manage user interactions.
• Data and Configuration: There are directories for DATA and JSON files (the PeriodicTableJson folder) indicating that the app loads and parses data—perhaps from a periodic table or similar biomolecular data.
• External/Third-Party Libraries: List LeanTween, JsonDotNet, OpenCVForUnity, and ExternalDependencyManager as key external dependencies that provide functionalities like smooth transitions, JSON serialization, and computer vision.
Relationships and Interactions
• The AR scenes communicate with the Unity Engine’s core rendering and input system.
• The UI Components receive input from the user and interact with scene controllers that coordinate the AR camera’s input, model generation, and visualization.
• The Model Generator component takes data (from assets or external sources like the JSON files) and dynamically constructs or alters 3D models.
Architectural Patterns and Design Principles
• Modular Separation: The project is broken into logical directories – Scripts, Scenes, Assets, Prefabs – implying a modular approach.
• MVC-like Separation: Though a strict MVC may not be implemented, the separation between “view” (scenes, UI prefabs), “controller” (various script controllers), and “model” (data, assets, external libraries) is evident.
• Use of External Dependencies for Clear Separation: The integration of third-party libraries is encapsulated in their directories (LeanTween, JsonDotNet, ExternalDependencyManager) indicating a plugin-based or component-based architecture.
Relevant Technologies and Frameworks
• Unity 3D Engine as the core runtime
• ARCore integration (via the ARCoreProjectSettings.json)
• LeanTween for tween animations
• JsonDotNet for JSON parsing
• ExternalDependencyManager for handling library dependencies
• OpenCVForUnity for image processing within AR features