DHTMLX Docs & Samples Explorer

Migration from 2.0 to 2.5

1. dhtmlxWindows support no more needed.

If you do not plan to use dhtmlxWindows on your page, we recommend you to remove links to dhtmlxwindows.js (it no more needed):

    <link rel="stylesheet" type="text/css" href="../../../dhtmlxWindows/codebase/dhtmlxwindows.css">
    <link rel="stylesheet" type="text/css" href="../../../dhtmlxWindows/codebase/skins/dhtmlxwindows_dhx_blue.css">
    <script src="../../../dhtmlxWindows/codebase/dhtmlxwindows.js"></script>

This is recommended way to getting more performance.

2. Container module.

Container is a common module used in layout, windows, accordion, tabbar.

Just add

      <script src="codebase/dhtmlxcontainer.js" type="text/javascript" charset="utf-8"></script>

dhtmlxLayout will no work without it.

3. Skin autodetect functionality.

By the default skin is dhx_skyblue (the new one in 2.5 version), but you also can use old dhx skin, dhx_blue and dhx_black.

Skin autodetection means detect and set corresponding skin by the layout itself depending on attached css skin file.

To set not default skin you shoyuld pass corresponding skin name as 3-rd argument into layout's constructor (also change skin on-the-fly feature appears in 2.5 version).

But now it no needed to set skin to layout. Skin will inherit to all attached components in the layout.

Just include needed skin css

    <link rel="stylesheet" type="text/css" href="codebase/skins/dhtmlxlayout_dhx_blue.css">

And init layout with 2 arguments

    var dhxLayout = new dhtmlXLayoutObject(document.body, "3L");

And layout will automatically set skin to “dhx_blue” to itself and all attached components.