Short description
2008-07-11
It would be good to have an option for <<FullSearch(...)>> to output results not like:
1. firstresult 2. secondresult 3. ...
but as a comma separated text:
firstresult, secondresult, thirdresult, ...
It would consume much(!) less space on the screen. For example a result list with 10 items consumes already a large fraction of the screen, while ten pagetitels could easily fit to one or two lines.
I would like to dynamically show pages from a Category on the starting page. The list output destroys the readability of the starting page, while non-list output would give a very good overview of whats going on in Categories with 3 to 50 member pages...
I too would like this feature. I've looked through the source but got very confused in the interaction between search._getPageList() and the formatter. Will keep looking.
(Oops, pageList() is actually MoinMoin.search.results.SearchResults.pageList().)
Has anyone implemented this feature?
-- Russell
Have a look at ListPages and add a patch for another list_type. -- ReimarBauer 2011-03-20 08:45:19
Thank you. I'll take a look through that. -- RussellSteicke 2011-03-20 11:28:19
That was a good start, and I can get a comma separated list, but ListPages only searches page titles. <<ListPages(category:Foo, comma_list)>> doesn't work as I hoped. I'll have to get the search code from FullSearch and massage that into a form that ListPages will like. -- RussellSteicke 2011-03-20 13:59:08
I'm also trying to improve the search output with ImprovedMoinSearch and the bundled PageListPlus macro, which could be extended to produce a comma-separated list of titles. What would be really nice is a template-driven search macro which references some template page containing the general form of each result with placeholders that could be replaced by the actual result values, but for now I'm using a format string instead. -- PaulBoddie 2011-03-21 18:35:58
That can be implemented in moin-2.0