<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=utf-8">
<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;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
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="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Iosevka Fixed SS16"">I agree with John on the subject of modena and flat themes.<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"">From the platform point of view, I would think we should focus on *<b>enabling*</b> the complex themes by providing the necessary tools. It is currently
<i>possible</i> to create e.g. a dark theme, or react to platform preferences' changes, by, for instance, dynamically generating a stylesheet - but the process is not easy.<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"">Adding variables might help more than anything else, in my opinion. Maybe there is a way to publish platform preferences via another set of variables available to CSS.<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"">To be specific, I see the following features that should be available to the CSS designer:<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"">1. consistent padding for compact/roomy user preference<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Iosevka Fixed SS16"">2. derived colors for dark/light/custom themes (I suspect the currently used derive() will not be sufficient)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Iosevka Fixed SS16"">3. base font<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Iosevka Fixed SS16"">4. component sizing which depends on the base font size<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"">On topic of modena.css, I think we may want to consider updating the stylesheet to support the dark theme as our first priority, leaving designing more elaborate custom theme
to the public.<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"">What do you think?<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>
<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 John Hendrikx <john.hendrikx@gmail.com><br>
<b>Date: </b>Tuesday, December 3, 2024 at 02:47<br>
<b>To: </b>openjfx-dev@openjdk.org <openjfx-dev@openjdk.org><br>
<b>Subject: </b>Re: A new theme for JavaFX<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">I think we can leave this to the community as FX provides sufficient<br>
means to have a 3rd party provide a theme. There are other themes out<br>
there, and they can be updated with new functionality once it becomes<br>
available in a FX version they're willing to support. Perhaps this one:<br>
<a href="https://github.com/mkpaz/atlantafx">https://github.com/mkpaz/atlantafx</a><br>
<br>
I also don't think modena looks that dated. As it is pretty smart with<br>
colors (using variables and ladders to select contrasting colors),<br>
adjusting just its base colors may be sufficient to have it work nicely<br>
as a dark theme.<br>
<br>
The modern "super flat almost borderless" look is IMHO counterproductive<br>
and often annoying as it is hard to see where one thing ends and another<br>
thing starts.<br>
<br>
--John<br>
<br>
On 03/12/2024 01:03, Michael Strauß wrote:<br>
> Continuing the discussion that was started in the CSS media queries thread:<br>
><br>
><br>
> On Mon, Dec 2, 2024 at 11:55</span><span style="font-size:11.0pt;font-family:"Arial",sans-serif"> </span><span style="font-size:11.0pt">PM Kevin Rushforth<br>
> <kevin.rushforth@oracle.com> wrote:<br>
>>> I'm thinking a bit bigger than just "Modena Dark". Since JFX 19, we've<br>
>>> added focusVisible, platform preferences, CSS transitions, and now<br>
>>> hopefully media queries. After this is done, I think we should<br>
>>> leverage all of those new features, and create a bold new theme for<br>
>>> JavaFX that feels at home in the year 2025.<br>
>> Depending on the scope, that's a pretty ambitious goal. :) Were you<br>
>> thinking of something derived from Modena (e.g., a "Modena 2025") that<br>
>> incorporates all of those things and maybe a few other tweaks? Or are<br>
>> you thinking a brand new "from scratch" theme? Based on past experience<br>
>> (the switch from Caspian to Modena in FX 8), the latter will require<br>
>> quite a lot of work, and someone with a good artistic eye and attention<br>
>> to detail to drive it. I expect it would be a fairly long process and<br>
>> require a *lot* of testing.<br>
>><br>
>> Anyway, that doesn't need to slow down this feature. This feature would<br>
>> help with either approach. And application developers would be able to<br>
>> take advantage in their own stylesheets before that.<br>
><br>
> While I think that Modena is a nice-looking theme, I can't help but<br>
> think that it's a nice-looking theme for the mid-2010's. It dates the<br>
> JavaFX platform, and its look and feel is the first thing that people<br>
> see when they interact with JavaFX (either with the framework itself,<br>
> or with user-facing applications). The UI landscape has evolved quite<br>
> a lot in the past decade. I think there is great value in completely<br>
> modernizing the JavaFX user experience, firmly and boldly moving it<br>
> forward, and making the framework attractive again for a new<br>
> generation of developers.<br>
><br>
> Ideally, this is more than a "Modena 2025" refresh. I completely agree<br>
> that this is a big project, and it requires talented people to pull it<br>
> off. However, there _are_ talented UI designers and developers in the<br>
> JavaFX community. I hope this will start a discussion on how a modern<br>
> JavaFX user experience can look like, and how we'd be able to achieve<br>
> it.<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>