HT for Web embedded Qtwebkit client Solution

HTML5 is strong enough, but many applications still need a standalone desktop client solution, after all, can operate local files and other functions or many tool class software can not fully adopt the cloud solution in the short term.

Http://brackets.io, recently released by Adobe, is a similar application, brackets describes itself as: an open source code editor for the Web, written in JavaScript, HTML and Css. Such a description is hard to imagine in the past as an editor's tool, and now the use of webkit nesting of various shells has made such applications mainstream.

Adobe's brackets uses its own https://github.com/adobe/brackets-shell/shell framework, but Brackets-shell is only tailored for brackets and is not recommended for general use:

Note:the Brackets-shell is only maintained for use by the brackets project. Although some people has definitely had success using it as an app shell for other projects, we don ' t provide any officia L Support for and we haven ' t do a ton of work to make the app shell easily reusable. Many people would likely find it easier to use a project like Node-webkit, which are more generic by design.

Generic applications using Https://github.com/rogerwang/node-webkit,HT for Web can naturally be packaged as client applications via Node-webkit, as shown in:

Recently encountered the user through QT to the HT for Web embedded Qtwebkit solution, but encountered a normal display but not mouse operation strange problem, after a toss to find HT incredibly put Qtwebkit in the desktop environment, the wrong identification as a touch mobile terminal environment, How to correctly judge the interaction between touch and mouse is very dog blood, can refer to http://stackoverflow.com/questions/4817029/ whats-the-best-way-to-detect-a-touch-screen-device-using-javascript/4819886#4819886 Coupled with today's window8 touch, mouse makes the problem even more complicated.

Fortunately, HT has a configurable scenario by setting Htconfig = {Default: {Istouchable:false}} before the introduction of the Ht.js package, forcing HT to be handled with regular mouse events. Because HT internal simple use "ontouchend" in document scheme to judge, in general the desktop environment this value is undefined, mobile terminal is null, and Qtwebkit incredibly in the desktop environment is also null, As a result, HT uses a touch listener event which causes the phenomenon to be unable to operate, and everything is OK after the Htconfig setting!

HTML5 the use of WebKit embedded packaging costs is not new, the entire world of various client technology is becoming more integrated, countless kinds of strange client scenarios are changing a lot of ideas and architecture, the recent wwdc2014 in the JavaScript for Automation I think is the highlight of the serious neglect, the entire Mac OSX system and applications can be called through the Javascrpit, early window for many applications and popular, Apple after a mobile terminal, the use of such as JavaScript for Automation's actions attract more professional client developers, perhaps unknowingly in the desktop field.

HT for Web embedded Qtwebkit client Solution