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

Tomoko Uchida edited comment on LUCENE-2562 at 7/25/18 10:13 AM:
-----------------------------------------------------------------

Hi,

I found a similar issue in ASF LEGAL.

"Should GPL+CPE move to Cat B?"
 [https://issues.apache.org/jira/projects/LEGAL/issues/LEGAL-336]

Seems the answer is definitely NO.

When sticking to JavaFX we probably cannot donate Luke to Apache products, 
though I like sophisticated JavaFX API and beautiful components.
 I'm now planning to port the UI layer from JavaFX to Swing.

Luke is getting more and more popular in GitHub users (dear committers, how 
many of you use Luke now?) I don't know why a desktop application gains 
popularity in the web browser era. But if many users need Luke, I think it 
should become an official member of Lucene in any form...


was (Author: tomoko uchida):
Hi,

I found a similar issue in ASF LEGAL.

"Should GPL+CPE move to Cat B?"
https://issues.apache.org/jira/projects/LEGAL/issues/LEGAL-336

Seems the answer is definitely NO.

When sticking to JavaFX we probably cannot donate Luke to Apache products, 
though I like sophisticated JavaFX API and beautiful components.
I'm now planning to port the UI layer from JavaFX to Swing.

Luke is getting more and more popular in GitHub users (dear committers, how 
many of you use Luke now?) I don't know why a desktop application gains 
popularity in the web browser era. But if many users need Luke, I think it 
should become an official company of Lucene in any form...

> Make Luke a Lucene/Solr Module
> ------------------------------
>
>                 Key: LUCENE-2562
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2562
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Mark Miller
>            Priority: Major
>              Labels: gsoc2014
>         Attachments: LUCENE-2562-Ivy.patch, LUCENE-2562-Ivy.patch, 
> LUCENE-2562-Ivy.patch, LUCENE-2562-ivy.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
>
>          Time Spent: 10m
>  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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to