×
Namespaces

Variants
Actions
(Difference between revisions)

Developer guidelines for new Nokia Asha Web Apps runtime proxy server release

From Nokia Developer Wiki
Jump to: navigation, search
hamishwillee (Talk | contribs)
hamishwillee (Talk | contribs)
m (Hamishwillee - Bot update - Fix metadata)
 
Line 1: Line 1:
 
[[Category:Nokia Asha Web Apps]]
 
[[Category:Nokia Asha Web Apps]]
 
{{Abstract|This article provides information about the new Nokia Asha Web Apps Runtime Proxy server release. }}
 
{{Abstract|This article provides information about the new Nokia Asha Web Apps Runtime Proxy server release. }}
{{ArticleMetaData <!-- v1.2 -->
+
{{ArticleMetaData <!-- v1.3 -->
 
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
 
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
 
|installfile= <!-- Link to installation file (e.g. [[Media:The Installation File.sis]]) -->
 
|installfile= <!-- Link to installation file (e.g. [[Media:The Installation File.sis]]) -->
Line 7: Line 7:
 
|sdk= <!-- SDK(s) built and tested against (e.g. [http://linktosdkdownload/ Qt SDK 1.1.4]) -->
 
|sdk= <!-- SDK(s) built and tested against (e.g. [http://linktosdkdownload/ Qt SDK 1.1.4]) -->
 
|platform= <!-- Compatible platforms - e.g. Symbian^1 and later, Qt 4.6 and later -->
 
|platform= <!-- Compatible platforms - e.g. Symbian^1 and later, Qt 4.6 and later -->
|devicecompatability= <!-- Compatible devices e.g.: All* (must have internal GPS) -->
 
 
|dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 -->
 
|dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 -->
 
|signing= <!-- Signing requirements - empty or one of: Self-Signed, DevCert, Manufacturer -->
 
|signing= <!-- Signing requirements - empty or one of: Self-Signed, DevCert, Manufacturer -->
|capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. -->
+
|capabilities= <!-- Required capabilities for code (e.g. ID_CAP_LOCATION, ID_CAP_NETWORKING) -->
 
|keywords= <!-- APIs, classes and methods (e.g. QSystemScreenSaver, QList, CBase -->
 
|keywords= <!-- APIs, classes and methods (e.g. QSystemScreenSaver, QList, CBase -->
 
|language= <!-- Language category code for non-English topics - e.g. Lang-Chinese -->
 
|language= <!-- Language category code for non-English topics - e.g. Lang-Chinese -->
Line 22: Line 21:
 
|creationdate= 20130416
 
|creationdate= 20130416
 
|author= [[User:isalento]]
 
|author= [[User:isalento]]
 +
<!-- The following are not in current metadata -->
 +
|devicecompatability= <!-- Compatible devices e.g.: All* (must have internal GPS) -->
 
}}
 
}}
  
Attention, Series 40 web app developers: An updated runtime proxy rendering engine on our servers rolled out last week. The new server release has some implications for your future development efforts. This update features Mozilla's 'Gecko' browser engine and will improve the layout and JavaScript processing of the web app content. The updated engine has significant improvements in terms of performance and capabilities compared to the 'Rhino'  engine it replaces. The new engine also complies strictly with the W3C standard, and offers more stability and compliance with other standards, including HTML5 and CSS3.
+
Attention, Series 40 web app developers: An updated runtime proxy rendering engine on our servers rolled out last week. The new server release has some implications for your future development efforts. This update features Mozilla's 'Gecko' browser engine and will improve the layout and JavaScript processing of the web app content. The updated engine has significant improvements in terms of performance and capabilities compared to the 'Rhino'  engine it replaces. The new engine also complies strictly with the W3C standard, and offers more stability and compliance with other standards, including HTML5 and CSS3.
  
 
Here are five new developer guidelines for your web apps:
 
Here are five new developer guidelines for your web apps:
Line 30: Line 31:
 
*Series 40 web apps supports a single html document only even in the previous release. However some developers used some workarounds and made multiple html documents in a web app. These workarounds will not work with the updated engine.
 
*Series 40 web apps supports a single html document only even in the previous release. However some developers used some workarounds and made multiple html documents in a web app. These workarounds will not work with the updated engine.
  
*<tt>element.innerText</tt> is no longer supported. Instead, you should use <tt>element.innerHTML</tt>
+
*{{Icode|element.innerText}} is no longer supported. Instead, you should use {{Icode|element.innerHTML}}
 
<code javascript>
 
<code javascript>
 
document.getElementById('el').innerText="Hello World";  // not supported
 
document.getElementById('el').innerText="Hello World";  // not supported
Line 36: Line 37:
 
</code>
 
</code>
  
*<tt>mwl.timer</tt> is always preferred over native JavaScript timer. The latter expires at the server, and so may not be useful to you.  
+
*{{Icode|mwl.timer}} is always preferred over native JavaScript timer. The latter expires at the server, and so may not be useful to you.  
  
 
Examples:
 
Examples:
Line 47: Line 48:
 
</code>
 
</code>
  
* Use either <tt><body onload="init()"></tt> or JavaScript <tt>window.onload=function(){...};</tt>, but not both. If mwl API needs to be called in an onload event, then 'body onload' is preferred.
+
* Use either {{Icode|<body onload="init()">}} or JavaScript {{Icode|window.onload=function(){...};}}, but not both. If mwl API needs to be called in an onload event, then 'body onload' is preferred.
* When using the <tt><form></tt> tag without ''action'' attribute, <tt><input type="button"></tt> should be used. Use of <tt><input type='submit'></tt> is only allowed when form has an ''action'' attribute with an absolute URL.
+
* When using the {{Icode|<form>}} tag without ''action'' attribute, {{Icode|<input type="button">}} should be used. Use of {{Icode|<input type='submit'>}} is only allowed when form has an ''action'' attribute with an absolute URL.
 
Examples:
 
Examples:
 
<code html4strict>
 
<code html4strict>

Latest revision as of 09:01, 16 May 2013

This article provides information about the new Nokia Asha Web Apps Runtime Proxy server release.

Article Metadata
Article
Created: isalento (16 Apr 2013)
Last edited: hamishwillee (16 May 2013)

Attention, Series 40 web app developers: An updated runtime proxy rendering engine on our servers rolled out last week. The new server release has some implications for your future development efforts. This update features Mozilla's 'Gecko' browser engine and will improve the layout and JavaScript processing of the web app content. The updated engine has significant improvements in terms of performance and capabilities compared to the 'Rhino' engine it replaces. The new engine also complies strictly with the W3C standard, and offers more stability and compliance with other standards, including HTML5 and CSS3.

Here are five new developer guidelines for your web apps:

  • Series 40 web apps supports a single html document only even in the previous release. However some developers used some workarounds and made multiple html documents in a web app. These workarounds will not work with the updated engine.
  • element.innerText is no longer supported. Instead, you should use element.innerHTML
document.getElementById('el').innerText="Hello World";  // not supported
document.getElementById('el').innerHTML="Hello World"; // correct way
  • mwl.timer is always preferred over native JavaScript timer. The latter expires at the server, and so may not be useful to you.

Examples:

//Do Not use. This timer will expire at server only.
setTimeout("functionName()", 3500);
 
//Use Instead. This timer will expire at client side
mwl.timer('timerName',3500,1,'functionName();');
  • Use either {{{1}}} or JavaScript {{{1}}}, but not both. If mwl API needs to be called in an onload event, then 'body onload' is preferred.
  • When using the <form> tag without action attribute, {{{1}}} should be used. Use of {{{1}}} is only allowed when form has an action attribute with an absolute URL.

Examples:

<!-- Do Not Use -->
<form id="fid" name="fbform"> feedback<br/>
<input type="text" name="tb" id="tb"/><br/>
<input type="submit" value="Send" name="pb" id="pb" onclick="validate();"/>
</form>
 
<!-- Use Instead -->
<form id="fid" name="fbform"> feedback<br/>
<input type="text" name="tb" id="tb"/><br/>
<input type="button" value="Send" name="pb" id="pb" onclick="validate();"/>
</form>
This page was last modified on 16 May 2013, at 09:01.
160 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×