How leks51ex/docker_flutter_test works
This is a starter Flutter application with a Dart entry point and native launch shells; the README documents no domain-specific features or workflow. The sampled code shows Linux and Windows startup paths, and iOS plugin registration. The Dart UI and several native host implementations were not sampled, so their runtime connections are not asserted.
Main entry points: flutter_window.cpp Flutter window · my_application.cc Linux host · win32_window.cpp Win32 window · main.cc Linux entry
Components 14
Desktop hosts
- Linux entry
linux/runner/main.cc - Linux host
linux/runner/my_application.cc - Linux host API
linux/runner/my_application.h - Linux plugin API
linux/flutter/generated_plugin_registrant.h - Windows entry
windows/runner/main.cpp - Flutter window
windows/runner/flutter_window.cpp - Flutter window API
windows/runner/flutter_window.h - Win32 window
windows/runner/win32_window.cpp - Win32 window API
windows/runner/win32_window.h - Windows plugin API
windows/flutter/generated_plugin_registrant.h
Mobile hosts
- iOS app delegate
ios/Runner/AppDelegate.swift - macOS plugin registration
macos/Flutter/GeneratedPluginRegistrant.swift
Flutter app
- Flutter application
lib/main.dart
Other components
- App user
Connections 8
- App user → Flutter application: uses
- Linux entry → Linux host: creates and runs
linux/runner/main.cc - Linux host → Linux host API: implements
linux/runner/my_application.cc - Windows entry → Flutter window: creates
windows/runner/main.cpp - Flutter window → Win32 window: inherits from
- Flutter window → Flutter window API: implements
windows/runner/flutter_window.cpp - Win32 window → Win32 window API: implements
windows/runner/win32_window.cpp - iOS app delegate → macOS plugin registration: registers plugins
ios/Runner/AppDelegate.swift