Hi M-A, We all know that development issues can become emotional for those closely involved with them. Lets all please make an extra effort not to assume the worst about other people's intentions or meanings.
On Mon, Nov 17, 2008 at 9:02 AM, Marc-Antoine Ruel <[EMAIL PROTECTED]>wrote: > > 2008/11/16 Marshall Greenblatt <[EMAIL PROTECTED]>: > > I agree with you on this point. I believe the best solution is to add > > "theme" support to chrome similar to the visual styles support provided > by > > Ah I see, it took me a while to realize but you don't want to embed > it, you want to create a custom UI above the chromium browser. The intent with these comments is to address Ben's stated concerns about whether the current chrome UI look/feel would be appropriate for an embedded context. Everyone so far has agreed that it would not. Most people wishing to utilize the chrome code base have no desire to develop a competing product. We simply wish to utilize existing chrome capabilities in our applications without re-implementing them. > Ok well > then it's mostly a fork you are looking to. While forking is always an option with an open source project, it is never a decision to be taken lightly. I maintain hope that we can all peacefully coexist in the same code base. > Otherwise, like I and Ben > said, for a truly embedded html viewer, RenderViewHost is the best > place to hook. Unfortunately, the chrome ActiveX team is a small group of developers with limited development time and resources. We are all developing other applications full-time (or part-time) that we hope will one day be able to use chrome as an embedded browser component. I'm sure you've read all of the messages in this thread, but here's an review of what we're trying to accomplish just to be clear: 1. Easy implementation and use by the client-side developer, preferably in the language of their choice. 2. Provide as much browser-like functionality as possible by default. 3. Allow the client to override, customize or disable default functionality if desired. 4. Minimize changes to the existing chromium code base, and avoid duplication of existing functionality if possible. 5. Take advantage of new features, bug fixes and enhancements to chromium while requiring minimal changes to the "embedded component." Re-implementing existing functionality is not currently an option for us. Modifying the existing browser code base to expose existing functionality is an option. I hope that the chromium developers and Google are willing to work with us so that the final solution is beneficial for everybody. > > > > > As an added bonus, if we provide features in the chrome ActiveX control > that > > go beyond what Microsoft provides -- like support for theming, tabs and a > > multi-process architecture -- then so much the better for us and our > users. > > Tabs? You cannot provide tabs with IWebBrowser2 without adding a new > interface and major UI coordination. You should look at implementing > the base functionality first before looking at complex issues like tab > support. As you say, IWebBrowser2 would need to be extended. As with any successful development project we plan to take baby steps the whole way. We have not committed to supporting IWebBrowser2, but are considering it as a means for providing a basic level of compatibility with existing clients. If we choose to go with IWebBrowser2 then we will extend its capabilities only at the appropriate time. > > > Actually, do you really need to do anything at all? I mean, if you > want to have a help center browser, have you thought about using: > path\to\chrome.exe > --user-data-dir=path\to\my\help\center\tmp-data-dir > --app=path\to\my\help\center\index.html This is a fine idea for somebody looking for a completely independent help viewer, and I encourage anyone with that purpose in mind to try this solution. Many of us, however, use embedded browsers as an integral part of our application user interface. For us it's necessary to have a level of fine-grained control over the browser's behavior that is not currently available with chrome. > > > M-A 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 -~----------~----~----~----~------~----~------~--~---
