I am trying to analyse memory usage of a web app using web inspector.
But it doesn't have a section called 'Memory' in Timelines as described in this article https://webkit.org/blog/6425/memory-debugging-with-web-inspector/
I also tried this solution Can't see Safari developer Timeline's Memory Instrument
but it doesn't get listed in the edit list as well
Available options are
Network Requests
Layout & Rendering
JavaScript & Events
Related
I'm using Ignition HMI application and it uses the JXBrowser as it's web browser component. I need to change the default image viewer used by JXBrowser to use a web-enabled browser with more capabilities (pan & zoom, called OpenSeaDragon).
How can that be done? I know you can get the BrowserPreferences, but I did not see anything specific to the default apps used.
OpenSeadragon is a JavaScript library that must be embedded into the web page and configured to provide an image viewer that can be used for panning, zooming, etc. I see they also provide a browser extension that allows you to view any image on a web page with their viewer, however, JxBrowser does not support Chrome/Chromium extensions at the moment.
I tried to port my succesefuly worked my kendo-based site as chrome app. But app does not works. I found on chrome developer console exception message "extensions::platformApp:17 history.pushState is not available in packaged apps." on
<script src="kendo/js/kendo.mobile.min.js"></script> string
I found the same problem on angular with a solution, but did not found for the Kendo.
Any way to resolve it?
By default Kendo UI (and Mobile) doesn't use the History API, due to its rather limited support in the past. If you explicitly enabled it, you can delete this option, though you will probably have to update your navigation throughout the apps:
http://docs.telerik.com/kendo-ui/api/javascript/mobile/application#configuration-pushState
To develop websites I use domino designer v9.01 with OpenNTF Bootstrap extension library v14. I am new to IBM domino so have mercy …
The trouble I have is : While previewing XPage apps in Notes all controls, views etc. are there and looks as expected. But when I preview same XPage apps in a web browser (newest FireFox, newest Microsoft Edge) I get messy results. To be more specific, the amount of controls, views, etc. are there and they also work. But their expected design is messy. I cannot describe it better because I have never seen such pages before.
Finally the question is : Why is the presentation of XPage apps in Notes perfect while in a web browser not ?
UPDATE
Here are 2 screenshots to visualize the problem. First screenshot is from Notes showing expected UI. Second screenshot is from FireFox browser showing non-expected UI which i call "messy". The content you see is a simple example from a tutorial. So do not wonder about that.
The Extension Library plugin will also need to be installed on the server as well as into Domino Designer. The usual process for this is using an UpdateSite database, as documented here http://www-10.lotus.com/ldd/ddwiki.nsf/xpAPIViewer.xsp?lookupName=XPages+Extensibility+API#action=openDocument&res_title=XPages_Extension_Library_Deployment&content=apicontent
I'm working a lot with the chrome developer tools to develop web applications. Currenty in one big project we have an application which features its own JSON-format for requests to the server. The JSON objects sent contain various information about the type of the request and its data and so on.
Is there an opportunity to extend chromes developer tools (especially the network view) with a special view which displays the data from the request in a way that makes it more readable for developers working with the project?
I tried to find out about extending the tools but i don't know really where to start. I found some information how i can add tabs and pages to the developer tools but nothing about how i can get the request / response information to display them.
There is no standard API to extend the network view of the developer tools. If you're happy with using a custom devtools tab, use the chrome.devtools.network API to filter and format responses, and render it in your tab.
If you're adventurous, you can use the next approach to directly modify the content of the network view.
First, you need to know how to debug the devtools.
Open the developer tools (F12).
If it's docked, undock it.
Press F12 to open the devtools of the devtools.
Then, you need to use your debugging/coding skills to find out which methods are responsible for rendering the network panel (tip: use DOM breakpoints to quickly discover where to start).
Write code which transforms the network tab to the desired format (either by monkey-patching, or by hooking up on the event you've found at the previous step).
At this point, you know how to change the lay-out of the network tab. Now, you need to permanently activate the code for your developer tools. I've explained two of such methods at How to inject javascript into Chrome DevTools itself.
You could download a copy of Google Chrome's source code and play with it; it's written in C++.
/trunk/src/chrome/browser/devtools looks to be the correct dir to look at.
You can make use of chrome.devtools.network.onRequestFinished. For more control and advanced information you can use chrome.webRequest api.
I am embedding an org.eclipse.swt.browser.Browser into a view in a modified eclipse (Indigo), for use as a preview pane of a form editor component. On a form model change or an element selection change the code renders the form via vaadin 6 and displays it in the browser component.
Now, this works like a charm in most cases. But for some highly complex forms the HTML+JS generated by vaadin generates a lot of stress on the browser, rendering it unresponsive for up to a few seconds. That in itself wouldn't be tragic (1), but as long as the SWT Browser component is busy rendering that stuff, the entire eclipse UI thread is blocked.
A simple way to reproduce this is to create an HTML page that blocks inside a javascript function (see https://gist.github.com/creinig/5150747 for an example) and display it in the SWT browser. As long as that JS function is running, the entire SWT application is not responding to anything.
The only info I've found on this problem are
one SO question (without resolution) and
one question on EclipseZone (unanswered).
Not that helpful :(
The API docs of the Browser component don't seem to offer any insight on whether its rendering is triggered periodically by the UI thread or if itself triggers something that blocks the UI.
Is there a way to decouple the Browser component's rendering from the SWT UI thread? Or anything else that could be done to protect the eclipse UI from hanging stuff in the browser?
(1): We need forms of this complexity level, we're already optimizing the rendering performance and a switch to vaadin7 will most likely also speed things up. But the problem will certainly persist, if only in reduced severity.
Not a real solution, but a workaround that Works For Me (TM):
As described here it is really easy to launch the system's default browser from SWT. So I'm going to add an option to the view containing the browser control that will "detach" the view by disabling the browser control and opening the system browser instead.
In case the linked page drops off the net, here's the gist:
org.eclipse.swt.program.Program.launch("http://my.funny.url/");
launches the application registered for HTTP URLs. In other words: the system default browser.
Happiness ensues :)