Hixie 68c57fb67f Require giving a GlobalKey to UniqueComponent
Having UniqueComponent automatically generate its own key is a trap. If
anyone ever creates a UniqueComponent in a build function (rather than
ahead of time) and forgets to pass a key, then that entire subtree is
going to be rebuilt, including layout, every time it's updated. Since
there's basically no way for us to catch this, we should at least force
the author to see the explicit "new GlobalKey()" call in their code.
2015-09-28 11:53:03 -07:00
2015-09-08 13:32:50 -07:00
2015-09-16 09:03:47 -07:00
2015-07-16 10:16:42 -07:00
2015-07-16 10:16:42 -07:00
2015-09-10 08:49:56 -07:00
.gn
2015-07-16 10:16:42 -07:00
2015-07-24 12:24:05 -07:00
2015-09-25 14:28:39 -07:00
2015-07-16 10:16:42 -07:00
2015-09-20 14:02:52 -07:00

Flutter

Build Status

Flutter is a new way to build high-performance, cross-platform mobile apps. Flutter is optimized for today's, and tomorrow's, mobile devices. We are focused on low-latency input and high frame rates on Android and iOS.

Community

Join us on IRC at #flutter on Freenode or join our mailing list, sky-dev@googlegroups.com.

Languages
Dart 75%
C++ 16.5%
Objective-C++ 2.9%
Java 2.8%
Objective-C 0.7%
Other 1.9%