<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
@font-face
{font-family:"Iosevka Fixed SS16";
panose-1:2 0 5 9 3 0 0 0 0 4;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Aptos",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Iosevka Fixed SS16";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Iosevka Fixed SS16"">I wonder if this could be done as an incubator module, or hidden behind an experimental system property.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Iosevka Fixed SS16""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Iosevka Fixed SS16"">-andy<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Iosevka Fixed SS16""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Iosevka Fixed SS16""><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">openjfx-dev <openjfx-dev-retn@openjdk.org> on behalf of Kevin Rushforth <kevin.rushforth@oracle.com><br>
<b>Date: </b>Monday, August 26, 2024 at 14:40<br>
<b>To: </b>openjfx-dev@openjdk.org <openjfx-dev@openjdk.org><br>
<b>Subject: </b>Re: New CSS parser for JavaFX<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt">Deprecating the existing API is an interesting idea, but with such a
<br>
large API surface it will be difficult to show that no application is <br>
using it.<br>
<br>
-- Kevin<br>
<br>
<br>
On 8/26/2024 2:35 PM, John Hendrikx wrote:<br>
><br>
> On 26/08/2024 22:42, Michael Strauß wrote:<br>
>>> can we create stylesheets programmatically without parsing (i.e. <br>
>>> construct the token tree directly)?<br>
>> Maybe, but `Stylesheet` and its constituent classes really seem like<br>
>> exposed implementation details of JavaFX. I would rather deprecate<br>
>> their use and remove them from the public API eventually.<br>
><br>
> I'm pretty convinced of that as well. The whole CSS API seems to have <br>
> been put in place to allow use of binary stylesheets (to perhaps <br>
> load Modena .5 seconds faster?), it doesn't seem to serve much of a <br>
> function beyond that. I haven't found a use for any of these classes <br>
> and the API surface they expose.<br>
><br>
> For example, I implemented a LESS parser that I can use with JavaFX, <br>
> and the CSS API was absolutely no help there (what is the point of <br>
> being able to create a StyleSheet when I can't "set" it on a Scene?) <br>
> -- instead I've just resorted to writing the LESS output to memory <br>
> buffers, and pointing my stylesheet properties directly to these <br>
> (using "data:text/css;charset=UTF-8;base64," URL's -- thanks for <br>
> whoever mentioned "data" URL's, I was writing these to temporary files <br>
> before that...).<br>
><br>
> The CSS API classes are also full of observable properties, which <br>
> seems a rather odd decision given that a Stylesheet is probably far <br>
> better represented as something immutable. Imagine assigning a <br>
> Stylesheet type to Scene (something that isn't possible, so it is <br>
> unclear what the purpose of this class is), then having the CSS engine <br>
> observe almost every aspect of this Stylesheet, just in case someone <br>
> decides to add a new Selector somewhere programmatically... it would <br>
> be incredibly complicated to "act" on such a change correctly, <br>
> requiring no doubt thousands of lines of code, that will likely never <br>
> ever be used in any FX application (well perhaps if you are writing a <br>
> Stylesheet editor, but that's hardly a use-case worth supporting just <br>
> in case...)<br>
><br>
> --John<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>