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

Comments

Popular posts from this blog

Const, Static, Final, Oh my!

Posted by Seth Ladd

(This is an "oldie but a goodie" misc@dartlang.org post originally written by Bob Nystrom. It is being posted here as the explanations still ring true.)

Bob writes:


"static", "final", and "const" mean entirely distinct things in Dart:

"static" means a member is available on the class itself instead of on instances of the class. That's all it means, and it isn't used for anything else. static modifies *members*.

"final" means single-assignment: a final variable or field *must* have an initializer. Once assigned a value, a final variable's value cannot be changed. final modifies *variables*.

"const" has a meaning that's a bit more complex and subtle in Dart. const modifies *values*. You can use it when creating collections, like const [1, 2, 3], and when constructing objects (instead of new) like const Point(2, 3). Here, const means that the object's entire deep state can be determ…

Dart 1.12 Released, with Null-Aware Operators and more

Dart 1.12.0 is now released! It contains the new null-aware operators language feature, and enhancements to pub, Observatory, dartdoc, and much more.

Null-aware operators

The new null-aware operators help you reduce the amount of code required to work with references that are potentially null. This feature is a collection of syntactic sugar for traversing (potentially null) object calls, conditionally setting a variable, and evaluating two (potentially null) expressions.

Click or tap the red Run button below to see them in action.

??

  if null operator. `expr1 ?? expr2` evaluates to `expr1` if not `null`, otherwise `expr2`.


??=

  null-aware assignment. `v ??= expr` causes `v` to be assigned `expr` only if `v` is `null`.

x?.p

  null-aware access. `x?.p` evaluates to `x.p` if `x` is not `null`, otherwise evaluates to `null`.

x?.m()

  null-aware method invocation. `x?.m()` invokes `m` only if `x` is not `null`.

Learn more about Dart's null-aware operators in our Language Tour.

.packages fi…

The new AdWords UI uses Dart — we asked why

Google just announced a re-designed AdWords experience. In case you’re not familiar with AdWords: businesses use it to advertise on google.com and partner websites. Advertising makes up majority of Google’s revenue, so when Google decides to completely redo the customer-facing front end to it, it’s a big deal. The Dart team is proud to say that this new front end is built with Dart and Angular 2. Whenever you asked us whether Google is ‘even using Dart for anything,’ this is what we had in mind but couldn’t say aloud. Until now. We asked Joshy Joseph, the primary technical lead on the project, some questions. Joshy is focusing on things like infrastructure, application latency and development velocity, so he’s the right person to ask about Dart.Q: What exactly did we launch on Monday?It’s a complete redesign of the AdWords customer experience that is rolling out slowly as a test to a small initial set of advertisers. The most noticeable thing is probably the Material Design look and f…