2
edits
XUL:XUL Application Packaging: Difference between revisions
Jump to navigation
Jump to search
→Background information
mNo edit summary |
|||
| Line 111: | Line 111: | ||
* Mac users expect drag-and-drop install of applications. The shipping "app" package must be ready to run after download and decompression. Also, embedding installers in the download process (active-x/xul helpers) is rather difficult to infeasible in the mac world, and requiring installers only hinders the ease of packaging and installation of software for an already small target audience. | * Mac users expect drag-and-drop install of applications. The shipping "app" package must be ready to run after download and decompression. Also, embedding installers in the download process (active-x/xul helpers) is rather difficult to infeasible in the mac world, and requiring installers only hinders the ease of packaging and installation of software for an already small target audience. | ||
* Mac applications must be loaded by Launch Services. This happens by actions that evoke app loading such as double-clicking on the app in the finder, double-clicking a document related to an app, or executing "open [app]" at the command line. If we want to pass a | * Mac applications must be loaded by Launch Services. This happens by actions that evoke app loading such as double-clicking on the app in the finder, double-clicking a document related to an app, or executing "open [app]" at the command line. If we want to pass a parameter to a properly launched app, we need to use a compatible way to do that (ODOC event posted to launched app). | ||