Hi All, To test the feasibility of turning Chrome into a multi-process ActiveX control I'm going to implement a simple experiment sans COM. The goal of this experiment is to have a client application launch chrome.exe programatically as a separate process, and have the chrome process then create its frame as a child window of the client application, at a position that the client application specifies. The client application will (a) spawn the chrome.exe process passing it an HWND and target window rectangle via command-line arguments, and (b) terminate the chrome.exe process when it exits. Other than that, the chrome process will be completely independent of the client application (for now).
To demonstrate the overall concept I've created a pair of basic (non-chrome) "client" and "server" applications. The source and VS2005 projects are available here: http://www.magpcss.net/patches/interprocex1.zip Build both in debug mode and then run the client application. The client application will launch the server application with command-line arguments that cause the server application to create and render a child window (red rectangle) in the client. When the client application exits the server application is also terminated. If anyone has comments or suggestions I'd love to hear from you. Otherwise, you may consider this a heads-up and background on what may be a series of very strange questions over the next few days :-). Regards, Marshall --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
