Hi Stephan,
I understand your preference for the speed of client-side filtering. Sadly
that's only the case for very small data-sets. Practical Plants has over 7,000
results to filter, so clientside filtering would require an unacceptably large
query upfront.
I'm not at all surprised the
Hi Yury,
1) You can specify a default query to run when it first loads. For practical
plants it queries all pages with [[Show on main page search::Yes]], so we can
define a few key plants to show upfront
2) I don't understand this question! Could you clarify?
Thanks for the kind words about the
very cool!
And I also like your mediawiki-skin. Is that available somewhere?
regards,
Bernhard
- Ursprüngliche Mail -
For the wiki I develop, I was interested in using the filtered output
format, but needed the results to be loaded dynamically when filters
were changed, as I have
Hey,
Would there be any demand for this?
Yes, having dynamic filtering and continuation for result formats is pretty
high on the wish list for result formats in general. Which is why people
are so excited about the filtered format. I however have two concerns about
this format:
* It seems to
Hi,
On 15 October 2012 12:10, Jeroen De Dauw jeroended...@gmail.com wrote:
Would there be any demand for this?
Yes, having dynamic filtering and continuation for result formats is pretty
high on the wish list for result formats in general. Which is why people are
so excited about the
Hi Andru!
It looks terrific and we really need similar AJAX-feature for fitered
format.
1) Do I understand correctly that by default (with no filters turned on)
you show some amount of results (say 20 results)?
2) a question to developers: how fast are the count queries? Maybe it's
good to use
