diff -r 87cfa131b535 -r e7e0ae78773e configurationengine/doc/plugins/general.rst --- a/configurationengine/doc/plugins/general.rst Fri Mar 12 08:30:17 2010 +0200 +++ b/configurationengine/doc/plugins/general.rst Tue Aug 10 14:29:28 2010 +0300 @@ -55,7 +55,7 @@ - + @@ -71,7 +71,7 @@ - The container is in http://www.symbianfoundation.org/xml/implml/1, the root element of implml namespace must always be container - The ruleml is in http://www.s60.com/xml/ruleml/2 - - The content is in xmlns="http://www.s60.com/xml/content/3" + - The content is in xmlns="http://www.s60.com/xml/content/2" When reading the implementation file, ConE checks the document root and its namespace to find out from namespace to start parsing. @@ -157,7 +157,7 @@ - + CustomSettings.StartupSoundFile.localPath configures @@ -167,15 +167,15 @@ - - + + - + @@ -291,7 +291,7 @@ - + X.Y configures X.Z = X.Y @@ -310,7 +310,7 @@ - + X.Y configures X.Z = X.Y @@ -356,10 +356,10 @@ .. code-block:: xml - - - - + + + + Tags can also get their values from ConfML settings, which can be referenced in the usual way: @@ -537,7 +537,7 @@ - + @@ -610,12 +610,10 @@ - - - + @@ -623,18 +621,4 @@ -In the above example the content is copied to \epoc32\data\widgets\some_dir\text.wgz. - - -.. rubric:: Footnotes - -.. [#multi-content-note] In this case the run-time behavior would still be same; ContentML - allows multiple ``output`` elements. However, this might not be the case for all - implementation languages. - -.. [#legacy-implml-root-name-note] The specifications for the legacy implementation - languages CRML and GenConfML do give the root element names, and say that each - implementation must be in its own crml/gcfml file. - It is recommended to stick to this convention for these two implementation languages - also in the future. Indeed, using them in a multi-implementation file has not been - tested and may not even work correctly. +In the above example the content is copied to \\epoc32\\data\\widgets\\some_dir\\text.wgz.