[chromium-dev] Re: Idea: Consistent opening of new tabs in background and foreground

Thanks Peter. I posted to Chromium-discuss. * Please do not reply to this thread anymore * On Sep 29, 7:10 am, "Peter Kasting" <[EMAIL PROTECTED]> wrote: > On Sat, Sep 27, 2008 at 6:23 PM, Yarin <[EMAIL PROT

[chromium-dev] Re: Cannot open include file: 'webkit_version.h' error

Fixed in r2670. I'll look into splitting WebCore to remove the file generation (if possible) into another separate configuration project. That may wait to after the webkit merge tough. M-A 2008/9/28 Marc-Antoine Ruel <[EMAIL PROTECTED]>: > Sorry for the trouble, I'll revert tomorrow morning. > >

[chromium-dev] Re: Proposal: Chrome Development for Corporate/Professional Windows Developers

To answer a few quick questions... 2008/9/26 HLS <[EMAIL PROTECTED]>: > 1) Development Machines vs Target Platfiorms > > This is critical as many Windows product operations do no like to mix > compilers, sdks, etc as it may affect other existing building > operations. This part is covered in ot

[chromium-dev] Re: Improving Build Process

2008/9/28 HLS <[EMAIL PROTECTED]>: > On Sep 28, 6:56 pm, "e. roman" <[EMAIL PROTECTED]> wrote: >> There was talk in the past of breaking debug builds into multiple >> DLLs, to mitigate link times. >> M-A did some investigation -- I don't recall the exact conclusion, but >> it was deemed not worth

[chromium-dev] Re: Proposal: Chrome Development for Corporate/Professional Windows Developers

> 3) DIALOGS AND RESOURCES > This is a BIG item for me. > - How are DIALOGS and RCs created? > - Is it WYSIWYG? > - Are there any special tool for this? The dialog code is mostly contained in classes that end in "View", ie. AboutChromeView (I think it is called that, don't have the code in front

[chromium-dev] Re: Cannot open include file: 'webkit_version.h' error

I copied the file from chromium\src\chrome\Release\obj\WebCore to chromium\src\chrome\Debug and the error vanished. On Sep 28, 11:45 am, "Nicolas Sylvain" <[EMAIL PROTECTED]> wrote: > +cc sgk > > I'm not sure how 2480 would cause that. > But from what I see it's a timing issue/dependency problem

[chromium-dev] Re: TRACE equivalent

Hi, take a look at src\base\logging.h. It's in base, which means that you can include it almost anywhere without feeling guilty. It gives you, among other things: DLOG - TRACE equivalent LOG - TRACE that also works in release builds DLOG_IF, LOG_IF - conditional TRACEs DCHECK - ASSERT equivalen

[chromium-dev] Re: Current line number from within a CALLBACK_FUNC_DECL?

Sorry for late reply. I don't think V8 provides this information through API currently. On Fri, Sep 26, 2008 at 3:12 PM, Elliot Glaysher <[EMAIL PROTECTED]> wrote: > Feng (or another v8 expert): > > Is there any way to get the current line number of an executing > javascript from within a C++ cu

[chromium-dev] Re: Proposal: Chrome Development for Corporate/Professional Windows Developers

Ah you're right, it's been a while since I have touched the dialogs. Sorry for the confusion. 2008/9/29 Finnur Thorarinsson <[EMAIL PROTECTED]>: >> 3) DIALOGS AND RESOURCES > >> This is a BIG item for me. >> - How are DIALOGS and RCs created? >> - Is it WYSIWYG? >> - Are there any special tool fo

[chromium-dev] Re: Proposal: Chrome Development for Corporate/Professional Windows Developers

