Common Mistakes
From WinLIKE Wiki
When people start to use WinLIKE without seeing the provided samples they often use WinLIKE in an inefficient way. They end up having to redesign their pages later to take full advantage of WinLIKE's capabilities. That's why the most common mistakes are explained here:
1. Creating Windows at Runtime
With WinLIKE it is possible to create windows during runtime. But in general it is better to predefine (invisible) windows and to use and load them when they are necessary. This is faster, you can re-use windows with existing properties (size, position etc.), it's less error-prone and much easier for development.
See for example 41_develop_links.html
2. Reloading the Root Page of an Application
Usually a WinLIKE website or web appication should load the main (root or background) page only once. All the other contents are handled within windows. The root page never changes and so there is no reload necessary which would destroy all WinLIKE windows and force a whole WinLIKE reload as well. But if you need to change the root page, just use a WinLIKE window scaled to 100% as a background.
See especially 16_sample_background.html
3. Loading External Content into Windows
Don't use WinLIKE itself to merge content from different server locations into one window-based site (client-side content syndication).
See 48_develop_external.html to see why.
4. Usage of XHTML in WinLIKE main page
WinLIKE is highly optimized in order to be as lightweight and fast as possible. That's why no XHTML (in Mozilla also known as CSS1Compat Mode) is allowed in the WinLIKE root page. It's better not to use a DOCTYPE definition or use <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> (Mozilla BackCompat Mode). Because WinLIKE doesn't care about window content, you can use XHTML in these content pages. But be aware of browser bugs which sometimes result in rendering problems.
