This is an old revision of the document!
Analysis of rendering labels on other sites
Now the merkalt sites (excluding wallstickers) are used next scheme: after the customer changed label parameters (type the text on the lines and leave the field; select motif, background or text color) there is blocked all controls of product and called script that renders label. The rendering saved in a temporary image file. On the page the label's preview defines as the “image” html-element which URL links to the rendered image file.
There are two update methods on label rendering. After each character set in the lines the label delayed update started (timeout is 500 ms). After each click (color changing, motif selecting, etc.) the label update started without a pause. When update of label preview is ready it applied unless user made any other action - this case the change not applied and preview generation starts again. Label's image URL is not the link to the updated image file as it now on Merkalt. There is an URL to script which generates label image and returns the image. Each user action launches a changing parameters of this URL and then receives updated image.
A similar algorithm for rendering the label as in the previous case. The only difference is that the process takes place without timeout. Что лучше, почему?
There are div elements as container for the label. All changes made by the user are displayed directly in the container html markup using javascript. //Надо написать что подобный способ используется в валлстикерс? Чем лучше, чем хуже. Имеет ли смысл в перспективе использовать этот метод? //
The principle of label rendering is similar to the previous case