[
https://issues.apache.org/jira/browse/LUCENE-8789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832959#comment-16832959
]
Tomoko Uchida edited comment on LUCENE-8789 at 5/4/19 1:27 AM:
---------------------------------------------------------------
Hi Uwe,
thanks for your comments and explanation. I have no strong feelings about that
so I will close this issue.
Personally I hope the minor glitches in the default look & feel for Windows
will be fixed in the future JDK (so that GUI developers do not have to worry
about that). The default Swing skin for Mac works fine on Retina display, just
like as native apps, and there are no noticeable glitches... don't get me wrong
I don't intend to blame the Windows UI.
bq. IMHO: You should change the BATCH file to use java.exe instead of
javaw.exe, a console window is opened anyways, but with javaw.exe you don't get
any console output when something wents wrong.
I might have made a mistake, but as far as stdout or stderr (I do not know
their names on windows) you can see them in the PowerShell or Command Prompt
window by deleting the current batch's first line {{@echo off}}.
I think it would be better that if we redirect the launch errors to a file,
same as the shell file does so. I will create another issue for this (I just
forgot that.)
was (Author: tomoko uchida):
Hi Uwe,
thanks for your comments and explanation. I have no strong feelings about that
so I will close this issue.
Personally I hope the minor glitches in the default look & feel for Windows
will be fixed in the future JDK (so that GUI developers do not have to worry
about that). The default Swing skin for Mac works fine on Retina display, just
like as native apps, and there are no noticeable glitches... don't get me wrong
I don't intend to blame the Windows UI.
> IMHO: You should change the BATCH file to use java.exe instead of javaw.exe,
> a console window is opened anyways, but with javaw.exe you don't get any
> console output when something wents wrong.
I might have made a mistake, but as far as stdout or stderr (I do not know
their names on windows) you can see them in the PowerShell or Command Prompt
window by deleting the current batch's first line {{@echo off}}.
I think it would be better that if we redirect the launch errors to a file,
same as the shell file does so. I will create another issue for this (I just
forgot that.)
> Use JGoodies' look&feel for Luke on Windows platform
> ----------------------------------------------------
>
> Key: LUCENE-8789
> URL: https://issues.apache.org/jira/browse/LUCENE-8789
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/luke
> Reporter: Tomoko Uchida
> Assignee: Tomoko Uchida
> Priority: Minor
> Attachments: LUCENE-8789.patch, Luke_ Lucene Toolbox Project - v9.0.0
> 2019_05_02 11_45_14.png, Luke_ Lucene Toolbox Project - v9.0.0 2019_05_02
> 11_53_37.png, sc_luke_java8.png, screenshot-1.png
>
>
> JGoodies Looks ([http://www.jgoodies.com/freeware/libraries/looks/]) is a
> Swing look&feel library for Windows platform.
> The main advantage of the library is (quoted from their home page):
> {quote}Our Windows look&feel focuses on a precise emulation on Windows XP,
> Vista, 7, 8, 8.1, and now Windows 10 in the following areas: menus, icons,
> colors, borders, fonts, font sizes, insets, and widget dimensions. It honors
> the screen resolution (low vs. high dpi) to adjust sizes, insets, and widget
> dimensions.
> {quote}
> The library works fine on Java11, relatively light weight (400KB), has no
> other external dependencies, and distributed under 2-Clause BSD License (see:
> [http://www.jgoodies.com/downloads/libraries/]).
>
> Actually, I forgot to include this when migrating Luke from the GitHub repo
> to Lucene project... :)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
