How whynotmake-it/flutter_liquid_glass works
Project type and purpose
• This is a Flutter-based monorepo of two related Dart packages, managed with Melos:
• liquid_glass_renderer: a core Flutter package providing liquid‐glass rendering via custom shaders and widgets.
• apple_liquid_glass: a thin wrapper that re-exports the core renderer for Apple‐specific use (currently WIP).
• An example Flutter app demonstrates usage of the renderer.
File structure
• Top‐level:
• melos.yaml – orchestrates workspace commands across packages (versioning, publishing, test runs).
• .github/workflows – CI pipelines (build, test, tag‐release).
• packages/ – two subpackages.
• liquid_glass_renderer/:
• lib/assets/shaders/ – GLSL fragment shaders (liquid_glass.frag, etc).
• test/ – unit/golden tests verifying rendering correctness.
• apple_liquid_glass/:
• minimal structure exporting the core library.
README for additional insights
• The README confirms this is a workspace of two interdependent Flutter packages.
a. Main components:
• Developer & CI (Melos) – workspace orchestration, versioning, publishing.
• Core Package: liquid_glass_renderer
– Assets: GLSL shader files loaded at runtime.
– Tests: unit and golden image tests.
• Wrapper Package: apple_liquid_glass (depends_on → liquid_glass_renderer)
• Example App: depends_on both packages; runs on Flutter desktop/mobile.
• External Services: pub.dev (package hosting), GitHub Actions (CI).
b. Relationships & data flow:
• Developer (IDE/CLI) → invokes Melos → runs build/test/publish on each package.
• Example App → imports apple_liquid_glass AND liquid_glass_renderer → at runtime loads shaders → Flutter engine & GPU.
• CI workflows trigger Melos scripts on push/tag → run tests in each package → publish on version bump.
c. Architectural patterns & design principles:
• Monorepo modularity via Melos: share common scripts, enforce version consistency.
• Separation of concerns: core rendering logic (renderer), platform-specific exports (apple).
• Asset-driven shader pipeline: GLSL files are first-class assets.
• Example app for integration verification.
d. Technologies & frameworks:
• Dart & Flutter (rendering surface, widget tree)
• Melos (monorepo management)
• GitHub Actions (CI/CD)
• GLSL (shader code)