On Fri, 2008-11-07 at 08:58 -0800, Rusty Lynch wrote: > On Wed, 2008-11-05 at 19:29 -0700, Liu, Raymond wrote: > > Hi guys
> I don't see anything in your design document that explains why we need > to duplicate (and extend) the existing libgmenu functionality. > > Why not limit the scope of genesis to the second part of your > introduction? > I think we should go further and limit it to the following goal listed in the document: "Application crash and hang-up detection, system resource starving detection/quota enforcement." (The launching aspects are not interesting since the UI shell will handle launching itself.) This goal has a lot of scope for interesting, useful and tricky things and this is what Genesis should be about. The main thing that is going to be necessary is the resource limiting for running processes (not launched applications, since programs can fork off and do things themselves). This is especially important when programs may not be "trusted". You'd probably want to talk to some of the kernel / plumbing guys to find out if the kernel has any resource limit / notification infrastructure that can be used to drive this. On the crash detection front we'll want some kind of solution like apport / bug-buddy / google breakpad to support the sending of backtraces back to developers. We'll also need some way of ensuring that if the components of the UI shell go away they'll get restarted. On the desktop this is handled by gnome-session. Maybe this is something Genesis may also be useful for but right now we don't have a clear idea of how the UI shell components fit together to require this. Hope that's helped. Regards, Rob _______________________________________________ Moblin dev Mailing List [email protected] To manage or unsubscribe from this mailing list visit: https://lists.moblin.org/mailman/listinfo/dev or your user account on http://moblin.org once logged in. For more information on the Moblin Developer Mailing lists visit: http://moblin.org/community/mailing-lists
