Hello, perhaps a bit off-topic but I just like to point out how complicated it can become. We should have the most complicated case in mind when we really want to get a design which can be used for all hardware config modules and not only a simple design which only works for simple hardware config and all complicated hardware config ends up in a mess of arbitrary addons (like arbitrary popups) and arbitrary workarounds because of a too simple basic design. On Apr 20 13:18 Michal Zugec wrote (shortened):
for network relation is 1:1, for printer it's 1:N
Actually for printer it's even more complicated because one printer can have N queues and additionally M queues can build up one class. For example: printer1 has queues bw1, color1 and photo printer2 has queues bw2 and color2 printer3 has queue bw3 queues bw1, bw2 and bw3 build up class bw queues color1 and color2 build up class color A class is some kind of meta configuration, i.e. a configuration which is not based upon hardware but based upon other configurations. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse-usability+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-usability+help@opensuse.org