I have been using this joke - suite 7 thing for a while and today i hit the most stupid and ridicious implementation of the collapse() and hide() methods for a layout cell.
If you have attached iframe and have for example a page with drawings, map navigation or whatever complex thing, once the user clicks the collapse arrow YOU LOSE ALL THE INFORMATION because the content gets removed from the dom!!!
NEVER EVER USE THIS LIBRARY IN A REAL PROJECT OR U WILL HAVE MAJOR PROBLEMS and LOSE YOUR CONTRACT!!!
What I believe is that they don’t provide more information about how is internally implemented the library, and thus cause that some people face this type of issues in the middle of a development process.
In your case the solution is not abandoning the whole library or persuade others to do so. Is just have the feature of adding an iframe as the content of a layout cell. This feature is not hard to implement if you create a component that inherit from the internal View class and properly handle the life of the iFrame. So I believe that could be a good idea if the library exposes the View class by default together with the methods of domvm that are commonly used.
If this is their main bussiness and somebody really use this library in a REAL WORLD projects they would have bombarded their forum with bug reports and negative comments.
Its not normal to have a HIDE method that REMOVES the dom and makes ur application LOSE all the state like socket connections, drawings and so on. THIS IS RIDICIOUS. They should give the option for the user to decide what would happen with the dom when u switch to another tab or hide some cell.
In the middle of a project u realize that u are f*cked up with this ridicious joke!
How could u have Suite 5 and after that release something which is like 30% ready and full of bugs and ridicious logic!
RUN AWAY FROM THIS CRAP!!!
Get a guaranteed answer from DHTMLX technical support team
under the most suitable support plan
