On Mon, 2012-01-09 at 17:20 +0100, Radek Vykydal wrote: > - Not sure where exactly does this belong, IMO it should be normal spoke, > perhaps accessible directly from some places (repo setup, network storage). I think if we don't automagically grab an IP from DHCP without prompting the user after the very first (language selection) screen, then the network screen should pop up there, but should also be accessible later for tweaking in the main hub (hub #1 / pre-install hub.) > - UI (xml) is taken from gnome-control-center in this first shot. > I can work on getting close to Mo's mockups, but > 1) I'd prefer the UI to look the same as the system, What do you mean? System = desktop version of it? > 2) we (rhel) will need functionality of NM Connection Editor (Configure button) > additionaly to basic ipv4 ipv6 config from the mockups (e.g. > Routes... -> Use this connection only for resources on its network, vlan configuration, > 802.1 X Security configuration, ...) > 3) we'll keep more code (nm-c-e) shared this way. Okay this is a good point. Are these something you get for "free" by using the shared code? > - Wireless configuration requires nm-applet as Security Agent (or writing our own) > Adding nm-applet to image is not easy - I tried it some months ago and it requires > quite a lot additional stuff - dbus, console kit... I could try to find my notes on > it if needed but I'd prefer using nm-applet atm (again - shared code). > > - I am thinking about adding Proxy configuration in similar way as in g-c-c. Proxy is weird because you potentially have two different ones? (Is that right?) A proxy to connect to the system that has the installation content vs a proxy the system will use post-installation to have a full internet connection? (Those could be two different networks, right?) The mockups definitely don't handle proxy right but I'm not sure the best way to do it. It does make sense to have it as an item in the network UI though. I don't know whether or not we should pull it from the 'installation source' screen as well? ~m _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
