cvs: php-gtk-web / index.php news.rss

scottmattocks		Thu Aug 10 17:25:45 2006 UTC

  Modified files:              
    /php-gtk-web	index.php news.rss 
  Log:
  A few readability changes and some more links.
  
http://cvs.php.net/viewvc.cgi/php-gtk-web/index.php?r1=1.124&r2=1.125&diff_format=u
Index: php-gtk-web/index.php
diff -u php-gtk-web/index.php:1.124 php-gtk-web/index.php:1.125
--- php-gtk-web/index.php:1.124	Thu Aug 10 15:00:15 2006
+++ php-gtk-web/index.php	Thu Aug 10 17:25:45 2006
@@ -1,6 +1,6 @@
 <?php
 /*
- * $Id: index.php,v 1.124 2006/08/10 15:00:15 scottmattocks Exp $ 
+ * $Id: index.php,v 1.125 2006/08/10 17:25:45 scottmattocks Exp $ 
  */
 
 // Start output buffering in order to grab the data from the documentation
@@ -59,11 +59,10 @@
 
 <h1>Documentation Filling Out</h1>
 <p><span class="newsDate">[10-August-2006]</span>
-This week, the <a href="http://gtk.php.net/docs.php">PHP-Gtk2 documentation</a> broke the 44.44% barrier: nearly half of the classes and their methods, properties and signals are documented. PHP-Gtk2 consists of 202 classes with nearly 2900 methods, and several signals and properties. PHP-Gtk2 is not half as useful if
-there is no documentation and examples the developer can rely on.
+This week, the <a href="http://gtk.php.net/docs.php">PHP-Gtk2 documentation</a> broke the 44.44% barrier: nearly half of the classes and their methods, properties and signals are documented. PHP-GTK 2 consists of 202 classes with nearly 2,900 methods, and many signals and properties. As the documentation matures, PHP-GTK 2 becomes easier to work with as the answers to many common problems become easier to find. 
 </p>
 <p>
-We ask you to help us in filling the white spots and creating examples. Writing documentation helps the project, but more you will learn from experimenting with new methods, and get a better understanding of the inner workings of the project. Interested? The doccing tutorial explains the first steps, and the php-gtk-doc mailing list is the central place for all manual issues. All help, examples and documentation, is appreciated.
+We ask you to help us fill in the white spaces and create examples for others to learn from. Writing documentation not only helps the project, but also helps you learn through experimenting with new methods, and gain a better understanding of the inner workings of the project. Interested? The <a href="http://gtk.php.net/resources.php">doccing tutorial</a> explains the first steps, and the <a href="http://gtk.php.net/resources.php">php-gtk-doc mailing list</a> is the central place for all manual issues. All help creating examples and writing or translating documentation, is appreciated.
 </p>
 
 <?php hdelim(); ?>
http://cvs.php.net/viewvc.cgi/php-gtk-web/news.rss?r1=1.30&r2=1.31&diff_format=u
Index: php-gtk-web/news.rss
diff -u php-gtk-web/news.rss:1.30 php-gtk-web/news.rss:1.31
--- php-gtk-web/news.rss:1.30	Thu Aug 10 15:00:15 2006
+++ php-gtk-web/news.rss	Thu Aug 10 17:25:45 2006
@@ -32,18 +32,20 @@
  <title>Documentation Filling Out</title>
  <link>http://gtk.php.net</link>
  <description>
-This week, the PHP-Gtk2 documentation broke the 44.44% barrier: nearly
+This week, the PHP-GTK 2 documentation broke the 44.44% barrier: nearly
 half of the classes and their methods, properties and signals are
-documented. PHP-Gtk2 consists of 202 classes with nearly 2900 methods,
-and several signals and properties. PHP-Gtk2 is not half as useful if
-there is no documentation and examples the developer can rely on.
-
-We ask you to help us in filling the white spots and creating examples.
-Writing documentation helps the project, but more you will learn from
-experimenting with new methods, and get a better understanding of the
-inner workings of the project. Interested? The doccing tutorial explains
-the first steps, and the php-gtk-doc mailing list is the central place
-for all manual issues. All help, examples and documentation, is appreciated.
+documented. PHP-GTK 2 consists of 202 classes with nearly 2,900 methods,
+and many signals and properties. As the documentation matures, PHP-GTK 2
+becomes easier to work with as the answers to many common problems become
+easier to find.
+
+We ask you to help us fill in the white spaces and create examples for
+others to learn from. Writing documentation not only helps the project, 
+but also helps you learn through experimenting with new methods, and gain
+a better understanding of the inner workings of the project. Interested? 
+The doccing tutorial explains the first steps, and the php-gtk-doc mailing
+list is the central place for all manual issues. All help creating examples
+and writing or translating documentation, is appreciated.
  </description>
  <dc:date>2006-08-10</dc:date>
 </item>