Bug 94738 - Use closure compiler to compile blackberry inspector frontend
Summary: Use closure compiler to compile blackberry inspector frontend
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit BlackBerry (show other bugs)
Version: 528+ (Nightly build)
Hardware: Other Other
: P2 Normal
Assignee: Peter Wang
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-22 11:43 PDT by Hanna
Modified: 2015-01-17 20:39 PST (History)
7 users (show)

See Also:


Attachments
Patch (12.11 KB, patch)
2012-08-22 12:16 PDT, Hanna
rwlbuis: review-
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Hanna 2012-08-22 11:43:58 PDT
Use closure compiler to compile blackberry inspector frontend

first inspectorBB.html should be generated automatically,
then the closure compiler should remove the whitespace within the inspector javascript file
Comment 1 Hanna 2012-08-22 12:16:01 PDT
Created attachment 159986 [details]
Patch
Comment 2 Pavel Feldman 2012-08-22 13:47:16 PDT
Inspector now loads code lazily using module infrastructure. You should combine files into modules using inline script and deploy all module js files along with inspector.js. See WebCore.gypi (or project.xcodeproj's Streamline inspector blah target) for modules content.

For example you should deploy ElementsPanel.js and inline all the files it imports via importScript. Same goes for other panels.
Comment 3 Hanna 2012-08-22 14:52:13 PDT
(In reply to comment #2)
> Inspector now loads code lazily using module infrastructure. You should combine files into modules using inline script and deploy all module js files along with inspector.js. See WebCore.gypi (or project.xcodeproj's Streamline inspector blah target) for modules content.
> 
> For example you should deploy ElementsPanel.js and inline all the files it imports via importScript. Same goes for other panels.

I looked at WebCore.gypi, it puts all the inspector frontend file names in 'webinspector_files'? I do not get what it's supposed to tell me.

So if ElementsPanel.js uses variable WebInspector, then I should say importScript(inspector.js) so that it knows the variable WebInspector on its own? What am I supposed to do with the modules afterwards? combining them together?
Comment 4 Pavel Feldman 2012-08-22 22:12:04 PDT
Look at the streamline inspector resources target in xcode project for WebCore and do the same thing. (Or extract it and reuse in both).
Comment 5 Hanna 2012-08-31 10:07:44 PDT
(In reply to comment #4)
> Look at the streamline inspector resources target in xcode project for WebCore and do the same thing. (Or extract it and reuse in both).

the streamline inspector in xcode proj combines all the js files except for a few worker files and 'import script' in those worker files imports things that they need? In our case we copy them over seperately, this setup only applies to the combined inspector files
Comment 6 Pavel Feldman 2012-09-03 02:05:50 PDT
> the streamline inspector in xcode proj combines all the js files except for a few worker files and 'import script' in those worker files imports things that they need? In our case we copy them over seperately, this setup only applies to the combined inspector files

I think you are looking at the outdated version of that file (> 2 weeks old).
Comment 7 Rob Buis 2012-09-17 07:54:55 PDT
Comment on attachment 159986 [details]
Patch

R- based on Pavel's comment.
Comment 8 Rob Buis 2012-09-17 07:55:22 PDT
Peter, is this something for you to look at? Konrad is on vacation.