Cheng Zhao aedacd39d2 Rename 'finish-launching' event to 'ready', ... 'finish-launching' is more like a OS X message name, and in atom-shell it means initialization has done, so 'ready' seems to be a better name and more easy to remember. The 'will-finish-launching' event just represents the corresponding message on OS X and is the same with 'ready' on other platforms, so we keep its name to indicate that it's only useful for OS X specified code.		2013-12-27 11:08:26 +08:00
..
app.coffee	Rename 'finish-launching' event to 'ready',	2013-12-27 11:08:26 +08:00
auto-updater.coffee	Add 'ready-for-update-on-quit' event for auto-updater.	2013-06-03 21:51:46 +08:00
browser-window.coffee	Get rid of the ugly ATOM_BROWSER_INTERNAL_NEW message.	2013-12-26 18:41:21 +08:00
dialog.coffee	Calling asynchronous functions in renderer now doesn't block browser.	2013-09-24 18:01:12 +08:00
ipc.coffee	Get rid of manually converting to base::Value when possible.	2013-12-05 23:47:07 +08:00
menu-item.coffee	Set application menu would set menu for all windows on Windows.	2013-10-05 14:31:30 +08:00
menu.coffee	Get rid of the ugly ATOM_BROWSER_INTERNAL_NEW message.	2013-12-26 18:41:21 +08:00
power-monitor.coffee	Add power-monitor module, fixes #45.	2013-08-03 16:03:56 +08:00
protocol.coffee	Add 'registered' and 'unregistered' events for protocol module.	2013-08-29 20:56:25 +08:00