Thread: [phpwebapp-commits] CVS: web_app/doc to_do.txt,1.10,1.11 changes.txt,1.7,1.8
Brought to you by:
dashohoxha
Menu
▾
▴
phpwebapp-commits
|
From: Dashamir H. <das...@us...> - 2004-07-23 09:40:26
|
Update of /cvsroot/phpwebapp/web_app/doc In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv7295/doc Modified Files: to_do.txt changes.txt Log Message: Index: to_do.txt =================================================================== RCS file: /cvsroot/phpwebapp/web_app/doc/to_do.txt,v retrieving revision 1.10 retrieving revision 1.11 diff -C2 -d -r1.10 -r1.11 *** to_do.txt 22 Jul 2004 16:01:38 -0000 1.10 --- to_do.txt 23 Jul 2004 09:40:17 -0000 1.11 *************** *** 1,62 **** - - Use the new framework with the other web applications - (smewapp etc.) in order to test the new parser (and the conversion tool). - - Fix some bugs in the documentation application and improve its contents a little bit. - - - Reformat all the files (automatically with emacs). - - - Make any small improvments in the documentation. - - - Make a new release of phpwebapp that includes the latest - changes in the parser any improvments in the docs, etc. - - ---------------------------------------------------------------------- - - * When switching an existing web application to the new version - of the framework (with the xml parser), these modifications - need to be done to the templates: - - 1 - Find and remove all <Header> and <Footer> tags and place their - contents outside the <Repeat> element. In case that the - recordset of the <Repeat> is a paged recordset and page variables - ({{PrevPage}}, {{NextPage}} etc.) are used for navigation, - then put the navigation part of the template inside the element - <RSNavig>. - - 2 - Replace 'not-equal operator' <> by !=, in the condition of <If> - elements: <If condition="'{{CurrPage}}'<>'{{PrevPage}}'"> - If there is any 'smaller-than' operator < in attribute values, - replace it by &lt;. If it is in the contents of an element - (e.g. in the contents of a <Query> element), then either replace - it by < or enclose the query inside <![CDATA[...]]>, like - this: <Query><![CDATA[ . . . ]]></Query> - - 3 - Replace the old usage of 'checked' in checkboxes with the new - usage; replace {{checked_var}} with checked="{{checked_var}}". - Do the same for the 'selected' attribute of the listboxes: - replace {{selected_var}} with selected="{{selected_var}}" - - 4 - Convert all the templates to clean XHTML code (convert all tags - and attributes to lowercase, replace <img...> by <img ... />, - etc.). Maybe 'tidy' can be used for this, however sometimes - it does not produce the desired results (because of the framework - tags). - - 5 - Add these lines at the beginning of the root templates: - <?xml version="1.0" encoding="iso-8859-1"?> - <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" - "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> - <html xmlns="http://www.w3.org/1999/xhtml" lang="EN"> - - 6 - Each xml parser is required to process the entities: & < - > " and ' and to return the corresponding character - instead of the entity itself. So, it is neccessary to replace - in the templates all the xml builtin entities, like this: - & --> &amp; - < --> &lt; - > --> &gt; - " --> &quot; - ' --> &apos; - --- 1,3 ---- Index: changes.txt =================================================================== RCS file: /cvsroot/phpwebapp/web_app/doc/changes.txt,v retrieving revision 1.7 retrieving revision 1.8 diff -C2 -d -r1.7 -r1.8 *** changes.txt 16 Jul 2004 14:45:14 -0000 1.7 --- changes.txt 23 Jul 2004 09:40:17 -0000 1.8 *************** *** 118,122 **** ------------------------------------------------------------------- - ------------------------------------------------------------------- * Added the tag <example>. It can be used like this: --- 118,121 ---- *************** *** 146,149 **** --- 145,195 ---- ------------------------------------------------------------------- + + * When switching an existing web application to the new version + of the framework (with the xml parser), these modifications + need to be done to the templates: + + 1 - Find and remove all <Header> and <Footer> tags and place their + contents outside the <Repeat> element. In case that the + recordset of the <Repeat> is a paged recordset and page variables + ({{PrevPage}}, {{NextPage}} etc.) are used for navigation, + then put the navigation part of the template inside the element + <RSNavig>. + + 2 - Replace 'not-equal operator' <> by !=, in the condition of <If> + elements: <If condition="'{{CurrPage}}'<>'{{PrevPage}}'"> + If there is any 'smaller-than' operator < in attribute values, + replace it by &lt;. If it is in the contents of an element + (e.g. in the contents of a <Query> element), then either replace + it by < or enclose the query inside <![CDATA[...]]>, like + this: <Query><![CDATA[ . . . ]]></Query> + + 3 - Replace the old usage of 'checked' in checkboxes with the new + usage; replace {{checked_var}} with checked="{{checked_var}}". + Do the same for the 'selected' attribute of the listboxes: + replace {{selected_var}} with selected="{{selected_var}}" + + 4 - Convert all the templates to clean XHTML code (convert all tags + and attributes to lowercase, replace <img...> by <img ... />, + etc.). Maybe 'tidy' can be used for this, however sometimes + it does not produce the desired results (because of the framework + tags). + + 5 - Add these lines at the beginning of the root templates: + <?xml version="1.0" encoding="iso-8859-1"?> + <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml" lang="EN"> + + 6 - Each xml parser is required to process the entities: & < + > " and ' and to return the corresponding character + instead of the entity itself. So, it is neccessary to replace + in the templates all the xml builtin entities, like this: + & --> &amp; + < --> &lt; + > --> &gt; + " --> &quot; + ' --> &apos; + ------------------------------------------------------------------- |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X