How j03lk/prueba-mov3 works
This is a small, otherwise undocumented Flutter application. Its visible product surface consists of a Dart entry point, a drawer, and three screens; their contents and navigation wiring were not sampled, so no Dart call relationships are asserted. The sampled platform files show native launch/window hosting scaffolding, not additional product-domain stages. Native-to-Dart handoff details are not evidenced in the excerpts.
Main entry points: flutter_window.cpp Flutter window · main.cc Linux launcher · main.cpp Windows launcher · main.dart Dart entry
Components 15
Flutter application
- Dart entry
lib/main.dart - Navigation drawer
lib/navigation/drawer.dart - Screen one
lib/screens/pantalla1Screen.dart - Screen two
lib/screens/pantalla2Screen.dart - Screen three
lib/screens/pantalla3Screen.dart
Platform hosts
- Linux launcher
linux/runner/main.cc - Linux app host
linux/runner/my_application.h - Windows launcher
windows/runner/main.cpp - Flutter window
windows/runner/flutter_window.cpp - Win32 window
windows/runner/win32_window.cpp - Window interface
windows/runner/win32_window.h - Linux plugin registry
linux/flutter/generated_plugin_registrant.h - Windows plugin registry
windows/flutter/generated_plugin_registrant.h - macOS plugin registry
macos/Flutter/GeneratedPluginRegistrant.swift
Other components
- App user
Connections 4
- App user → Dart entry: opens app
- Linux launcher → Linux app host: creates app
linux/runner/main.cc - Windows launcher → Flutter window: creates window
windows/runner/main.cpp - Flutter window → Window interface: extends