On Fri, 23 Oct 1998, Jonathan Marsden wrote:
> On 23 Oct 1998, Jeroen Pluimers writes:
>
> >> If you leave the filter empty and "accept", you will get the whole
> >> thing. Linuxconf triggers this filter when a list has ... 15
> >> entries :-)
>
> > I really dislike the filter behaviour as it is implemented now.
>
> > Currently, the behaviour of the user interface depends on the number
> > of entries in the list.
>
> > That behaviour should not exist, as it makes the process more
> > difficult to comprehend and (worse) more difficult to monitor with
> > external (automated) scripting tools.
The html mode was never intended to be automated.
> I tend to agree here. The 'surprise' of a new screen at 15 users in
> the user accounts menus confused one of my novice sysadmins a couple
> of weeks back. He thought something had broken! The UI really ought
> not to radically change like this at some arbitrary number of entries.
>
> The magic value of 15 is apparently hard coded in several places in
> the code, too, rather than being a defined constant, which makes hacks
> like making it zero (always filtering) or making it 65535 (almost
> never filter) more awkward than would otherwise be necessary.
Wrong. This 15 is at two places in the code. Filtering is handled by the
DIALOG_RECORDS object (dialog/dialiste.cc). For user account, a more
complete filtering is available and the constant is used there also.
Changing this constant to a configurable value (in features) is roughly 10
lines of code, including storing,editing and retrieving the value.
> > I have thought about two solutions:
> >
> > - always have the filter dialog before you see anything of the list
> > - always show the list, with an extra edit box to specify the filter
>
> The second approach will be problematic when the list is really big,
> like 1000 entries... the HTML page generated would be huge and take a
> very long time to be sent, when it is not really wanted anyway.
> Sending the whole list before the user can choose to filter it defeats
> one important purpose of filtering, I would think. So, annoying
> though it will be for those with small numbers of entries, I suspect
> the only reasonable way to have filtering is to always have filtering.
> At least it is then consistent :-)
This is done especially for the html mode. For the GUI mode and ncurses
mode, we could very well have something completly different such as an
incremental search field (the list scroll as you type).
For the GUI, when doing remote GUI, sending the whole list is a problem.
Anyway, I will turn this into a configurable feature.
--------------------------
Jacques Gelinas
[EMAIL PROTECTED]
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]
