Rob Bradford wrote: > I'd be concerned about having a central daemon that loads in the desktop > files, parses them and then communicates with the details to a client. I > can only typically imagine that only one client (the launcher) will care > about displaying available applications. If you have to have a copy of > all the data in both the client and the daemon you've just wasted memory > with the addition of e.g. rpc overhead.
I would have to agree; the launcher, as the primary user, is best placed to hold the application database to avoid doing RPC; if anything else absolutely needs access to that database, it can then RPC the launcher. However, if the launcher UI is done properly, there will be no need for secondary ones; I would go as far as to say that a need for having multiple launchers is symptomatic of suboptimal UI design, and it should not be necessary to cater for this in the API. > An alternative strategy i'd like to suggest for genesis is to focus only > on the launching and life cycle and that the api for client (i.e. > launcher) would be a very simple "run this full path" command. The > handling of the .desktop files would only be for the launcher to deal > with. Yes, I too think daemon should be as simple as possible; for the life cycle management to work well, you want minimal overhead in the daemon process. Tomas _______________________________________________ dev mailing list [email protected] https://www.moblin.org/mailman/listinfo/dev
