Rich Text Editors

FlutKit provides ready-to-use rich text editor wrappers to simplify form integration while keeping APIs consistent and easy to adopt. The editors expose minimal, predictable constructors, making them suitable for rapid UI assembly and documentation-driven usage.

QuillEditorCustom

QuillEditorCustom is a lightweight wrapper around Quill that focuses on sensible defaults and optional extensibility.

Constructor

QuillEditorCustom({
  Key? key,
  QuillController? controller,
  String? Function(String)? onValidate,
  double height = 400.0,
})

QuillEditorCustom({
  Key? key,
  QuillController? controller,
  String? Function(String)? onValidate,
  double height = 400.0,
})

Example Usage

QuillEditorCustom(
  height: 400,
)

QuillEditorCustom(
  height: 400,
)

Notes

• height is optional and defaults to 400.0 for consistent layout behavior.
• controller can be injected for advanced state control, but is not required for basic usage.
• onValidate integrates directly with form validation flows.

FleatherEditorCustom

FleatherEditorCustom follows the same API philosophy as QuillEditorCustom, ensuring a uniform developer experience across different editor engines.

Constructor

FleatherEditorCustom({
  Key? key,
  double height = 400.0,
  FleatherController? controller,
  String? Function(String)? onValidate,
})

FleatherEditorCustom({
  Key? key,
  double height = 400.0,
  FleatherController? controller,
  String? Function(String)? onValidate,
})

Example Usage

FleatherEditorCustom(
  height: 400,
)

FleatherEditorCustom(
  height: 400,
)

Notes

• Constructor parity with QuillEditorCustom reduces cognitive overhead when switching editors.
• Default values encourage fast prototyping without sacrificing customization options.

Design Rationale

• Minimal constructors lower the learning curve and make components easier to replicate and document.
• Consistent defaults ensure predictable UI behavior across the UI kit.
• Optional extensibility allows advanced users to inject controllers and validation logic without complicating basic use cases.

This approach aligns with FlutKit’s goal: components that are easy to adopt, easy to document, and safe to scale.

Demo

To see this component in action, please refer to the demo available under Forms → Editors