Implement ChipView for the search

[koppor]

Currently, we distinguish between basic and grammar-based search.

It was proposed to reimplement the GUI for search as follows:

.

Keywords: search autocompletion javafx

See also discussion at JabRef#7391 (comment)

[koppor]

In case the query is a valid lucence syntax, use that query. If the query is not a Lucene query, just take each keyword and do an OR search. -- Maybe indicate with a backbround color that the search syntax is not correct.

[calixtus]

@koppor created a pr draft about the basic integration of a lucene parser in jabref (JabRef#8206).

[btut]

If the query is not a Lucene query, just take each keyword and do an OR search.

I would argue that an AND search would be more appropriate, except if one field appears twice. So:

author=koppor author=btut -> OR search
author=koppor title=JabRef -> AND search

[koppor]

@btut Do you know what Lucene / Elastic search is doing when using "as is"? (Maybe with a reference?)

[ThiloteE]

I would just like to shortly state here that there have been voices to implement fine grained extended search capabilities in issues: JabRef#4237, JabRef#6185 and JabRef#7996. If and how these would be compatible to the chip-view type of search outlined here and in JabRef#7806 or the field autocompletion feature in JabRef#7423 is something to ponder about.

I just don't want these other topics to be overlooked, forgotten, since Koppor/Jabref and Jabref/Jabref are two different repositories.

[btut]

@btut Do you know what Lucene / Elastic search is doing when using "as is"? (Maybe with a reference?)

From the lucene documentation:
The OR operator is the default conjunction operator.

[koppor]

Note that there was another UI proposal: JabRef#7423. Maybe the proposal at JabRef#7423 is a next step, if we got JabRef#8356 merged.