gui/settings change idea for ease of use
-
Hey all, here's an idea that others have said "that's actually a really great idea" that i think i once pitched before, but i'll throw it out there again.
If i were a developer, i'd take care of it myself and submit it, but i'm not, so..the absolute biggest issue i see with the gui is inconsistency in the enable/disable, check/uncheck.
some settings are "check to disable", some are "uncheck to enable", and this can lead to configuration mistakes.
It would be incredibly helpful if a standard was adopted to eliminate the "check to disable" and "uncheck to enable";
put another way, all settings were "check to enable", and that was it.. if a setting is checked, its enabled, if unchecked its disabled and visa versa, and next to each setting a faint italicized note that said "default is: (checked or unchecked)" that way if the end user changes settings but forgets, they have an immediate reference.
it would make for a cleaner and more organized interface. afterall, the whole point of a gui is to make things easier and it seems logical that considering this is a security appliance, ease of use is paramount so as to avoid security problems due to configuration mistakes..
Just a thought
-
@jc1976 could you post a specific example or a few of them even better - this would make sure everyone is clear to what change you want to make.
I agree listing default is always a good idea for sure.
But also want to point out that it is the responsibility of the user/admin of the firewall to make sure the settings are how they want them. Regardless of something being disabled or enabled, or checked or unchecked, etc.
-
That's something we want to standardize eventually but it's a much bigger task than anyone realizes, and very easy to introduce new bugs in the process. Easy to think/suggest, but much more complicated to implement.
Overall we'd like to eliminate confusing/negative actions in options and move to a standard type of toggle control that makes it more obvious when things are on/off rather than checkboxes, too.
But for now we've at least been trying to do the right thing for new functions that get added when it's feasible.
