Hi All,
I've added support to CEF for creating embedded NPAPI plugins (see the
updated cefclient project from svn). Embedded plugins provide the same
capabilities as DLL-based plugins but are implemented as an integrated
component of the container application. So, for instance, you can now
creat
Hi Peng,
There is no requirement that AddJSHandler() be called with a unique
CefJSHandler
instance. It just depends on what you're trying to do. If all of the
JavaScript objects are represented by the same class (MyJSHandler), and it's
important for the class implementation to know which JavaScri
Hi
The chromium embedded framework (CEF) project is an excellent work! Thanks
for the hard work.
I have a maybe a stupid question as follows:
In cefclient.cpp , if there are more than one class, say 3 classes, do I
have to add the following code 3 times?
// Register our JavaScript "myclass" obj
Hi Daniel,
Just a heads up, I tried creating an MFC project linked against the chromium
libraries and ran into a number of MFC runtime-related linking conflicts
that I was unable to resolve. Hopefully you'll have better luck than I did.
I'm thinking, though, that to support MFC we'll need to crea
Hey Marshall. Thanks for all your hard work!!! I will be working on an MFC
wrapper as soon as I get Chromium redownloaded and built. I will be happy
to submit it to the community once finished!
Daniel A. White
On Tue, Dec 2, 2008 at 2:05 PM, Marshall Greenblatt
<[EMAIL PROTECTED]>wrote:
> On
On Tue, Dec 2, 2008 at 1:55 PM, Amanda Walker <[EMAIL PROTECTED]> wrote:
>
> Looks interesting!
>
> Suggestion: put links to your design docs into the "wiki" tab of the
> project page (or just move them over) so that people can find the docs
> easily.
Good idea. I'm still figuring out how the w
Looks interesting!
Suggestion: put links to your design docs into the "wiki" tab of the
project page (or just move them over) so that people can find the docs
easily.
--Amanda
On Tue, Dec 2, 2008 at 11:04 AM, Marshall Greenblatt
<[EMAIL PROTECTED]> wrote:
> Hi All,
>
> The chromium embedded fr
No, then it needs to be
--- CUT HERE ---
solutions = [
{ "name": "src",
"url": "svn://chrome-svn.corp.google.com/chrome/trunk/src",
"custom_deps" : {
"src/cef": "http://chromiumembedded.googlecode.com/svn/trunk";,
}
},
]
--- CUT HERE ---
(I still haven't tried out)
M-A
On T
Thanks Marshall. I will be trying this out!
Daniel A. White
On Tue, Dec 2, 2008 at 11:04 AM, Marshall Greenblatt <[EMAIL PROTECTED]
> wrote:
> Hi All,
>
> The chromium embedded framework (CEF) project is now available for download
> via svn:
>
> http://code.google.com/p/chromiumembedded/
>
> T
The "cef" directory should be created inside the "src" directory, at the
same level as "chrome", "base", "third_party", etc. Is that what this
.gclient example does?
On Tue, Dec 2, 2008 at 11:14 AM, Marc-Antoine Ruel <[EMAIL PROTECTED]>wrote:
>
> So the .gclient file would looke like:
>
> --- CU
So the .gclient file would looke like:
--- CUT HERE ---
solutions = [
{ "name": "src",
"url": "svn://chrome-svn.corp.google.com/chrome/trunk/src",
},
{ "name": "cef",
"url": "http://chromiumembedded.googlecode.com/svn/trunk";,
},
]
--- CUT HERE ---
(I haven't tried out)
M-A
On
11 matches
Mail list logo
