mgarin
commented
6 years ago Problem 1: UI feels noticeably sluggish compared to other PLAFs (e.g. JTattoo). Not sure if that is due to advanced rendering?
It might be a bit slower than other L&F libraries, but that heavily depends on use case.
By looking at the screenshot and considering the second problem context - I suppose you are using lots of JInternalFrames in that application. If so - that might be the reason of "sluggish" UI. Basically all JInternalFrames are non-opaque on your screenshot which puts a lot of strain on the rendering process due to the way Swing renders things.
I didn't really optimize default JInternalFrame style for some "heavy" use cases, so no wonder it may perform poorly.
My recomendation - if you want to increase performance - adjust JInternalFrame style to make them use a simple rectangular shape and be opaque. Default JInternalFrame style (internalframe.xml) looks like this:
<!-- Internal frame -->
<style type="internalframe">
<component>
<opaque>false</opaque>
</component>
<painter>
<decorations>
<decoration>
<WebShape round="4" />
<WebShadow type="outer" opacity="0.35" width="10" />
<LineBorder color="170,170,170" />
<ColorBackground color="237,237,237" />
</decoration>
<decoration states="focused">
<WebShadow type="outer" opacity="0.7" />
</decoration>
<decoration states="maximized">
<WebShape round="0" />
<WebShadow type="outer" width="0" />
<LineBorder opacity="0" />
</decoration>
</decorations>
</painter>
<!-- Title panel -->
<style type="panel" id="title" extends="transparent" padding="0,5,0,0">
<!-- Title icon -->
<style type="image" id="icon" />
<!-- Title label -->
<style type="label" id="title" extends="shadow" padding="0,5,0,10">
<component class="com.alee.laf.label.WebLabel">
<horizontalAlignment>0</horizontalAlignment>
<maximumWidth>100</maximumWidth>
</component>
</style>
<!-- Buttons panel -->
<style type="panel" id="buttons" extends="grouppane">
<!-- Decoration control buttons -->
<style type="button" id="control" padding="3,5,3,5">
<component>
<focusable>false</focusable>
</component>
<painter>
<decorations>
<decoration>
<WebShape round="2" />
<WebShadow type="outer" width="5" />
</decoration>
</decorations>
</painter>
</style>
<style type="button" id="minimize" extends="control" />
<style type="button" id="maximize" extends="control" />
<style type="button" id="close" extends="control" />
</style>
</style>
<!-- Root pane -->
<style type="rootpane" id="rootpane">
<component>
<opaque>false</opaque>
</component>
<!-- Content pane -->
<style type="panel" id="content" extends="transparent" />
</style>
</style>You don't really need to adjust everything - just the JInternalFrame decoration, so something like this should do the job:
<!-- Internal frame -->
<style type="internalframe">
<component>
<opaque>true</opaque>
</component>
<painter>
<decorations overwrite="true">
<decoration>
<WebShape round="0" />
<LineBorder color="170,170,170" />
<ColorBackground color="237,237,237" />
</decoration>
<decoration states="maximized">
<LineBorder opacity="0" />
</decoration>
</decorations>
</painter>
</style>To clarify - this is an XML description of component style that can used with styling branch WebLaF version. Since you are writing an OS - you most certainly will need some custom styles, so this might be a good thing to start with.
There are two ways to use any separate style for the component (like the one i've shown above):
-
Provide it within a fully-implemented skin which can be described in XML - for example the default library light skin.xml, this way you can even change default component styles, but you will have to provide style definitions for all component types in your skin OR at least extend a skin that already has them.
-
Provide it as a skin extension for existing skin - for example demo application uses extensions for providing custom styles it uses, here is its default light skin extension.xml. Unlike skin - skin extension doesn't require you to provide style definitions for all component types, you can provide only styles you need. The downside of using extension - you cannot change default component styles or styles that are defined in the extended skin.
Either of ways would work for you, but if you go with an extension - you will need to specify your custom style identifier (StyleId) whenever you create component that should use it. It is easy with Web* components as they have custom constructors for providing StyleId and a bit more tricky with common J* components - here is a small guide on how it can be done.
You can check how demo application uses skin extensions in demo module sources:
stefan-reich
kirill-grouchnikov
Endogen
Hi,
I tried the latest 1.2.9 WebLAF snapshot in my OS, and it is almost working! Looks really good too.
Problem 1: UI feels noticeably sluggish compared to other PLAFs (e.g. JTattoo). Not sure if that is due to advanced rendering?
Problem 2: Some internal frames always grow whenever you try to resize them (never shrink). Notice the big window in the background which basically only contains a JTextArea in a JScrollPane. Other PLAFs allow these same windows to be resized normally.
Many greetings, Stefan BotCompany.de