On 7/19/2013 10:29 AM, SUJIT PAL wrote:
I am not sure what the Solr4 admin tool uses
Solr's UI since 4.0 is javascript and requires a browser to run. In earlier versions it was JSP, built server-side but still displayed in a browser. This is reasonable because Solr is a service application that is typically accessed over the network. Its user interface is browser-based. Solr doesn't present a user interface in the same way as a "standard" program like a spreadsheet or a word processor.
The kind of UI choices (like Pivot) that are being talked about for Luke are Java APIs that build OS GUI dialog boxes for "standard" programs. If you try to compare that with the Solr UI, you're comparing apples and oranges.
Luke is a standalone application that works on Lucene indexes, independent of the application (Solr or user-created) that built them. My opinion, and I'll let you decide whether it's humble or otherwise:
First, we need to get Luke fully integrated into the Lucene codebase as a module. That module must build the standalone application that we know and love.
Next, if Luke is not already modular enough so that it can work as a library, the modularization process will have to be completed. If this is required, it likely to be a very hairy change.
I think that trying to replace the Luke functionality in Solr with calls to a Luke library would be premature before the steps above are completed.
Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
