Innovations node-webkit 0.6.3

Yesterday (July 23), the Intel open source technology center launched another version of the node-webkit engine. As before, this engine allows you to open browser-like windows (based on Chromium code) and use Node.js APIs in them - and therefore, it’s easy to create GUI applications using web development methods (in JavaScript, HTML, CSS, WebGL , etc.). .) under Windows, Mac OS X and Linux operating systems.

The new version received the number 0.6.3 and contains the Node engine version 0.10.12:


')
Three months ago (April 29), I reviewed one of the previous versions of node-webkit (version 0.5.1). Since then, a number of significant innovations have appeared in node-webkit .

The most important of these was the improvement of the search subsystem and the launch of applications. Now, when you start the node-webkit engine, it looks for the application in the following order:

1. It checks the tail of the node-webkit executable file , whether the ZIP-packed application is docked to it.
   
2. Searches for the application manifest ( package.json file) in the same directory as the node-webkit executable file .
   
3. Searches for a ZIP-packaged application (named package.nw ) in the same directory.
   
4. Uses the first command line parameter as the path to the application.

Previously, after the first of these steps, node-webkit went straight to the fourth, so to run non-attached applications, you had to write a script wrapper (and under Windows - a batch file) that would put the path to the application in the first place on the command line A node-webkit is called (and if there were other parameters, it would shift them to the second, third, and so on place). Now, node-webkit acts on my advice , so finally it becomes possible not to bother yourself with this job, but simply and artlessly put the node-webkit engine into the application directory and then start the engine.

Besides:

• In the new field App.dataPath, you can read the path to application data stored in the user's system directory. (In Windows, this will be “% LOCALAPPDATA% / name”, in Linux it will be “ ~ / .config / name”, in OS X it will be “~ / Library / Application Support / name”, where “name” is the name of the application, asked in his manifesto .)
  
• The new App.clearCache () function allows you to programmatically clear the file cache, downloaded via HTTP - both in memory and on disk.
  
• The App.open event now arrives in all application windows.
  
• In the application manifest , the dom_storage_quota parameter appeared to indicate the number of megabytes available for data stored through the DOM Storage API.
  
• The new method App.getProxyForURL (URL) returns (in PAC format ) information about the proxy server used to access the specified URL.
  
• Debugger settings (in particular, breakpoints) are saved between sessions.
  
• The debugging feature “ Devtools jail ” allows you to show a debugging console inside some iframe.

Therefore, I can only advise users of node-webkit: take this new version.