Comment 3 for bug 36797

tested on final Dapper. There are still three issues with this UI if we are shooting for being ultra user-friendly:

1) 127.0.0 is the default entry for a network printer scan, obviously no network printer could be connected to that subnet. The app should automagically pull the current subnet and use that as the default entry. I doubt most people have any idea what a subnet is (see #2)

2) The box for entering a subnet is too small to see the entire subnet and while there is basic data validation, the error message is useless. A better approach would force an entry into a proper subnet, perhaps by breaking the field into three fields and modifiying the validation error message to say something like "Invalid subnet address. Valid subnet addresses are in this format: x.y.y where x is a number between 1 and 255 and y is a number between 0 and 255. For example, 192.168.0 or 10.0.0. Typical subnets for home networks are 192.168.0 or 192.168.1"

Thinking about it more, it doesn't seem to make sense to require manual entry of the subnet at all. If the subnet can't be detected there is something wrong with the network and the scan will fail anyway.