Hi, My bad. I'm so used to build WebKit with most build options disabled. Reverted to a default build configuration and it indeed looks good.
Thanks, -Ilyes On Thu, Dec 1, 2011 at 2:35 PM, Ilyes Gouta <[email protected]> wrote: > Hi Martin, > >> Have you run 'make install' or set the WEBKIT_INSPECTOR_PATH >> environment variable? > > Yes. I understand that the inspector's JS and HTML files are > post-processed and then installed in the final destination location. > > I'm getting (just) this on my shell: > > ** Message: console message: undefined @0: TypeError: 'undefined' is > not a function > > Running the inspector w/o a 'make install' resulted in WebKit > complaining about not finding the sources in the right place. Running > the unprocessed code lead to few - kind of - fatal errors when trying > to run the inspector's JS back-end code. > > Why I'm not getting the full UI of the inspector (the icons) at least? > > -Ilyes > > On Thu, Dec 1, 2011 at 11:02 AM, Martin Robinson <[email protected]> wrote: >> On Thu, Dec 1, 2011 at 10:53 AM, Ilyes Gouta <[email protected]> wrote: >>> I got it built, enabled via --enable-developer-extras run-time option >>> and exposed via the embedding API in GtkLauncher, but then all I get >>> is the empty HTML/JS w/ just the grey toolbar when I click on "Inspect >>> Item" in the contextual menu. >> >> Have you run 'make install' or set the WEBKIT_INSPECTOR_PATH >> environment variable? >> >> --Martin _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
