There are currently separate views for the spool list: One for the spool tab and one for the spool search that appears when clicking the "..." button in the sidebar or when searching for a template. (There is a third one that shows the selected spools for the tools, but that is a different usecase.)
The two views do basically the same from a user perspective. From a developer perspective they are very different though: The tab loads from the database every time a filter is applied while the sidebar works on the spools loaded to memory when the page was loaded. This not only causes some glitches (one of them being #43) when both are used, but also causes higher maintenance and worse code readability.
The sidebar list has a text filter (search) though. This is implemented in JavaScript and hides filtered spools. There currently is no text-based search for the database, so the spools tab does not have a text filter (search). (See #22)
The tab view on the other hand has pagination. The sidebar will just always show all the spools. That's probably the reason why it has a text filter, however, it is desirable to have both functionalities in both views.
To solve issues causes by operating on a spool list in memory and avoid updating the list in memory, both views could be unified, always loading directly from the database and offering pagination and text filtering (text search) in all places. This requires implementing such a filter for the spools tab view first.
There are currently separate views for the spool list: One for the spool tab and one for the spool search that appears when clicking the "..." button in the sidebar or when searching for a template. (There is a third one that shows the selected spools for the tools, but that is a different usecase.)
The two views do basically the same from a user perspective. From a developer perspective they are very different though: The tab loads from the database every time a filter is applied while the sidebar works on the spools loaded to memory when the page was loaded. This not only causes some glitches (one of them being #43) when both are used, but also causes higher maintenance and worse code readability.
The sidebar list has a text filter (search) though. This is implemented in JavaScript and hides filtered spools. There currently is no text-based search for the database, so the spools tab does not have a text filter (search). (See #22)
The tab view on the other hand has pagination. The sidebar will just always show all the spools. That's probably the reason why it has a text filter, however, it is desirable to have both functionalities in both views.
To solve issues causes by operating on a spool list in memory and avoid updating the list in memory, both views could be unified, always loading directly from the database and offering pagination and text filtering (text search) in all places. This requires implementing such a filter for the spools tab view first.