[jira] [Comment Edited] (LUCENE-2562) Make Luke a Lucene/Solr Module

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Comment Edited] (LUCENE-2562) Make Luke a Lucene/Solr Module

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/LUCENE-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16819550#comment-16819550 ]

Tomoko Uchida edited comment on LUCENE-2562 at 4/16/19 10:22 PM:
-----------------------------------------------------------------

Thanks for the comment, [~thetaphi].

I would like to add a notice, "For HiDPI graphics on Windows/Linux, Java 11 or grater is recommended to run the bundled GUI application Luke." to right after the first line ("Apache Lucene runs on Java 8 or greater.") in SYSTEM_REQUIREMENTS.txt.
{quote}You can print a warning (using the Constants.JDK_IS_MINIMUM_JAVA11 field) in the log file.
{quote}
OK, I will print some message in the footer bar or log file, if there are APIs to detect the display resolution.

Why I thought of adding notes to the user interface, users are not necessarily realize that the graphical problem relates to Java version they use. (Not long ago a user opened an issue titled "UI problem" in the github repo, even though I mentioned about this in the download page :) )


was (Author: tomoko uchida):
Thanks for the comment, [~thetaphi].

I would like to add a notice "For HiDPI graphics on Windows/Linux, Java 11 or grater is required to run the bundled GUI application Luke." to right after the first line ("Apache Lucene runs on Java 8 or greater.") in SYSTEM_REQUIREMENTS.txt.

> You can print a warning (using the Constants.JDK_IS_MINIMUM_JAVA11 field) in the log file.

OK, I will print some message in the footer bar or log file, if there are APIs to detect the display resolution.

Why I thought of adding notes to the user interface, users are not necessarily realize that the graphical problem relates to Java version they use. (Not long ago a user opened an issue titled "UI problem" in the github repo, even though I mentioned about this in the download page :) )

> Make Luke a Lucene/Solr Module
> ------------------------------
>
>                 Key: LUCENE-2562
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2562
>             Project: Lucene - Core
>          Issue Type: Task
>          Components: modules/luke
>            Reporter: Mark Miller
>            Assignee: Tomoko Uchida
>            Priority: Major
>              Labels: gsoc2014
>             Fix For: 8.1, master (9.0)
>
>         Attachments: LUCENE-2562-Ivy.patch, LUCENE-2562-Ivy.patch, LUCENE-2562-Ivy.patch, LUCENE-2562-ivy.patch, LUCENE-2562.patch, LUCENE-2562.patch, LUCENE-2562.patch, Luke-ALE-1.png, Luke-ALE-2.png, Luke-ALE-3.png, Luke-ALE-4.png, Luke-ALE-5.png, luke-javafx1.png, luke-javafx2.png, luke-javafx3.png, luke1.jpg, luke2.jpg, luke3.jpg, lukeALE-documents.png, screenshot-1.png, スクリーンショット 2018-11-05 9.19.47.png
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> see
> "RE: Luke - in need of maintainer": http://markmail.org/message/m4gsto7giltvrpuf
> "Web-based Luke": http://markmail.org/message/4xwps7p7ifltme5q
> I think it would be great if there was a version of Luke that always worked with trunk - and it would also be great if it was easier to match Luke jars with Lucene versions.
> While I'd like to get GWT Luke into the mix as well, I think the easiest starting point is to straight port Luke to another UI toolkit before abstracting out DTO objects that both GWT Luke and Pivot Luke could share.
> I've started slowly converting Luke's use of thinlet to Apache Pivot. I haven't/don't have a lot of time for this at the moment, but I've plugged away here and there over the past work or two. There is still a *lot* to do.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]