Agreed. I think apache is a preferable home.
The major change to Luke in providing a Luke core api is the need to be
remotable i.e. Use of an interface and serializable data objects used for args.
Gwt rpc should take care of the marshalling and I've used similar frameworks
for applet clients.
On 2010-07-12 09:14, John Wang wrote:
share FE with luke is defn a good idea.
any thoughts on putting webluke up on goog code or github?
Guys, if you want to move forward with webluke, I think it's better to
do this under Lucene contrib. The reason is that if there's a
substantial developmen
share FE with luke is defn a good idea.
any thoughts on putting webluke up on goog code or github?
-John
On Sun, Jul 11, 2010 at 10:22 PM, Mark Harwood wrote:
> I had concerns about the bloat the gwt compiler would add to the source
> distro.
> If of interest it could do with upgrading to the l
I had concerns about the bloat the gwt compiler would add to the source distro.
If of interest it could do with upgrading to the latest gwt. Ideally all Luke
front ends (swing/gwt/thinlet) would share the same back end api. Decoupling
from thinlet as done in this webluke code is the first step d
Mark:
This is a super useful tool!
Any plans of putting it under lucene contrib?
Thanks
-John
On Fri, Jul 9, 2010 at 7:26 AM, Mark Harwood wrote:
> See
> http://search.lucidimagination.com/search/document/63cef9e98692a126/webluke_include_jetty_in_lucene_binary_distribution
>
> There's a
See
http://search.lucidimagination.com/search/document/63cef9e98692a126/webluke_include_jetty_in_lucene_binary_distribution
There's a link to a zip file with source there which should still be available.
On 9 Jul 2010, at 15:14, Mark Miller wrote:
> Did the GWT version of Luke that Mark Har
Did the GWT version of Luke that Mark Harwood started ever get dumped to
JIRA or anything? All I can find is a link to a war, but not the source.
Mark? Anyone?
- Mark
-
To unsubscribe, e-mail: [email protected]
Fo
