Hi Amanda, On Mon, Nov 17, 2008 at 3:01 PM, Amanda Walker <[EMAIL PROTECTED]> wrote:
> > > As has been mentioned by others, I could more easily fork chrome and > develop > > whatever I choose. However, I prefer an approach that will allow me to > > contribute my changes back to the chrome project as a whole. I've > > demonstrated this preference with a number of changes, admittedly small, > > that I've implemented in the past. I have no expectation that new > changes I > > make will be accepted. I'm positive, however, that they won't be > accepted > > if I don't first make the effort to discuss them with the chromium > > development team. That is why, up to this point, the discussion has been > > primarily abstract -- issues this important should not be decided by one > > individual, especially when that individual (myself) is not intimately > > familiar with the design choices behind current chromium internals. > > While I understand that perspective, I also have to say that with this > team, an individual saying "I think we should do X via method Y, and > here's a working proof of concept" get much farther, much faster than > "how should we do X?" Even if the first prototype gets thrown away, a > concrete proof of concept always helps to scope the problem, identify > unexpected complications or side issues, etc. I agree with you, and that was why I was a bit surprised by the initial slew of negative responses. I'm currently in the process of turning the example that started this thread into a COM implementation, which I'll then post for additional feedback. After that, I'll begin pulling things out of browser core and see how it goes... > > > > I'm not asking chromium or Google to commit development resources to this > > project. I'm simply seeking ideas and feedback on how we can make our > > changes in a way that would beneficial to the chromium project as a > whole. > > Most of the feedback so far have been along the lines of "use > > RenderViewHost." Unfortunately, this advice is incompatible with what > we're > > trying to achieve (again, see parent thread). > > Well, it (or the analogous code in test_shell) does seem to be the > closest to IWebBrowser2, and would be a great place to start, since > it's in effect chromium's internal embedding interface. I suspect > that's why people have been pointing you in that direction. I have already implemented a working embedded client based on test_shell, with much assistance from developers on this list. More information on that client is available in this thread: http://groups.google.com/group/chromium-dev/browse_thread/thread/5b23e1a218811b3d That's where I first ran into the core browser bundling problem. Since then I've been pondering how to provide additional functionality without re-implementing, and that's what led to this discussion. Changing the interface to be COM-based seemed like a natural next step as well. > > > > This is exactly why I'm seeking input at this point in the development > > process. Again, we need to know about the far-reaching implementation > > concerns before we go out and write code. > > Fair enough--on the other hand, some of those concerns will be quite > invisible until someone goes out and writes a proof of concept. It's > a balancing act. > > > Just as an example, I've seen nothing to indicate that I can get (a) > > multi-process architecture support, (b) printing support or (c) context > > menus without either accessing the browser base or re-implementing them. > > It seems to me that you could get all of those with RenderViewHost, > though you might have to crib a bit. You certainly wouldn't need the > whole browser module, though. > > > This is a very good idea. Can I add content under > > http://sites.google.com/a/chromium.org/dev/developers/design-documents, > or > > should I look elsewhere? > > Hmm, that's a good question. I don't know, off hand, but I'll see if > I can find out. > > --Amanda Again, thank you for taking the time to respond to my questions. 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 -~----------~----~----~----~------~----~------~--~---
