2404cdc901
As another step toward aligning the macOS plugin API with the iOS plugin API, and with its final form, rename the plugin-related classes from FLEPlugin* to FlutterPlugin*. This makes the names of the clasess the same between iOS and macOS. Eventually they should actually merge, with annotations/ifdefs for platform differences, but for now since the macOS version uses the same method names and is simply a subset of the iOS APIs (with one to-be-stabilized method that is macOS-specific) doing the merge later won't be a breaking change. Doing this now allows for building out plugin tooling and plugin implementations on macOS without creating a growing body of code that will experience a breaking change later. See: https://github.com/flutter/flutter/issues/31735 https://github.com/flutter/flutter/issues/32718
Flutter Engine
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.
The Flutter Engine is a portable runtime for hosting Flutter applications. It implements Flutter's core libraries, including animation and graphics, file and network I/O, accessibility support, plugin architecture, and a Dart runtime and compile toolchain. Most developers will interact with Flutter via the Flutter Framework, which provides a modern, reactive framework, and a rich set of platform, layout and foundation widgets.
If you are new to Flutter, then you will find more general information on the Flutter project, including tutorials and samples, on our Web site at Flutter.dev. For specific information about Flutter's APIs, consider our API reference which can be found at the docs.flutter.dev.
If you intend to contribute to Flutter, welcome! You are encouraged to start with our contributor guide, which helps onboard new team members.