Differences

This shows you the differences between two versions of the page.

--- merkalt:rendering_analysis [2013/09/05 06:39] – dmitriy
+++ merkalt:rendering_analysis [2013/09/05 09:20] (current) – ramil
@@ Line 1: / Line 1: @@
 **Analysis of rendering labels on other sites**
-Now the merkalt sites (excluding wallstickers) are using the next schemz: after the customer changed label parameters (type the text on the lines and leave the field; select motif, background or text color) there is a lock of all controls of product and execution of script in the background which renders label. The rendering result is saved in a temporary image file. In the HTML the label's preview is defined as the "image" html-element which URL linked with the rendered image file.
+Now the merkalt sites (excluding wallstickers) are using the next schema: after the customer changed label parameters (type the text on the lines and leave the field; select motif, background or text color) there is a lock of all controls of product and execution of script in the background which renders label. The rendering result is saved in a temporary image file. In the HTML the label's preview is defined as the "image" html-element which URL linked with the rendered image file.
   * http://www.nordicprint.no/navnelapper.
 Update performed after each character set in the lines fields of the label preview constructor. On each change of solitary character, delayed update is 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 change of parameters for image URL and then receives updated image.  //примеры Url для картинки на http://www.nordicprint.no/navnelapper приведи. я не понял например меняется там урл или нет. Если да почему там нет эффекта с исчеезанием/появлением, если нет как они насчет кеша решают проблему//
+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 change of parameters for image URL and then receives updated image.
+For example, after typing text "test" in the Linje 1 generates URL to preview image as
+/extensions/ColorStickers/operations.php?&operation=preview&bk=undefined&g=0&rand=7113.364054360752&c=000000&l1=test&l2=&l3=&f=1 for preview.
+If we change the color of the text to blue the URL will be
+/extensions/ColorStickers/operations.php?&operation=preview&bk=undefined&g=0&rand=5381.829658103297**&c=0c75eb**&l1=test&l2=&l3=&f=1. There is changed parameter "c". By changing label preview URL parameters they gets new label preview.
   * https://www.navnelapper.no/klassiske.
-A similar algorithm for rendering the label as in the previous case. The only difference is that the process takes place without timeout. Delayed updating the preview of label is better then immediate update because of it calls asynchronously and does not prevent the user to do some actions on. //Не согласен, а без таймаута не асинхронно?//
+A similar algorithm for rendering the label as in the previous case. The only difference is that the process takes place without timeout. It is better to render label without delay. In the previous case, probably using the timeout they would want a certain visual effect.
   * http://www.smartlapper.no/navnelapper/bestill.
 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.
 This method is used on the merkalt's wallstickers site now.
-The advantages of this method is that the whole process of rendering labels are on the client side, no server requests are performed and therefore there is no need to use lockers or calls rendering by timeout as preview change is immediate. The disadvantage of this method is that we need to adapt the layout preview of the label for the main types of web-browsers. //Я не понял что это значит - adapt как? Там по идее только работы много//  This method is one of the best in terms of performance. Perhaps it could be considered to be used.
+The advantages of this method is that the whole process of rendering labels are on the client side, no server requests are performed and therefore there is no need to use lockers or calls rendering by timeout as preview change is immediate. The disadvantage of this method is that it need much more work. This method is one of the best in terms of performance. Perhaps it could be considered to be used.
   * http://navnetrykk.no/bestill-navnelapper.html
 The principle of label rendering is similar to the previous case