[Webkit-unassigned] [Bug 66655] New: Web Inspector: [meta] compile front-end using closure compiler.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=66655

           Summary: Web Inspector: [meta] compile front-end using closure
                    compiler.
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Web Inspector
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: pfeldman at chromium.org
                CC: timothy at apple.com, rik at webkit.org, keishi at webkit.org,
                    pmuellr at yahoo.com, joepeck at webkit.org,
                    pfeldman at chromium.org, yurys at chromium.org,
                    bweinstein at apple.com, apavlov at chromium.org,
                    loislo at chromium.org


I've been experimenting with closure compiler and have found a number of errors in the front-end with its help. Now that closure compiler supports getters and setters, I think it is time to give it another try. Here is what needs to be done:

1. Implement a python script that either compiles front-end using java library or sends files to the closure compiler service
2. Start annotating "@constructor" and "@extends" as suggested at http://code.google.com/closure/compiler/docs/js-for-compiler.html
3. Slowly compile files one by one, eliminating dependencies as we go

There are two potential problems as I see them:
1. We can't make compilation a build stage yet (either needs a java library or web service available)
2. Closure does not support "const". I think this is a fine price to pay given that we can annotate it with /** @const */ and migrate back once const hits the standard.

Given the amount of effort I put into it vs the errors that I discovered, I think it is worth it.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.