Quote:
Originally Posted by kovidgoyal
I'm not the greatest fan of the cumulative behavior. It's surprising, different from all the rest of the searching mechanism and likely to generate why does this work this way type bug reports.
|
The lastest experiment doesn't have cumulative behavior other than expected, where search terms in the search, including summarize_booklist, affect subsequent search term evaluation. Said another way, search expressions, including summarize_booklist, are reproduceable. Running the expression again gives the same answer, assuming no context changes such as VLs, sorts, and underlying data changes.
Quote:
|
If I understand correctly, the use case is basically generating a "report" of some kind over your books? Like series with the last book or whatever? Might be better to have a separate reports tool like there is in the editor, in a popup rather than trying to shoehorn it into the search + book_list view.
|
I will look at this.
The "pro" is avoiding adding "stuff" to existing mechanisms.
At first blush the "cons" are:
- Being required to create a query language for the report tool that duplicates the existing search, sort, and VL mechanisms.
- Not having the rest of calibre easily available, such as book details, pin views, column ordering, column icons, and plugins.