2012-12-17, 12:02
Got some ideas for GUI implementation "done right".
For me it would be a nice thing to manage settings for WOL Servers in Power saving (see http://oi47.tinypic.com/e0okg5.jpg ). In my opinion the best approach would be to add, edit or delete servers to a "wol list" with additional settings for each entry (MAC, ip, timeout, etc) and handle the WOA active / disabled state in the "Add shares" menu (see https://dl.dropbox.com/u/28792047/xbmc/s...hot006.png ). By the global "wol list" the WOL active state can be hidden in GUI, if the share is not on a server in the "wol list". If the server is on the "wol list" the according connection parameters are loaded to send the wol packet.
This keeps the GUI clean for average consumers and for experienced users everything can be "done right".
What do you think about that?
For me it would be a nice thing to manage settings for WOL Servers in Power saving (see http://oi47.tinypic.com/e0okg5.jpg ). In my opinion the best approach would be to add, edit or delete servers to a "wol list" with additional settings for each entry (MAC, ip, timeout, etc) and handle the WOA active / disabled state in the "Add shares" menu (see https://dl.dropbox.com/u/28792047/xbmc/s...hot006.png ). By the global "wol list" the WOL active state can be hidden in GUI, if the share is not on a server in the "wol list". If the server is on the "wol list" the according connection parameters are loaded to send the wol packet.
This keeps the GUI clean for average consumers and for experienced users everything can be "done right".
What do you think about that?
