A supported public API for HTML Editor customization [#RT-21268]

[Slavko Scekic]

Hi,

As instructed by Johnatan, I've broke down this issue on four separate
ones. The first (htmlText as JavaFX Property) is already submitted, so I've
omitted it. Here are the three new ones:
Allow HTML Editor's toolbar customization
(RT-21280)<http://javafx-jira.kenai.com/browse/RT-21280> Provide
a mechanism to limit the number (and type) of available fonts in HTML
Editor (RT-21281) <http://javafx-jira.kenai.com/browse/RT-21281> Allow
selecting default HTML Editor's font from
code<http://javafx-jira.kenai.com/browse/RT-21282>(RT-21282, open)With
regards,
Slavko

On Thu, May 3, 2012 at 5:07 AM, John C. Turnbull <ozemale at ozemail.com.au>wrote:

> +1
>
> I agree wholeheartedly with this suggestion.  The HTMLEditor as it
> currently
> stands is not particularly useful and offers no means of configuration.
>  The
> use case where you just want to display some HTML text without the editor
> controls and without the overhead of instantiating a full-blown WebKit
> browser cannot be ignored.
>
> -jct
>
> -----Original Message-----
> From: openjfx-dev-bounces at openjdk.java.net
> [mailto:openjfx-dev-bounces at openjdk.java.net] On Behalf Of Slavko Scekic
> Sent: Tuesday, 1 May 2012 06:25
> To: openjfx-dev
> Subject: A supported public API for HTML Editor customization [#RT-21268]
>
> Hi all,
>
> I've filed a new JIRA request concerning the HTML Editor control. Please
> take a look <http://javafx-jira.kenai.com/browse/RT-21268> and make
> contributions. Here it is:
>
> I dear say that everyone who's used the HTML Editor control will agree that
> it is not really adequate for serious use. So, I propose several
> enhancements to the API:
>
> 1) Make HtmlText an ObservableValue - CRUCIAL.
> 2) Allow toolbar customization. At minimum, this should include
> disabling/enabling or hiding/showing available controls.
> 3) Provide a mechanism to limit the number (and type) of available fonts.
> This is essential for web content production (web-safe fonts are still
> considered a good design practice, but also for the theme-specific fonts),
> and when preparing content for external components, like JasperReports.
> 4) Allow selecting default font from code.
>
> Thanks,
> Slavko
>
>