Integration through non-editable HTMLArea: the HTML markup in the dataprovider attached to the non-editable HTMLArea needs to be valid XML, as Servoy needs to parse and process the contents  

• media url rewrites
• src url rewrites
• script, style and link tags inside the custom HTML 
• javascript:.... event handler rewrites
  • tip: create a button element, make is invisible through css (visibility: hidden) and through JavaScript click the button: 
    <button id="myCoordinatesCallbackHandler" onclick="javascript:globals.myCoordinatesCallbackMethod(browser:x, browser:y)" style="visibility: hidden">dummy</button>
    document.getElementById("myCoordinatesCallbackHandler").click()
• body onLoad event to trigger logic when the content gets rendered 
• Tips:
  • XML (add HTML template here)
    • CDATA
    • Watch out for self closing divs
  • Manage custom StyleSheets inside Servoy and include them into the Web Client using the following code:
    var style = solutionModel.getStyleSheet(name).getText();
    .....

WebClientUtils plugin:

• Allows to force inclusion of some of the JavaScript libraries Servoy ships with: Servoy by default conditionally includes them onto the Web Client markup only when they are needed. If custom clientside logic requires the library to be available, this can be done using the following code:
  ...
• Allows to execute JavaScript clientside in the browser
• Allows adding class attributes to the markup of elements
• Allows for generating callback scripts 
• Allows for marking elements as rendered: this hooks deeply into Servoy mechanism for updating the Web Client markup when something changes in the UI. When ....

For an overview of the version of each JavaScript library that is bundled with Servoy, check ....