Nobody's in a position to object, though I know a bunch of people are approaching the problem from different angles. Perhaps we'll end up with a bake-off :-).
More seriously, coding up an example implementation, even just as a proof of concept, is a great way to validate a design (take a look at Awesomium, for example--implementing it revealed a bunch of issues that the author hadn't anticipated, which led to design changes and some great improvements, even though it's still in the "experimental" stage). --Amanda On Wed, Nov 26, 2008 at 10:58 AM, Daniel A. White <[EMAIL PROTECTED]> wrote: > > Man, I am itching to help start coding this... any objections? > > On Nov 25, 4:04 pm, "Marshall Greenblatt" <[EMAIL PROTECTED]> > wrote: >> Cool, it sounds like the embedded browser spaces on linux and osx are well >> accounted for. For the time being I'll continue with an os-agnostic >> approach because it's relatively painless to do so. Here, then, is the >> embedded browser framework that I envision, complete with C++ class >> definitions: >> >> http://code.google.com/p/chromium/wiki/EmbeddedBrowserFramework >> >> Any and all comments are welcome :-). >> >> - Marshall > > > -- --Amanda --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