> If you are used to Initializing dialogs using InitDialog, > the equivalent in Chrome is ViewHierarchyChanged. And now that I have the code in front of me, ViewHierarchyChanged often contains something like: if (child == this) { if (is_add) { // Code to initialize the dialog. } e

[chromium-dev] Re: Correct way to create an NPObject for assignment to CppVariant

On Sat, Sep 27, 2008 at 6:31 PM, Marshall Greenblatt <[EMAIL PROTECTED] > wrote: > Hi All, > > What is the correct way to create an NPObject for assignment to a > CppVariant instance? The CppVariant instance in this case represents the > return value from a CppBoundClass callback. For example, i

[chromium-dev] Re: Correct way to create an NPObject for assignment to CppVariant

On Mon, Sep 29, 2008 at 1:06 PM, Marshall Greenblatt <[EMAIL PROTECTED]> wrote: > Perhaps these questions are a bit too broad, given the lack of existing code > that utilizes this capability. > > New question: > > Should it be possible to create an NPObject representation of a JavaScript > Array f

[chromium-dev] Re: Correct way to create an NPObject for assignment to CppVariant

Hi Feng, Sorry to be a bother, but you seem to be the person to ask for JavaScript-related questions :-). In webkit/glue/CppVariants, is NPN_Evaluate() the proper approach to use for creating a JavaScript Array (to then use as a return value from a CppBoundClass callback), or would a different ap

[chromium-dev] Re: Pass the invoked JavaScript method name as an argument to the fallback callback

Hi Feng, If you wouldn't mind, please give us your opinion on this question. Evan Martin says you might have already responded, but if you did we've somehow managed to misplace it :-(... Thanks, Marshall On Wed, Sep 24, 2008 at 10:45 PM, Marshall Greenblatt < [EMAIL PROTECTED]> wrote: > Hi Eva

[chromium-dev] Re: Proposal: World-writeable chromium development wiki

On Sep 26, 12:37 pm, Yarin <[EMAIL PROTECTED]> wrote: > C) Independently host another wiki at some web server. > Would cause legal issues. Not if it's titled "Unofficial Chromium Wiki" and hosted on some random dude's webspace (where "some random dude" is any institution other than Google). The

[chromium-dev] WebKit merge landing tomorrow afternoon

We plan to land the webkit_merge_branch onto trunk tomorrow afternoon. http://src.chromium.org/svn/branches/chrome_webkit_merge_branch/ We still have a bunch of failures: http://build.chromium.org/buildbot/waterfall/waterfall?builder=Webkit%20(merge) but we plan to mark all failing tests as "fixa

[chromium-dev] Re: WebKit merge landing tomorrow afternoon

Hi Eric, Is there a document somewhere that describes the changes that we can expect? Regards, Marshall On Mon, Sep 29, 2008 at 6:00 PM, Eric Seidel <[EMAIL PROTECTED]> wrote: > > We plan to land the webkit_merge_branch onto trunk tomorrow afternoon. > http://src.chromium.org/svn/branches/chrom

[chromium-dev] Re: WebKit merge landing tomorrow afternoon

Not really. We are merging in a forked copy of WebKit based on WebKit r36102 from webkit.org. http://trac.webkit.org/browser/trunk?rev=36102 Previously our WebKit was based off of: http://trac.webkit.org/browser/branches/Safari-3-1-branch -eric On Mon, Sep 29, 2008 at 7:26 PM, Marshall Greenbl

[chromium-dev] Re: WebKit merge landing tomorrow afternoon

The changelog is substantial (over 100,000 lines of commit logs) Since the Safaro 3.1 branch originated from [EMAIL PROTECTED], and we are merging to [EMAIL PROTECTED], you can view the changelogs with: % svn log http://svn.webkit.org/repository/webkit/trunk -r30073:36102 In fact this is a supe

[chromium-dev] Re: WebKit merge landing tomorrow afternoon

I copied the output to here: http://romaneric.googlepages.com/webkit-merge-log.txt It is ~4mb On Mon, Sep 29, 2008 at 8:42 PM, e. roman <[EMAIL PROTECTED]> wrote: > The changelog is substantial > (over 100,000 lines of commit logs) > > Since the Safaro 3.1 branch originated from [EMAIL PROTECTE

[chromium-dev] Changes to Issue tracker Area- labels

We had too many Area- labels. The issue tracker only displays a maximum of 11 labels matching a prefix. Even 11 labels often scroll out of view when you are looking for an autocomplete match. I reduced the number of Area- labels to make it easier to categorize issues and divide them up for triage