Paul Elschot wrote:
Would it be possible to privide such a GUI automatically
(by introspection) given a set of Query classes of which objects
can be mixed to form a query?
Certainly possible - I've seen app servers with automatic GUI test
clients which can introspect an EJB interface and l
On Sunday 04 December 2005 05:17, Yonik Seeley wrote:
> On 12/3/05, Paul Elschot <[EMAIL PROTECTED]> wrote:
> > Indeed, this is a disadvantage of the "function call" syntax.
>
> It depends on the langage. Take Python for example:
>
> >>> def foo(a,b): print a,b
> >>> foo(1,2)
> 1 2
> >>> foo(a=1
On Dec 4, 2005, at 6:52 AM, Paul Elschot wrote:
I tried rewroting the XML query in exactly this way, with a
few property=.. constructs:
boostingQuery(
matchQuery=moreLikeThis(
percentTermsToMatch="0.25",
docId="44",
On Sunday 04 December 2005 15:26, Erik Hatcher wrote:
>
> On Dec 4, 2005, at 6:52 AM, Paul Elschot wrote:
> > I tried rewroting the XML query in exactly this way, with a
> > few property=.. constructs:
> >
> > boostingQuery(
> > matchQuery=moreLikeThis(
> > percentTer
Following up on the (Span)RegexQuery topic, I've started working on
moving this code to contrib/regex so that it can leverage various
regex implementations. I'm making a generic interface that currently
(though subject to change) has these methods:
void compile(String pattern);
boolean
On Dec 4, 2005, at 11:02 AM, Paul Elschot wrote:
Are there XML editors that can limit their output to a given
stylesheet?
In that case one only needs to predefine a style sheet for queries.
Yes, there are many sophisticated XML editors. I'm not quite sure
where you're going with this thou
I think I'm with Erik on this - I generally don't see end users keen to
type anything other than "words with spaces" as queries.
I do see them commonly using GUI forms with multiple inputs and behind
the scenes application code assembling the query - the same way just
about every web app in the
On Sunday 04 December 2005 22:32, markharw00d wrote:
> I think I'm with Erik on this - I generally don't see end users keen to
> type anything other than "words with spaces" as queries.
I think/hope that XSL allows a simplified front end that would fit
my needs.
> I do see them commonly using G
[ http://issues.apache.org/jira/browse/LUCENE-473?page=all ]
Erik Hatcher closed LUCENE-473:
---
Fix Version: 1.9
Resolution: Duplicate
> Fix to let Searcher.close() and other methods accessible from c++ code
> --
[ http://issues.apache.org/jira/browse/LUCENE-324?page=all ]
Erik Hatcher resolved LUCENE-324:
-
Fix Version: 1.9
Resolution: Fixed
Assign To: Erik Hatcher (was: Lucene Developers)
Ray - 谢谢你 (let's see if JIRA can handle Chinese :) Sorr
[ http://issues.apache.org/jira/browse/LUCENE-324?page=all ]
Erik Hatcher closed LUCENE-324:
---
Assign To: (was: Erik Hatcher)
> org.apache.lucene.analysis.cn.ChineseTokenizer missing offset decrement
> --
Hi All,
I think this release issue died out again. I noticed an increase in
commit activities recently! I've also noticed the release plan for
2.0 on the wiki. Does current 1.9 already meet the criterias for 2.0?
At least API-wise? If so, is it possible to make ways for a release?
at least mar
12 matches
Mail list logo
