From: Andrea S. <asc...@us...> - 2005-03-08 23:44:14
|
Update of /cvsroot/expressions/htdocs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv5913 Modified Files: about.html development.html Log Message: make pages validate in validator.w3.org Index: development.html =================================================================== RCS file: /cvsroot/expressions/htdocs/development.html,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** development.html 8 Mar 2005 23:38:24 -0000 1.2 --- development.html 8 Mar 2005 23:44:04 -0000 1.3 *************** *** 41,48 **** cvs -d:pserver:ano...@cv...:/cvsroot/expressions login cvs -z3 -d:pserver:ano...@cv...:/cvsroot/expressions co <em>modulename</em></pre> ! Instead of <tt><em>modulename</em></tt> use <tt>docs</tt> for the documentation. When you are asked for a password for <em>anonymous</em>, just press Enter.<br/>If you run into any problems with that, please have a look at the <a href="http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1">SourceForge <acronym title="Concurrent Versions System; software to coordinate several developers">CVS</acronym> documentation</a>. If that doesn't solve your problem, let us know. </li> <li>We also have a <a href="http://lists.sourceforge.net/lists/listinfo/expressions-cvs/"><acronym title="Concurrent Versions System; software to coordinate several developers">CVS</acronym> commit mailing list</a> that you can use to keep track of what's going on.</li> <li>The <a href="http://sourceforge.net/projects/expressions/">project's SourceForge page</a> has some more information, but we'll try to keep this web site in sync with the SourceForge page.</li> </div> </body> --- 41,49 ---- cvs -d:pserver:ano...@cv...:/cvsroot/expressions login cvs -z3 -d:pserver:ano...@cv...:/cvsroot/expressions co <em>modulename</em></pre> ! Instead of <tt><em>modulename</em></tt> use <tt>docs</tt> for the documentation. When you are asked for a password for <em>anonymous</em>, just press Enter.<br/>If you run into any problems with that, please have a look at the <a href="http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1">SourceForge <acronym title="Concurrent Versions System; software to coordinate several developers">CVS</acronym> documentation</a>. If that doesn't solve your problem, let us know. </li> <li>We also have a <a href="http://lists.sourceforge.net/lists/listinfo/expressions-cvs/"><acronym title="Concurrent Versions System; software to coordinate several developers">CVS</acronym> commit mailing list</a> that you can use to keep track of what's going on.</li> <li>The <a href="http://sourceforge.net/projects/expressions/">project's SourceForge page</a> has some more information, but we'll try to keep this web site in sync with the SourceForge page.</li> + </ul> </div> </body> Index: about.html =================================================================== RCS file: /cvsroot/expressions/htdocs/about.html,v retrieving revision 1.2 retrieving revision 1.3 diff -C2 -d -r1.2 -r1.3 *** about.html 8 Mar 2005 23:38:24 -0000 1.2 --- about.html 8 Mar 2005 23:44:04 -0000 1.3 *************** *** 46,50 **** </div> <p>We will develop two clients, one for cell phones/<acronym title="Personal Digital Assistant; a handheld computer">PDA</acronym>s and one for desktop/laptop computers. Both clients can post to a blog. Both can save entries so that they can be posted later. The desktop client keeps an offline copy of old blog postings (made through this client or any other way the blogging platform supports). Both clients can synchronise with each other, so that it is possible to write an entry with the desktop client, synchronise it with a cell phone and post the entry from there, and vice versa.</p> ! <p>We already have a few ideas for some technical details (shown in blue in <a href="#figure-scenario">the scenario</a>. <ul> <li>Both clients will be implemented in Java, so that they can run on as many operating systems as possible (hopefully...).</li> --- 46,50 ---- </div> <p>We will develop two clients, one for cell phones/<acronym title="Personal Digital Assistant; a handheld computer">PDA</acronym>s and one for desktop/laptop computers. Both clients can post to a blog. Both can save entries so that they can be posted later. The desktop client keeps an offline copy of old blog postings (made through this client or any other way the blogging platform supports). Both clients can synchronise with each other, so that it is possible to write an entry with the desktop client, synchronise it with a cell phone and post the entry from there, and vice versa.</p> ! <p>We already have a few ideas for some technical details (shown in blue in <a href="#figure-scenario">the scenario</a>.</p> <ul> <li>Both clients will be implemented in Java, so that they can run on as many operating systems as possible (hopefully...).</li> *************** *** 53,58 **** <li>The two clients will synchronise via Bluetooth and maybe via <acronym title="infrared">IR</acronym>.</li> </ul> ! </p> ! <p>Do you have any comments about the scenario? Let us know via the <a href="http://lists.sourceforge.net/lists/listinfo/expressions-development/">development mailing list</a> or the <a href="http://sourceforge.net/projects/expressions/">forum</a>. </div> </body> --- 53,57 ---- <li>The two clients will synchronise via Bluetooth and maybe via <acronym title="infrared">IR</acronym>.</li> </ul> ! <p>Do you have any comments about the scenario? Let us know via the <a href="http://lists.sourceforge.net/lists/listinfo/expressions-development/">development mailing list</a> or the <a href="http://sourceforge.net/projects/expressions/">forum</a>.</p> </div> </body> |