Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.
Talk:Series 40: SVG resources localization
Hamishwillee - Document the trade offs?
Thanks for this article. There is certainly a place for SVG in games menus, and given that, being able to localise them is important.
It is possibly worth updating your introduction slightly with more clarification of the domains in which you might use the SVG approach (e.g. games) because obviously it is more efficient and easier to use a high level component like LCDUI TextField or LCDUI TextBox or LWUIT TextArea etc if that sort of menu is suitable.
What would be great is to write a companion article (or extend this one) which discusses more generally the tradeoffs between using SVG and other methods for dealing with the complex problem of scaling. This could cover for example the fact that SVG consumes more memory, and that you may need to do work to scale the borders of touchable elements in code. In contrast drawing to Canvas directly means that you need to handle all scaling problems, which could be more complicated for developers. The article could compare and contrast Canvas versus SVG drawing, explain step-by-step how to create the Mystic Square Screen using both ways and mention each method’s strengths and weaknesses (maybe include screenshots taken from devices with different resolutions).
04:03, 15 August 2012 (EEST)
Izinin - tradeoffs between using SVG and other methods
Good point and good topic for a wiki article. Thank you for the suggestion. I will come back to Series 40 soon.
How easy LWUIT in development is depends on development tool because LWUIT operates resources heavily. I will need learn more Nokia developing tools offering.
As for SVG document -- all effects here are supposed to be made by hand -- but there is good point, once you grasp the technology , you do not depends on tools any more :). Thinking about WEB applications growing popularity that is a valuable knowledge.
SVG animation is fired when an element is getting input focus:
<animateTransform begin="button_0.focusin" attributeName="transform" type="scale" to="2" dur="0.25s" fill="freeze" additive="sum" />
On the example above, you can see how concise the animation definition is and persons who have QtQuck, Silverlight background will find many common things in the expression.
10:15, 20 August 2012 (EEST)