On Mon, 2010-02-08 at 19:00 -0600, Brian Cameron wrote: > gnome-session-worker: > > > > Currently gdm-session-worker supports several working states: > > > > > SETUP_COMPLETE->AUTHENTICATED->AUTHORIZED->ACCREDITED->SESSION_OPENED->SESSION_STARTED > > > > For gnome-screensaver, we need to add some new states in the state > diagram: > > > > > SCREENSAVER_SETUP_COMPLETE->SCREENSAVER_AUTHENTICATED->SCREENSAVER_AUTHORIZED. > > Is it really necessary to define new states? Since GDM uses GObject > object-oriented techniques, I would think that it might make more > sense > to manage this via making two subclasses of a base class. The > lockscreen subclass could just have no-ops for the states that are not > meaningful in the lockscreen case. > > Brian,
Since gdm-session-worker handles the DBus signals of org.gnome.DisplayManager.Session in a state transition function, It looks natural to add a new state transition function with more states. It may look like monitoring the new signals come from Screensaver org.gnome.ScreenSaver. Jeff _______________________________________________ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
