Comment #1 on issue 12608 by [email protected]: Chromium should handle creating desktop shorcuts for apps http://code.google.com/p/chromium/issues/detail?id=12608
Posting some discussion from private email: mpcomplete wrote: The shortcut creation code lives in the gears 'desktop' module: http://code.google.com/p/gears/source/browse/#svn/trunk/gears/desktop The basic flow is: - user clicks "create shortcut" button - (gears_integration.cc): browser posts a message to the IO thread (which gears runs on), to call into gears - (chrome_plugin_host.cc): browser calls into gears - (gears module_cr.cc): gears creates a chrome-specific Desktop object to handle the request - (gears desktop_cr.cc): gears calls into the browser-neutral desktop code - (gears desktop.cc): gears shows a dialog [this step has some more calls into chrome and back], then creates the shortcut ---------------------------------------------------------------------- More from mpcomplete: Re-adding Mark to clarify what exactly he wants to do with the shortcut functionality. It's definitely possible. The question is how much work is involved :). The answer to that partly depends on the requirements. One of the reasons we chose to use gears for this is that gears has a programmatic javascript API to create a shortcut. See http://code.google.com/apis/gears/samples/hello_world_shortcuts/hello_world_shortcuts .html . We wanted the experience to be similar for the javascript API and for using Chrome's menu item. Things that are shared between those: - code - the dialog code, and to a lesser extent, look and feel - logic and storage to prevent us prompting for shortcut creation if the shortcut already exists. We could just decide to diverge the features completely, and that would mean copying the code from gears and refactoring it to work in Chrome. Or we might want them to continue to behave similarly, which would require closer interaction between Gears and Chrome. Or something else that I haven't thought of. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
