FLU — Flutter

FLU Flutter projects, and the toolchain that goes with them.

The projects

The list remembers the projects that were opened. “Create a Flutter project” asks for the package name and the folder.

What a left click does depends on where you are. In a project, it opens the menu: that is what you need on the spot — run, build, the devices. Elsewhere, it jumps to the last project opened from this button, where there is nothing to act on. Right-click opens the menu everywhere.

The commands

Get dependencies, analyze, test, format, clean, upgrade, see outdated dependencies, run the diagnostic. Build release targets Windows, Linux, Android (APK or bundle) and the Web — and it really is --release for all five, which the earlier label, “Build…”, did not say.

Build debug targets the same five platforms with --debug: it is the same menu, only the mode changes. It asks for no device — this is how you drop a debug binary without waiting for the toolchain to answer.

Run

The device list is behind its entry, not inside it. Spread out in the menu, it forced the toolchain to be queried on every opening: flutter devices takes a few seconds, and you paid that delay just to pick “Analyze” or “Get dependencies”. It is now looked up only when it is about to be used. A single target — and the command starts without asking anything.

“Run” looks for devices and offers its own — or all of them. The output is displayed as it comes, with Flutter’s keys within reach: reload (r), restart (R), help (h), detach (d), clear the output (c), quit (q). “Run with options…” adds whatever you want to flutter run — --profile, --dart-define=key=value. “Look for devices…”, at the bottom of that same menu, restarts the search and comes back to it: a phone plugged in afterwards would never appear otherwise.

The end is stated: Done, Failed (1), Stopped. The output can be copied with a button.

A successful build leads to its file. A button then appears in the banner: it takes the view to the result’s folder and puts the cursor on it — the .exe, the .apk, the bundle. It is the toolchain that says where it wrote, not a list of paths kept here: each target puts its own elsewhere, and this changes with Flutter versions. Nothing appears while the command is running, nor when it has failed — there would be nothing to show.

If the toolchain is missing

The button appears only where Flutter is installed.

Meneaufile manual, in English.