https://github.com/flutterquill/quill-native-bridge
An internal plugin for flutter_quill package to access platform-specific APIs
https://github.com/flutterquill/quill-native-bridge
clipboard flutter flutter-package flutter-plugin
Last synced: 4 months ago
JSON representation
An internal plugin for flutter_quill package to access platform-specific APIs
- Host: GitHub
- URL: https://github.com/flutterquill/quill-native-bridge
- Owner: FlutterQuill
- License: mit
- Created: 2024-10-14T00:14:21.000Z (9 months ago)
- Default Branch: main
- Last Pushed: 2024-12-14T20:51:19.000Z (7 months ago)
- Last Synced: 2025-03-05T13:18:44.995Z (4 months ago)
- Topics: clipboard, flutter, flutter-package, flutter-plugin
- Language: Dart
- Homepage: https://pub.dev/packages/quill_native_bridge
- Size: 1.02 MB
- Stars: 0
- Watchers: 1
- Forks: 3
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# 🪶 Flutter quill_native_bridge plugin
An internal Flutter plugin for [`flutter_quill`](https://pub.dev/packages/flutter_quill) package to access platform-specific APIs,
built following the [federated plugin architecture](https://docs.google.com/document/d/1LD7QjmzJZLCopUrFAAE98wOUQpjmguyGTN2wd_89Srs/).
A detailed explanation of the federated plugin concept can be found in the [Flutter documentation](https://docs.flutter.dev/packages-and-plugins/developing-packages#federated-plugins).This means the project is separated into the following packages:
1. [`quill_native_bridge`](https://pub.dev/packages/quill_native_bridge): The app-facing package that clients depend on to use the plugin. This package specifies the API used by the Flutter app.
2. [`quill_native_bridge_platform_interface`](https://pub.dev/packages/quill_native_bridge_platform_interface): The package that declares an interface that any platform package must implement to support the app-facing package.
3. The platform packages: One or more packages that contain the platform-specific implementation code. The app-facing package calls into these packages—they aren't included into an app, unless they contain platform-specific functionality:
* [`quill_native_bridge_android`](https://pub.dev/packages/quill_native_bridge_android)
* [`quill_native_bridge_ios`](https://pub.dev/packages/quill_native_bridge_ios)
* [`quill_native_bridge_macos`](https://pub.dev/packages/quill_native_bridge_macos)
* [`quill_native_bridge_linux`](https://pub.dev/packages/quill_native_bridge_linux)
* [`quill_native_bridge_windows`](https://pub.dev/packages/quill_native_bridge_windows)
* [`quill_native_bridge_web`](https://pub.dev/packages/quill_native_bridge_web)For more details, refer to [quill_native_bridge README](./quill_native_bridge/README.md).