Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8344643

RichTextArea Control (Incubator)

XMLWordPrintable

    • Icon: CSR CSR
    • Resolution: Unresolved
    • Icon: P2 P2
    • tbd
    • javafx
    • None
    • source, binary, behavioral
    • minimal
    • This feature is being delivered as an incubator module. No existing public API will be changed.
    • Java API, File or wire format
    • JDK

      Summary

      Incubates a RichTextArea control for displaying and editing of rich text that can be styled in a variety of ways, capable of working with large documents.

      Problem

      JavaFX lacks a dedicated rich text area control, resulting in a functional gap in relation to Swing. The new RichTextArea control intends to bridge this gap.

      The main design goal is to provide a control that is complete enough to be useful out-of-the box, as well as open to extension by the application developers. The benefit of providing such a control as a part of the core platform is not just adding support for rich text, but also in taking care of many intricate details required for such support, making it easier for third party developers who decide to extend the basic functionality.

      Solution

      The incubator module jfx.incubator.richtext provides two Control classes: RichTextArea and CodeArea, the latter optimized for a single-font use case such as code editor.

      See https://github.com/andy-goryachev-oracle/Test/blob/main/doc/RichTextArea/RichTextArea.md

      Specification

      Unified diff: TBD

      Javadoc: https://cr.openjdk.org/~angorya/RichTextArea/javadoc/

      Behavior: https://github.com/andy-goryachev-oracle/jfx/blob/8301121.RichTextArea/doc-files/behavior/RichTextAreaBehavior.md

      The detailed changes. Acceptable normative formats include inline patches, attached webrevs, and attached specdiffs. The names of attached files are recommended to include a bug id. References to external webservers, such as http://cr.openjdk.java.net/, can be provided as informative supplements for the convenience of reviewers, but must be accompanied by a normative form of the specification directly associated with the CSR issue to satisfy archival purposes.

            angorya Andy Goryachev
            angorya Andy Goryachev
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: