Flutter plugin v22 now available -- New Flutter tooling releases!
Wm Leler
Improved Flutter editing assists
We’ve added several new code refactorings to help you build and refactor your Flutter UI code. In VS Code they are available in the light bulb menu using the keyboard shortcut ‘cmd-.’; in IntelliJ / Android Studio these are available via the keyboard shortcut ‘cmd-enter’.
Flutter Outline view
Available in the IntelliJ plugin this release, we’re introducing the first version of the Flutter Outline view. This view provides a structured tree view of the UI widgets of your build method. It synchronizes the selection between the outline tree and the source code, allowing you to select a widget in the tree and see the corresponding source location. The view also exposes several code refactorings, like widget centering, padding, and deletion, from its toolbar:
The view is currently behind a flag; to see the Outline view, open the Preferences dialog, and adjust the Flutter Outline setting in Languages & Frameworks > Flutter. Please try it out and provide us with feedback for improvements!
Flutter Inspector Improvements
We’ve moved the Flutter Inspector out from behind a flag - it’s on and available by default! In order to improve it’s discoverability, we automatically open it when you run a Flutter app; this is configurable via a user preference. Some Flutter Inspector improvements this release include live updating of property values as a widget animates, and improved tracking of widget creation locations (this feature requires passing the --preview-dart-2 and --track-widget-creation flags in your launch configuration). Additional improvements include:
Support for multiple running applications
Basic speed search for the Inspector Tree
Restore flutter framework toggles after a restart
Action to open the Observatory timeline view
Enum property support and tweaks to the property display
VS Code and Dart-Code
This version of Dart-Code focuses on simplifying getting started with Flutter projects and improving the code editing experience.
In the command palette you'll find a new command (Flutter: New Project) that will prompt for a project name/location and run flutter create for you, opening the resulting project at the lib/main.dart file without you needing to use a terminal:
To streamline starting a debugging session, two steps have been removed from the initial debugging process for a Flutter application:
You'll no longer be asked to pick between the Dart and Flutter debuggers.
You'll no longer be presented with a launch.json file to modify. The launch.json file is no longer required for Flutter unless you need to specify a different entry script or custom arguments.
If you have an existing launch.json file and haven't customised it, you may delete it. Pressing F5 will now immediately launch the Flutter debugger.
And, we’ve updated the package update prompt: if you open a project that has missing or stale packages you'll now be prompted to fetch them. If you have multiple workspace folders then each one will be updated in sequence.
Additionally, the following improvements have been made to the editor:
Flutter-specific snippets:
stless: StatelessWidget
stful: StatefulWidget
stanim: StatefulWidget with an AnimationController
Code fixes now support tab stops
More intelligent code completion will avoid inserting parameter placeholders that already exist
Dart 2 preview
The Dart team recently announced a major update to the Dart programming language: Dart 2! The M22 IntelliJ plugin and latest VS Code plugin add support for enabling a preview of Dart 2 for Flutter. For details, see the Dart 2 Preview for Flutter page.
For more information
For more detailed fixes and improvements, see our changelogs:
see the Flutter IntelliJ plugin changelog
Ken
--
You received this message because you are subscribed to the Google Groups "Flutter Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flutter-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
ra...@dasralph.de
Devon Carew
this "Flutter inspector auto open on every app start" thing is to much for me. Can you explain how I can disable it? "this is configurable via a user preference" is too little information for me.Ralph
--
You received this message because you are subscribed to the Google Groups "Flutter Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to flutter-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.