Skip to main content

Flutter plugin v21 now available -- Introducing the NEW Flutter Inspector

Flutter Inspector

We’re very excited to be able to announce the first version of the Flutter Inspector for IntelliJ and Android Studio! It will be featured in a talk at DartConf in LA (Wednesday, Jan. 24, 10am Pacific time) and will be live streamed on the DartConf website and on the Google Developers channel on Youtube. Be sure to watch it.

The inspector makes it much easier to understand why your application is rendering the way it does. It allows you to: 
  • View the UI structure of your app as a tree of widgets. 
  • Select a point on your device or simulator and find the corresponding Widget that rendered those pixels. 
  • View properties for individual widgets. 
  • Generally, better understand layout issues. 
The inspector view can be opened via View > Tool Windows > Flutter Inspector (it shows content only when an app is running). To inspect a specific widget, select the ‘Toggle inspect mode’ action in the toolbar, then click on the desired widget on the phone or simulator. The widget will be highlighted in your app’s UI, you’ll see the widget in the widget hierarchy in IntelliJ, and will be able to view the individual properties for that widget.

We’re actively working in this space, including working on ways to filter the number of widgets shown in the tree view; look for more news in the coming months. Don’t hesitate to provide feedback to us on the inspector!

Additional inspector features and changes in the M21 release:
  • renamed the ‘Flutter’ view to ‘Flutter Inspector’ 
  • normalized the Flutter Inspector toolbar icons 
  • in the property view, show color properties with a color swatch 
  • in the property view, show icon properties using their associated Material icons 
  • fix to enable the Flutter Inspector view to display for Bazel projects 

App launch and running improvements

We now display a notification when programs elements were successfully reloaded but not run when the view was reassembled; this is an indication that you may need to restart to see your UI changes:

Additional launch and run changes:
  • add a hyperlink for the “restart” message in the debugging console output 
  • improved console hyperlinking for local files 
  • ensure that an existing config is selected at startup, and fix run config autoselection for plugin projects 
  • for non-Bazel projects, don't show the Flutter Bazel launch type 

Testing support improvements

  • fix test discovery for plugin example tests, and fix discovery of tests in example sub-directories 
  • improve the pub root detection for flutter tests

Popular posts from this blog

A stronger Dart for everyone

We are constantly asking ourselves:
How do we make developers even more productive when writing Dart apps? We believe that a critical part of the answer to this question is to make strongmode – a sound static type system for Dart – the standard for all Dart developers.

Teams that use Dart to build apps like Soundtrap, AdWords, AdSense, and Greentea say they really enjoy using strong mode features, such as early error detection. In fact, teams that have switched completely to strong mode cite not only early error detection but also better code readability and maintainability as major benefits. We hear this both from small teams and – even more so – from large teams with hundreds of developers writing and maintaining millions of lines of Dart code. As Björn Sperber from Soundtrap says,
Strong mode and the smooth integration with IntelliJ is a joy to use and a huge improvement. If you’ve tried out Flutter, you’ve already used strong mode checks from the Dart analyzer.

Given the benefits …

AngularDart 3.0: Easy upgrade, better performance

AngularDart 3.0 is now available. It brings better performance and smaller generated code, while also making you more productive.

Version 3.0 is an evolution: although it has some breaking changes (detailed below), it is a smooth upgrade due to minimal public API adjustments. Most of the progress is under the hood—in code quality, stability, generated code size, performance, and developer experience.

Code quality:
2731 instances of making the framework code more type safe (using sound Dart).The AngularDart framework code size is down by 12%.Many additional style updates to the codebase:Changed to use idiomatic <T> for generic methods.Removed NgZoneImpl, all the code exists in NgZone now.Stability:
Many CSS encapsulation fixes due to update with csslib package.Fixed bugs with IE11.

For the Mail sample app, we see 30% faster time-to-interactive (currently 3812 ms on a simulated 3G connection, measured via Lighthouse).Our large app benchmark shows 2x faster render times of…

AngularDart 4

AngularDart v4 is now available. We've been busy since the release angular2 v3.1.0 in May. Not only did we "drop the 2", but we also improved the compiler and tightened up the framework to give you smaller code, we updated the package structure to improve usability, and we added several new features. Check out the updated documentation to get started.
Just angular Upgrading to v4 will require more than updating your version constraint. The package has changed names (back) to angular – dropping the 2. You'll need to update your pubspec.yaml and the corresponding imports in your code. In most instances, find-and-replace should do the trick. Going forward, the package will be called package:angular. We'll just update the version number.
Smaller code The updated compiler in 4.0 allows type-based optimizations that not only improve runtime performance but generate better code because we are able to strongly type templates. A big result of the update is that many ap…