How sharmer156/dialux works
Project type and purpose
• This is not a traditional codebase but an open-source resource repository for the DIALux lighting-design software.
• Purpose: to collect and distribute sample files (.dlx, .ies), a mobile APK, images, documentation, and links to courses/plugins.
File structure
• Top‐level artifacts:
• DialuxMobile.apk – the DIALux mobile app binary
• dialux-sample-files/ – sample DIALux project files (.dlx)
• ies-sample-files/ – sample photometric IES files and a README
• img/ – supporting images and a readme
• README.md, LICENSE – repository documentation
• No source code or build scripts; it is static content for download/use.
• Directory “file composition” contains its own README (likely describing how files are organized).
README for additional insights
• README describes DIALux, how to download the desktop/mobile software, and points to tutorials and plugin info.
• No internal architecture; it serves as a hub for resources.
a. Main components
• Git Repository (GitHub/GitLab/etc.)
• Artifact Storage
– APK (DialuxMobile.apk)
– .dlx sample files (dialux-sample-files/)
– .ies sample files (ies-sample-files/)
– Images (img/)
• Documentation
– README.md at root
– file composition/README.md
– ies-sample-files/readme.markdown
• End Users
– Lighting designers (desktop users)
– Mobile users (install APK)
– Plugin developers (refer to /plugin/README.md)
b. Relationships and interactions
• Users clone or download the Git repo → retrieve artifacts → open in DIALux desktop or mobile
• Documentation guides users how to install or use samples
• Sample files are loaded into DIALux for design and calculation
c. Architectural patterns or design principles
• Static content repository pattern
• Clear separation between asset types (DXL projects vs. IES photometric data vs. images vs. binaries vs. docs)
d. Relevant technologies/frameworks
• Git for version control and distribution
• DIALux Desktop & DIALux Mobile apps for consumption of samples and APK
• Markdown for documentation