From: Alan H. <al...@tu...> - 2006-08-29 07:28:29
|
On Mon, 2006-08-28 at 14:58 -0500, Daniel E. Shipton wrote: > The Windows app_faker seems to be severely limited in what it can do > (compared to other platforms). Applications that have their own data > to load do not work very well because of the temporary infrastructure > that Chromium sets up to run it. How do most people deal with this > issue? I would like to see the Chromium not specify the application > to run in the mothership config file and instead let the user run the > app_faker /with/the/path/to/what/they/want/to/run . I don't see why > this would be a problem(on All platforms). I find it quite unnatural > to specify the file path to a Windows executable from a config file. > Thoughts? Comments? Dan, You don't need to use the app_faker at all. As long as the Chromium opengl32.dll is chosen for the application startup, you can rule out app_faker just as you can on other platforms. You are probably best to read the autostart document in the Chromium documentation to get you going. Which explains the Windows route to application starting. Alan. |