Table of Contents
Advertisement
9. Try to avoid using too many widgets in a page. Often widgets are placed outside of the visible area
or their transparency is controlled by a tag. Since widgets are loaded even if they are not visible
having too many widgets in a page can slow down significantly the page change time.
10. If possible, split a page with too many widgets in multiple pages with less widget.
11. For popping up new graphic elements in a page, prefer dialog pages with controlled positioning to
transparent widgets
12. Have a check in opt folder to see if static optimization is working as expected: the widgets z-order
might need to be changed to fix it
13. Numeric fields are often used to run JavaScript code on OnDataUpdate event even if the widget
doesn't need to be visible on the page. In this case place the widget outside the page visible area
instead of making it invisible, altering font color or visibility property. In fact in the latter case it is
likely to end up with many left over wedges.
14. Use HotSpot button if you need a touch area to react to user inputs
15. If you reuse a widget from the gallery or you create your own, remember to set the right optimization
properties (either static/dynamic/auto) or check if that kind of widget has the desired optimization
properties. For example button widgets are dynamic widgets. For instance, if you use a button
widget just for its frame it won't be optimized since the button widget is dynamic. If you just need the
frame please use the UP Image SVG from the widget gallery.
16. With many pages having many dynamic widgets and using a common template the suggested
configuration is to set:
a. template static optimization flag set to true
b. page static optimization flat set to false (background is already provided by the template)
So, the background image can be reused among many different pages saving a lot of RAM that can
be used for page caching.
17. Avoid using dynamic widgets like buttons only for the page background to make graphical effect
without any real use of the buttons, instead use widget images (which can be obtained from the
gallery) to apply the same graphical effect. This will reduce the load time of the page if we design it
in an optimal way.
Follow an example of good and bad usage of Static optimization.
Figure 322
ACGM0195V1EN
HMWIN Studio User Manual
(http://www.w3.org/TR/SVGTiny12/) supported.
315
Advertisement
Table of Contents
