Re: Remove old LAFs from application and use new default LAF instead

2022-08-29 Thread Laszlo Kishalmi
Right now we are using all installed LaF-s to display in the combo box. 
You might create an SPI PR for a filtering interface. It's in the 
platform/core.windows module.


You might create something that checks/changes the following file on 
startup:

$USER_DIR/config/Preferences/laf.properties


On 8/29/22 00:43, Mike Hallan wrote:

Hi,
I would like to remove all LAFs so that the only ones available in 
MyApp are "FlatLaf Light" and "FlatLaf Dark".
I have set the default LAF in branding resource bundle for MyApp to be 
com.formdev.flatlaf.FlatLightLaf.
Ideally I want that if a user of a previous version of MyApp, who had 
been using "Windows" LAF, now starts the new new version of MyApp that 
MyApp won't find "Windows" LAF (because it no longer exists) and will 
therefore revert to using the new branded default of "FlatLAF Light".

Therefore:
1) Is is possible to remove all non-FlatLaf LAFs? Please tell me how 
to do it safely.
2) Will the application revert to using the branded default LAF if it 
can't find the previous LAF because it no longer exists in the 
application?

Thanks!


Warnings in pom.xml files of a multi-module project

2022-08-29 Thread Mark Eggers

Folks,

I have the following setup:

Windows 10 Pro - latest updates
JDK 17 (JDK 11, JDK 8 defined for legacy projects)
Netbeans 15 (voting candidate) installed from zip

I did not import any settings from NetBeans 14.

I have the following project structure to build with JDK 8:

Aggregator
|--- pom.xml
+--- Module_1
 | pom.xml
+--- Module_2
 | pom.xml
+--- Module_3
 | pom.xml

The parent definition in the modules are:


some.organization
Aggregator
1.0.0-SNAPSHOT


Module_n
1.0.0-SNAPSHOT
(jar or war)

where n = [1,2,3].

The Aggregator project:


some.organization
someConfig
2.1.0


Aggregator
1.0.0-SNAPSHOT
pom

In each of the modules, I get the following warning in my pom.xml files:

'parent.relativePath' of some.organization:Module_n:1.0.0-SNAPSHOT 
points to some.organization:Module_n instead of 
some.organization:Aggreagator, please verify your project structure.


This occurs for n = [1,2,3].

This also occurs with a zip-installed copy of NetBeans 14 on Windows.

I do not get this warning when running the same setup on Ubuntu 22.04 
with either the SNAP-installed NetBeans 14 or a zip-installed NetBeans 15.


What am I missing?

. . . just my two cents
/mde/

-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists



Remove old LAFs from application and use new default LAF instead

2022-08-29 Thread Mike Hallan
Hi, I would like to remove all LAFs so that the only ones available in MyApp 
are "FlatLaf Light" and "FlatLaf Dark".I have set the default LAF in branding 
resource bundle for MyApp to be com.formdev.flatlaf.FlatLightLaf.Ideally I want 
that if a user of a previous version of MyApp, who had been using "Windows" 
LAF, now starts the new new version of MyApp that MyApp won't find "Windows" 
LAF (because it no longer exists) and will therefore revert to using the new 
branded default of "FlatLAF Light".Therefore: 1) Is is possible to remove all 
non-FlatLaf LAFs? Please tell me how to do it safely.2) Will the application 
revert to using the branded default LAF if it can't find the previous LAF 
because it no longer exists in the application?Thanks!