answered 2023-11-17 01:52:53 +0800

AndreiArdei
111 ● 3

Hey! So we also had the same issue in our implementation, some searchboxes have over 9k elements and searching was dead slow. I'm of the opinion that going back and forth between the client and the server will only slow it down. Looking at what made the client side so slow was the fact that ZK was trying to delete DOM objects that were not matching the criteria causing the DOM to recalculate. What I did instead was override this and instead just mark elements as invisible with CSS (display none). For us that is a huge improvement. Went down from a key stroke taking ~13 seconds on a 9K dataset to now being ~1 second (of course it now depends on the client, with firefox being noticeably faster)

answered 2023-10-24 14:57:53 +0800

hawk
3205 ● 1 ● 5
http://hawkphoenix.blogsp...

updated 2023-10-24 14:58:07 +0800

There are several options:

SimpleListModel

see https://www.zkoss.org/wiki/ZKComponentReference/Input/Searchbox#Model you can store all data in a SimpleListModel, it will filter data at the server side

add data dynamically

• assign an empty ListModelList first,
• listen to onSearching and add the matched data into the ListModelList