How lambsauce911/flutter_valladolid_austin works
This is a Flutter student-profile-form application with native launch shells for multiple desktop and mobile platforms. The principal user workflow appears to be entering a student profile in the Dart app, but the README is empty and lib/main.dart was not sampled, so its form stages and internal behavior cannot be verified. The graph therefore shows the app entry and evidenced native host relationships without inventing form logic; platform boilerplate is represented only where the source index identifies core modules.
Main entry points: main.dart Student profile app · main.cpp Windows entry point · flutter_window.h Flutter window host · my_application.h GTK application
Components 11
Flutter application
- Student profile app
valladolid_act05/lib/main.dart
Platform hosts
- Windows entry point
valladolid_act05/windows/runner/main.cpp - Flutter window host
valladolid_act05/windows/runner/flutter_window.h - Win32 window
valladolid_act05/windows/runner/win32_window.cpp - Linux entry point
valladolid_act05/linux/runner/main.cc - GTK application
valladolid_act05/linux/runner/my_application.h - Linux plugin interface
valladolid_act05/linux/flutter/generated_plugin_registrant.h - Windows plugin interface
valladolid_act05/windows/flutter/generated_plugin_registrant.h - macOS plugin registrar
valladolid_act05/macos/Flutter/GeneratedPluginRegistrant.swift - iOS app delegate
valladolid_act05/ios/Runner/AppDelegate.swift
Other components
- App user
Connections 7
- App user → Student profile app: uses
- Windows entry point → Flutter window host: creates
valladolid_act05/windows/runner/main.cpp - Flutter window host → Win32 window: inherits
valladolid_act05/windows/runner/flutter_window.h - Windows entry point → Student profile app: launches
- Linux entry point → GTK application: creates
valladolid_act05/linux/runner/main.cc - GTK application → Student profile app: launches
- iOS app delegate → Student profile app: launches