anjuta r4653 - in trunk: . www/htdocs
- From: sgranjoux svn gnome org
- To: svn-commits-list gnome org
- Subject: anjuta r4653 - in trunk: . www/htdocs
- Date: Sat, 31 Jan 2009 14:15:28 +0000 (UTC)
Author: sgranjoux
Date: Sat Jan 31 14:15:28 2009
New Revision: 4653
URL: http://svn.gnome.org/viewvc/anjuta?rev=4653&view=rev
Log:
* www/htdocs/anjuta_news.html:
* www/htdocs/authors.php:
* www/htdocs/development.php:
* www/htdocs/downloads.php:
* www/htdocs/features.php:
* www/htdocs/home.php:
* www/htdocs/tasks.php:
Copy edited Web pages, making numerous small fixes to grammar and
English usage.
Modified:
trunk/ChangeLog
trunk/www/htdocs/anjuta.php
trunk/www/htdocs/anjuta_news.html
trunk/www/htdocs/authors.php
trunk/www/htdocs/development.php
trunk/www/htdocs/features.php
trunk/www/htdocs/home.php
trunk/www/htdocs/tasks.php
Modified: trunk/www/htdocs/anjuta.php
==============================================================================
--- trunk/www/htdocs/anjuta.php (original)
+++ trunk/www/htdocs/anjuta.php Sat Jan 31 14:15:28 2009
@@ -61,15 +61,15 @@
</ul>
<h3>Documentations</h3>
<ul>
- <li><a href="/documentations/subpage/documents/libanjuta/index.html">Anjuta API docs</a></li>
+ <li><a href="http://library.gnome.org/devel/libanjuta/stable";>Anjuta API docs</a></li>
<li><a href="http://live.gnome.org/Anjuta";>Anjuta wiki</a></li>
- <li><a href="/documentations/subpage/documents/C/anjuta-faqs/anjuta-faqs.html">FAQ [English]</a></li>
+ <li><a href="http://library.gnome.org/devel/anjuta-faqs/stable";>FAQ [English]</a></li>
<!--<li><a href="/documentations/subpage/documents/ja/anjuta-faqs/index.html">FAQ [Japanese]</a></li>
<li><a href="/documentations/subpage/documents/C/anjuta-tutorial/index.html">Tutorial [English]</a></li>
<li><a href="/documentations/subpage/documents/de/anjuta-tutorial/index.html">Tutorial [German]</a></li>
<li><a href="/documentations/subpage/documents/zh_CN/anjuta-tutorial/index.html">Tutorial [Chinese]</a></li> -->
<li><a href="/documentations/subpage/documents/C/anjuta-build-tutorial/index.html">Build Tutorial [English]</a></li>
- <li><a href="/documentations/subpage/documents/C/anjuta-manual/anjuta-manual.html">Manual [English]</a></li>
+ <li><a href="http://library.gnome.org/devel/anjuta-manual/stable";>Manual [English]</a></li>
<!--<li><a href="/documentations/subpage/documents/ja/anjuta-manual/index.html">Manual [Japanese]</a></li> -->
</ul>
<h3>Project Status</h3>
Modified: trunk/www/htdocs/anjuta_news.html
==============================================================================
--- trunk/www/htdocs/anjuta_news.html (original)
+++ trunk/www/htdocs/anjuta_news.html Sat Jan 31 14:15:28 2009
@@ -1,3 +1,12 @@
-<p><a href="http://sourceforge.net/forum/forum.php?forum_id=862696";><strong>Anjuta DevStudio 2.23.91 Cyclone (unstable) released</strong></a><br /><small class="date">2008-09-01 21:42 - <a href="http://sourceforge.net/projects/anjuta/";>Anjuta DevStudio</a></small><br />Anjuta team proudly announces the release of Anjuta DevStudio 2.23.91 that will eventually lead us to stable 2.24.0 release, code named Cyclone. The version number has been bumped from traditional 2.5.x to 2.23.x to honor GNOME release cycle. This is an unstable release for GNOME 2.23.91 release, so be sure to adjust your expectations.
<br /><a href="http://sourceforge.net/forum/forum.php?forum_id=862696";>Read More »</a></p><p><a href="http://sourceforge.net/forum/forum.php?forum_id=857910";><strong>Announce: Anjuta DevStudio 2.5.90 Cyclone (unstable) release</strong></a><br /><small class="date">2008-08-18 21:28 - <a href="http://sourceforge.net/projects/anjuta/";>Anjuta DevStudio</a></small><br />ïAnju
ta team proudly announces the first unstable release Anjuta DevStudio 2.5.90 that will eventually lead us to stable 2.6.0 release, code named Cyclone. This is an unstable release, so be sure to adjust your expectations accordingly. This is release is for upcoming GNOME 2.23.90 release.
<br /><a href="http://sourceforge.net/forum/forum.php?forum_id=857910";>Read More »</a></p><p><a href="http://sourceforge.net/forum/forum.php?forum_id=831211";><strong>Anjuta DevStudio 2.5.0 Cyclone (unstable) released</strong></a><br /><small class="date">2008-06-03 18:35 - <a href="http://sourceforge.net/projects/anjuta/";>Anjuta DevStudio</a></small><br />Anjuta team proudly announces the first unstable release Anjuta DevStudio 2.5.0 that will eventually lead us to stable 2.6.0 release, code named Cyclone. This is an unstable release, so be sure to adjust your expectations accordingly. This is release is for upcoming GNOME 2.23.3 unstable release.
<br /><a href="http://sourceforge.net/fo
rum/forum.php?forum_id=831211">Read More »</a></p><p><a href="http://sourceforge.net/news/?group_id=14222";>Site news archive »</a></p>
+<p><a href="http://sourceforge.net/forum/forum.php?forum_id=910261";><strong>Anjuta DevStudio 2.25.5 (unstable) released</strong></a><br /><small class="date">2009-01-21 21:32 - <a href="http://sourceforge.net/projects/anjuta/";>Anjuta DevStudio</a></small><br />Anjuta 2.25.5 (19 January 2009) -- Johannes Schmid
+<br /><a href="http://sourceforge.net/forum/forum.php?forum_id=910261";>Read More »</a></p><p><a href="http://sourceforge.net/forum/forum.php?forum_id=910256";><strong>Anjuta DevStudio 2.25.4 (unstable) released</strong></a><br /><small class="date">2009-01-21 21:29 - <a href="http://sourceforge.net/projects/anjuta/";>Anjuta DevStudio</a></small><br />The anjuta team is proud to announce the release of Anjuta 2.25.4! Some more info on the release can be found at
+<br /><a href="http://sourceforge.net/forum/forum.php?forum_id=910256";>Read More »</a></p><p><a href="http://sourceforge.net/forum/forum.php?forum_id=891107";><strong>Anjuta DevStudio 2.24.2 Cyclone (stable) released </strong></a><br /><small class="date">2008-11-25 09:35 - <a href="http://sourceforge.net/projects/anjuta/";>Anjuta DevStudio</a></small><br />Anjuta is proud to announce a small update for the stable series with the following changes:
+<br />
+<br />Translations updates:
+<br /><a href="http://sourceforge.net/forum/forum.php?forum_id=891107";>Read More »</a></p><p><a href="http://sourceforge.net/forum/forum.php?forum_id=878754";><strong>Anjuta DevStudio 2.24.1 Cyclone (stable) released</strong></a><br /><small class="date">2008-10-19 16:51 - <a href="http://sourceforge.net/projects/anjuta/";>Anjuta DevStudio</a></small><br />Anjuta team proudly announces the release of Anjuta DevStudio 2.24.1. This is an update for the stable 2.24.x series and fixes some annoying bugs that slipped into the .0 version.
+<br />
+<br />Anjuta 2.24.1 (19 October 2008) -- Johannes Schmid
+<br /><a href="http://sourceforge.net/forum/forum.php?forum_id=878754";>Read More »</a></p><p><a href="http://sourceforge.net/forum/forum.php?forum_id=869510";><strong>Anjuta DevStudio 2.24.0 Cyclone (stable) released</strong></a><br /><small class="date">2008-09-22 15:52 - <a href="http://sourceforge.net/projects/anjuta/";>Anjuta DevStudio</a></small><br />Anjuta team proudly announces the release of Anjuta DevStudio 2.24.0. It is the first stable release of 'Cyclone' series 2.24.x. This release is for GNOME 2.24.0 release due in coming days and contains many bugfixes and updated translations.
+<br /><a href="http://sourceforge.net/forum/forum.php?forum_id=869510";>Read More »</a></p><p><a href="http://sourceforge.net/news/?group_id=14222";>Site news archive »</a></p>
Modified: trunk/www/htdocs/authors.php
==============================================================================
--- trunk/www/htdocs/authors.php (original)
+++ trunk/www/htdocs/authors.php Sat Jan 31 14:15:28 2009
@@ -1,61 +1,61 @@
-<!--
- <table border="0" width="100%" cellspacing="0" cellpadding="5">
- <tbody>
- <tr>
- <td><img border="0" src="image_web/members_icon_ws.jpg" width="48" height="50"></td>
- <td width="100%"><img border="0" src="image_web/authors_title.jpg" width="315"
- height="37"></td></tr></tbody></table>
--->
-
-<?php
+<!--
+ <table border="0" width="100%" cellspacing="0" cellpadding="5">
+ <tbody>
+ <tr>
+ <td><img border="0" src="image_web/members_icon_ws.jpg" width="48" height="50"></td>
+ <td width="100%"><img border="0" src="image_web/authors_title.jpg" width="315"
+ height="37"></td></tr></tbody></table>
+-->
+
+<?php
// get contents of a file into a string
$filename = "svn/AUTHORS";
$handle = fopen($filename, "r");
$contents = fread($handle, filesize($filename));
$contents = preg_replace("/note[^\~]*/im", "", $contents);
-$contents = preg_replace("/^([^\n]+:)\n\-\-\-\-+$/m", "<h3>\\1</h3><ul>", $contents);
-$contents = preg_replace("/^\t([^\<]+)\<([^\>]+\ [^\>]+)\>.*?\(([^\)]+)\).*?$/m", "<li>\\1 <\\2> (\\3)</li>\n", $contents);
-$contents = preg_replace("/^\t([^\<]+)\<([^\>]+\ [^\>]+)\>.*?$/m", "<li>\\1 <\\2></li>\n", $contents);
-$contents = preg_replace("/^\t(.+?)$/m", "<li>\\1</li>\n", $contents);
-$contents = preg_replace("/\n\t\n/m", "</ul>\n", $contents);
-/* $contents = preg_replace("/\n/m", "<br>", $contents);
+$contents = preg_replace("/^([^\n]+:)\n\-\-\-\-+$/m", "<h3>\\1</h3><ul>", $contents);
+$contents = preg_replace("/^\t([^\<]+)\<([^\>]+\ [^\>]+)\>.*?\(([^\)]+)\).*?$/m", "<li>\\1 <\\2> (\\3)</li>\n", $contents);
+$contents = preg_replace("/^\t([^\<]+)\<([^\>]+\ [^\>]+)\>.*?$/m", "<li>\\1 <\\2></li>\n", $contents);
+$contents = preg_replace("/^\t(.+?)$/m", "<li>\\1</li>\n", $contents);
+$contents = preg_replace("/\n\t\n/m", "</ul>\n", $contents);
+/* $contents = preg_replace("/\n/m", "<br>", $contents);
$contents = preg_replace("/\n\t(*)\n+/m", "\n<li>\\1</li>\n", $contents);
-*/
-
+*/
+
$contents = preg_replace("/\@/", "<i><script language=javascript>document.write(\"@\");</script><noscript>_at_</noscript></i>", $contents);
print($contents);
echo("<p>");
-$members_database = "databases/members.database";
-if (!($fp = fopen($members_database, "r"))) {
- die("could not open Authors Database");
-}
-$xml_authors = xml_parser_create();
-$authors_data = fread($fp,filesize ($members_database));
-xml_parser_set_option($xml_authors,XML_OPTION_CASE_FOLDING,0);
-xml_parse_into_struct($xml_authors,$authors_data,$vals,$index);
-
-foreach ($vals as $key) {
- $desc = $key[attributes];
- if ($key[level] >= 2) {
- if ($key[type] == 'open') {
- echo "<h3>$desc[name]</h3><ul>\n";
- }
- }
- if ($key[level] >= 3) {
- if ($key[type] == 'complete') {
- echo "<li>$desc[name] <$desc[email]> ($desc[country]): $desc[contribution]</li>\n";
- }
- }
- if ($key[level] >= 2) {
- if ($key[type] == 'close') {
- echo "</ul>\n";
- }
- }
-}
-xml_parser_free($xml_authors);
+$members_database = "databases/members.database";
+if (!($fp = fopen($members_database, "r"))) {
+ die("could not open Authors Database");
+}
+$xml_authors = xml_parser_create();
+$authors_data = fread($fp,filesize ($members_database));
+xml_parser_set_option($xml_authors,XML_OPTION_CASE_FOLDING,0);
+xml_parse_into_struct($xml_authors,$authors_data,$vals,$index);
+
+foreach ($vals as $key) {
+ $desc = $key[attributes];
+ if ($key[level] >= 2) {
+ if ($key[type] == 'open') {
+ echo "<h3>$desc[name]</h3><ul>\n";
+ }
+ }
+ if ($key[level] >= 3) {
+ if ($key[type] == 'complete') {
+ echo "<li>$desc[name] <$desc[email]> ($desc[country]): $desc[contribution]</li>\n";
+ }
+ }
+ if ($key[level] >= 2) {
+ if ($key[type] == 'close') {
+ echo "</ul>\n";
+ }
+ }
+}
+xml_parser_free($xml_authors);
-echo ("<p><b>Note: </b><i>If you have contributed something significant to Anjuta and your name is missing here, please email Naba Kumar <naba<i><script language=javascript>document.write(\"@\");</script><noscript>_at_</noscript></i>gnome.org> with your Full name, email address, country and a brief reminder of what you have done. This page is auto-generated from AUTHORS file in CVS.</i><p>");
+echo ("<p><b>Note: </b><i>If you have contributed something significant to Anjuta and your name is missing here, please email Naba Kumar <naba<i><script language=javascript>document.write(\"@\");</script><noscript>_at_</noscript></i>gnome.org> with your full name, email address, country and a brief reminder of what you have done. This page is auto-generated from the AUTHORS file in CVS.</i><p>");
?>
Modified: trunk/www/htdocs/development.php
==============================================================================
--- trunk/www/htdocs/development.php (original)
+++ trunk/www/htdocs/development.php Sat Jan 31 14:15:28 2009
@@ -1,116 +1,116 @@
-<!--
- <h3>Anjuta hourly CVS tarball update</h3>
- <p>
-
- <?php
- $filename = "cvs/index.html";
- $handle = fopen($filename, "r");
- $contents = fread($handle, filesize($filename));
- $contents = preg_replace("/\n/m", "", $contents);
- $contents = preg_replace("/^.*<ul>/i", "<ul>", $contents);
- $contents = preg_replace("/<\/ul>.*$/i", "</ul>", $contents);
- $contents .= "You can also browse the CVS online at <a href=\"http://cvs.gnome.org/viewcvs/anjuta/\";>GNOME ViewCVS interface</a>";
- print($contents);
-
- ?>
- </p>
--->
- <h3>Getting Anjuta from GNOME subversion server</h3>
- <p>
- Subversion is a powerful tool to allow many developers work on the
- same source code. This is possible because each developer checks out a copy of
- the current version of the source code. Then, each developer independently works on
- his or her own personal copy of the sources. When the developer has made
- changes, he or she commits them back to the subversion repository.
- The subversion server then takes care of things like trying
- to merge each developer's changes with those of others. When that doesn't work, the
- developer is notified, and he or she must do a hand merge of the conflicts.
- </p>
- <p>First, you need to set up the editor environmental variable, for example:
- </p>
- <div class="terminal">
- $ export EDITOR='emacs'
- </div>
-
- <p>Make sure you have all the dependencies of Anjuta installed and ready.
- Now, grab the anjuta, gnome-build and gdl modules from the repository:</p>
-
- <div class="terminal">
- $ svn checkout http://svn.gnome.org/svn/gdl/trunk gdl <br/>
- $ svn checkout http://svn.gnome.org/svn/gnome-build/trunk gnome-build <br/>
- $ svn checkout http://svn.gnome.org/svn/anjuta/trunk anjuta
- </div>
-
- <p>That only gives read access to the repository. Instead, if you have an account
- in svn.gnome.org and want write access (you must have been granted write access
- to anjuta module as an Anjuta developer), you need to checkout the source with:</p>
-
- <div class="terminal">
- $ svn checkout svn+ssh://svn.gnome.org/svn/gdl/trunk gdl <br/>
- $ svn checkout svn+ssh://svn.gnome.org/svn/gnome-build/trunk gnome-build <br/>
- $ svn checkout svn+ssh://svn.gnome.org/svn/anjuta/trunk anjuta
- </div>
-
- <p>Now, you will want to go through them to build and install. Run:</p>
-
- <div class="terminal">$ ./autogen.sh</div>
-
- <p>If you want to enabled Anjuta API docs generation, you can pass --enable-gtk-doc to
- the above autogen.sh script. Then continue just like you would work with a tarball
- package:</p>
- <div class="terminal">
- $ ./configure<br/>
- $ make<br/>
- $ su [password]<br/>
- # make install<br/>
- </div>
-
- <p>After you have checked the code out, you can use:</p>
- <div class="terminal">
- $ svn update (in the anjuta top level directory)
- </div>
- <p>to update your personal copy of anjuta to the latest version from the
- subversion repository and rebuild.
- </p>
-
- <h3>Prolog</h3>
- <p>"A service to open source is a service to mankind." </p>
- <p>
- I have spent lots of time and energy on the development of Anjuta, and
- the only thing I expect in return is your generous help in its
- further development. It took me quite some time to bring the first
- release of Anjuta to the world in 1999. For quite some time, the development of
- Anjuta was just "a one man show", but very soon it acquired
- quite a bit of attention, and now I am proud to say that Anjuta
- has a full-fledged development team! I am very thankful to all the
- people who have contributed and continue contributing to the further
- development of Anjuta as "a service to Mankind."
- <br/><br/>
- -Naba
- </p>
-
-<h3>History</h3>
- <p><b>27th Dec 1997 ...</b></p>
- <p>
- I had a date with Anjuta (my GF and not
- the program). It was really after a long time that I was going to meet
- her. We usually do not meet often because of the 'geographical distance'.
- Coincidentally, that day was also her birthday. I was
- feeling very happy and had decided to celebrate her birthday with a
- little piece of cake. Well, because my luck was not good that day, I could not
- celebrate her birthday. This made me feel as though I'd been hit by a billion
- bullets. I could not even do such a little thing for her (after all, we were
- meeting after a long time). Simply because I could not forget the incident, I
- decided to do something for her solely from my side. And I did it. Meantime,
- Gnome had been lacking a good build environment (by 'good' I mean user
- friendly). And many people, especially my friends, those who swear by M$, had
- been commenting: "Of course, Linux has become user-friendly. See, you can
- now click buttons. But the thing is, you don't feel like clicking them. " I
- just wanted them to 'feel like clicking them.'
- <br/>
- <br/>
- Then, I started the journey ...
- </br/>
- </br/>
- -Naba
- </p>
+<!--
+ <h3>Anjuta hourly CVS tarball update</h3>
+ <p>
+
+ <?php
+ $filename = "cvs/index.html";
+ $handle = fopen($filename, "r");
+ $contents = fread($handle, filesize($filename));
+ $contents = preg_replace("/\n/m", "", $contents);
+ $contents = preg_replace("/^.*<ul>/i", "<ul>", $contents);
+ $contents = preg_replace("/<\/ul>.*$/i", "</ul>", $contents);
+ $contents .= "You can also browse the CVS online at <a href=\"http://cvs.gnome.org/viewcvs/anjuta/\";>GNOME ViewCVS interface</a>";
+ print($contents);
+
+ ?>
+ </p>
+-->
+ <h3>Getting Anjuta from the GNOME Subversion server</h3>
+ <p>
+ Subversion is a powerful tool that allows many developers to work on the
+ same source code. With Subversion, each developer checks out a copy of
+ the current source code and independently works on
+ his or her own personal copy of the sources. When the developer has made
+ changes, he or she commits them back to the Subversion repository.
+ The Subversion server then takes care of things like trying
+ to merge each developer's changes with those of others. When that doesn't work, the
+ developer is notified, and he or she must do a hand merge of the conflicts.
+ </p>
+ <p>First, you need to set up the EDITOR environment variable, for example:
+ </p>
+ <div class="terminal">
+ $ export EDITOR='emacs'
+ </div>
+
+ <p>Make sure you have all dependencies of Anjuta installed and ready.
+ Now, grab the <code>anjuta</code> and <code>gdl</code> modules from the repository:</p>
+
+ <div class="terminal">
+ $ svn checkout http://svn.gnome.org/svn/gdl/trunk gdl <br/>
+ $ svn checkout http://svn.gnome.org/svn/libgda/trunk libgda <br/>
+ $ svn checkout http://svn.gnome.org/svn/anjuta/trunk anjuta
+ </div>
+
+ <p>That only gives read access to the repository. If you have an account
+ in svn.gnome.org and want write access (you must have been granted write access
+ to the <code>anjuta</code> module as an Anjuta developer), you instead need to check out the source with:</p>
+
+ <div class="terminal">
+ $ svn checkout svn+ssh://svn.gnome.org/svn/gdl/trunk gdl <br/>
+ $ svn checkout svn+ssh://svn.gnome.org/svn/libgda/trunk libgda <br/>
+ $ svn checkout svn+ssh://svn.gnome.org/svn/anjuta/trunk anjuta
+ </div>
+
+ <p>Now you will want to build and install. Run:</p>
+
+ <div class="terminal">$ ./autogen.sh</div>
+
+ <p>If you want to enable Anjuta API documentation generation, you can pass --enable-gtk-doc to
+ the above autogen.sh script. Then continue just like you would work with a tarball
+ package:</p>
+ <div class="terminal">
+ $ ./configure<br/>
+ $ make<br/>
+ $ su [password]<br/>
+ # make install<br/>
+ </div>
+
+ <p>After you have checked the code out, you can use:</p>
+ <div class="terminal">
+ $ svn update (in the anjuta top level directory)
+ </div>
+ <p>to update your personal copy of Anjuta to the latest version from the
+ Subversion repository and rebuild.
+ </p>
+
+ <h3>Prolog</h3>
+ <p>"A service to open source is a service to mankind." </p>
+ <p>
+ I have spent lots of time and energy on the development of Anjuta, and
+ the only thing I expect in return is your generous help in its
+ further development. It took me quite some time to bring the first
+ release of Anjuta to the world in 1999. For quite some time, the development of
+ Anjuta was just "a one man show", but very soon it acquired
+ quite a bit of attention, and now I am proud to say that Anjuta
+ has a full-fledged development team! I am very thankful to all the
+ people who have contributed and continue contributing to the further
+ development of Anjuta as "a service to Mankind."
+ <br/><br/>
+ -Naba
+ </p>
+
+<h3>History</h3>
+ <p><b>27th Dec 1997 ...</b></p>
+ <p>
+ I had a date with Anjuta (my GF and not
+ the program). It was really after a long time that I was going to meet
+ her. We usually do not meet often because of the 'geographical distance'.
+ Coincidentally, that day was also her birthday. I was
+ feeling very happy and had decided to celebrate her birthday with a
+ little piece of cake. Well, because my luck was not good that day, I could not
+ celebrate her birthday. This made me feel as though I'd been hit by a billion
+ bullets. I could not even do such a little thing for her (after all, we were
+ meeting after a long time). Simply because I could not forget the incident, I
+ decided to do something for her solely from my side. And I did it. Meantime,
+ Gnome had been lacking a good build environment (by 'good' I mean user
+ friendly). And many people, especially my friends, those who swear by M$, had
+ been commenting: "Of course, Linux has become user-friendly. See, you can
+ now click buttons. But the thing is, you don't feel like clicking them. " I
+ just wanted them to 'feel like clicking them.'
+ <br/>
+ <br/>
+ Then, I started the journey ...
+ </br/>
+ </br/>
+ -Naba
+ </p>
Modified: trunk/www/htdocs/features.php
==============================================================================
--- trunk/www/htdocs/features.php (original)
+++ trunk/www/htdocs/features.php Sat Jan 31 14:15:28 2009
@@ -1,134 +1,175 @@
<h1>The scoop on Anjuta DevStudio</h1>
<p>
-Anjuta DevStudio has been designed to be simple to operate yet powerful enough to fullfil all your programming needs. Many features have evolved since the early days and several very attractive ones added. Our focus is on delivering power and usability at the same time without overloading your senses and making your software development a pleasurable process. We will always be busy getting you one of the best IDE experiences by straighting up all the neat features and stablizing it. We hope you will have a good time using Anjuta. If not, please help us make it better by reporting bugs and suggestions. Here are some of the things you will find in Anjuta.
+Anjuta DevStudio has been designed to be simple to operate yet powerful enough
+to fulfill all your programming needs. We've added many new features to Anjuta
+over the course of its development. Our focus is on delivering
+power and usability at the same time and
+making your software development enjoyable without overloading your senses. We intend to
+continue improving and stabilizing Anjuta to give you the best IDE experience possible.
+We hope you will have a good time
+using Anjuta. If not, please help us make it better by reporting bugs and
+suggestions.
+</p>
+<p>
+The following screenshot illustrates some of the things you will find in Anjuta.
</p>
+
<h2>User Interface</h2>
<p>
-<a href="screenshots/anjuta-2.1/anjuta-2.1.2-1.png"><img style="border: 0; padding: 10px" src="screenshots/anjuta-2.1/anjuta-2.1.2-1-thumb.png" align="right"></a>
-Anjuta has a very flexible and advanced docking system that allows you to layout all views in whatever way you like. You can drag and drop the views using drag bars and re-arrange the layout. The layouts are persistent for each project so you can maintain different layouts required by projects. All dock views are minimizable to avoid clutter in main window. Minimized views appear as icons on left side of main window. All menu actions are configurable either by type-in-the-menu (the usual GNOME way) or by a dedicated shortcuts configuration UI.
+<a href="screenshots/anjuta-2.1.2-1.png"><img style="border: 0; padding: 10px" src="screenshots/anjuta-2.1.2-1-thumb.png" align="right"></a>
+Anjuta has a flexible and advanced docking system that allows you to
+lay out all views in whatever way you like. You can drag and drop the views
+using drag bars and rearrange the layout. The layouts are persistent for
+each project so you can maintain different layouts for different projects.
+All dock views are minimizable to avoid clutter in the main window. Minimized
+views appear as icons on the left side of the main window. You can configure all menu actions
+either by typing when the cursor is over a menu item (the usual GNOME way) or through
+a dedicated shortcut configuration user interface.
</p>
<h2>Plugins</h2>
<p>
-Anjuta is very extensible with plugins. Almost all features in Anjuta are implemented using plugins which can be dynamicaly enabled or disabled. You can select which plugins to be active for your projects and the default mode (no-project mode). Like UI layout, plugins selection are also persistent for each project making it easy to work on different levels of project complexities.
+Anjuta is very extensible with plugins. Almost all features in Anjuta are implemented using plugins which can be dynamicaly enabled or disabled. You can choose which plugins should be active for your projects and for the default mode (no-project mode). Like the user interface layout, the set of active plugins is also persistent for each project making it easy to work on projects with various levels of complexity.
</p>
<p>
-Anjuta also has a highly extensible plugin framework for those who want to extend it with their own features. Plugins can be developed and installed independent of main Anjuta development. Anjuta being written in C, the plugin framework and the API are all in C. However, c++ and python bindings are under active development. In not so distant future, it would be possible to write c++ and python plugins for Anjuta.
+Using plugins, you can extend Anjuta with your own features. As Anjuta is written in C, the plugin framework and the API are also in C. However, C++ and Python bindings are under active development. In the near future, it should be possible to write Anjuta plugins in C++ and Python.
</p>
<p>
-All plugins in Anjuta are easily substitutable with different plugins implementing the same features. This allows, for example, to have multiple editors to choose from (so far, we have scintilla and gtksourceview editors) or implement a new one (vim/emacs anyone?) suiting your taste. This applies to any plugin. If Anjuta finds that there are multiple plugins satisfying the same feature requirement, it will prompt the user to select one and remember it for rest of the time. It is posible to 'forget' this selection by clearing a gconf key (sometime soon we will have a preferences UI to make it easier).
+All plugins in Anjuta are easily replaceable with different plugins implementing similar features. This allows you, for example, to choose from multiple editors (so far, we have the Scintilla and GtkSourceView editors) or to implement a new one suiting your taste (vim/Emacs, anyone?). This applies to any plugin. If Anjuta finds that there are multiple plugins satisfying the same feature requirement, it will prompt the user to select one and will remember the selection.
</p>
<h2>File Manager</h2>
<p>
-Integrated file manager plugin behaves more or less like your typical file manager in a tree view. It lists all directories and files in current project (or a pre-configured directory if there is no project open). It is possible to not list hidden files and/or files that are ignored by version control system. A custom regexp can also be set in file manager preferences to hide additional files.
+The integrated file manager plugin behaves more or less like your typical file manager in a tree view. It lists all directories and files in the current project (or a pre-configured directory if there is no project open). You can choose not to list hidden files and/or files that are ignored by the version control system. You can also set a custom regular expression in the file manager preferences to select additional files to hide.
</p>
<p>
-Default action (double-click) on any of the files would open it, either within Anjuta if there is a plugin capable of handling it or with external application configured in your standard desktop. The file can also be opened with other applications/plugins from the context menu which lists all plugins and applications that are able to open it.
+The default action (double-clicking) on any file will open it, either within Anjuta if there is a plugin capable of handling it or with an external application configured in your standard desktop. A file can also be opened with other applications/plugins from the context menu which lists all plugins and applications that are able to open it.
</p>
<p>
-In addintion, File Manager context menu also lists actions associated with other plugins, such as build actions (associated with build system plugin), CVS/Subversion actions (associated version control system plugins) and project actions (associated with Project Manager plugin). This allows to conveniently perform all actions from within the File Manager.
+In addition, the file manager context menu also lists actions associated with other plugins, such as build actions (associated with the build system plugin), CVS/Subversion actions (associated with version control system plugins) and project actions (associated with the project manager plugin). This allows you to conveniently perform all actions from within the file manager.
</p>
<h2>Project Manager</h2>
<p>
-Anjuta has a very powerful Project Manager plugin which can open pretty much any automake/autoconf based project on the planet. It might fail on some oddly configured projects, but as long as the project is done by using automake/autoconf properly it should work.
-</p>
-<p>
-The neat thing is that it does not store any project information beyond what is already available in project struture. That is, there is no separate project data maintained by Anjuta and all project processing are done directly within the project structure. This allows the project to be maintained or developed outside Anjuta without having to, so called, 'porting' or 'switching' to a new platform. Since technically Anjuta projects are just automake projects, mixed development of it (Anjuta and non-Anjuta users) or switching back and forth between Anjuta and other tools is quite possible without any hindrance.
-</p>
-<p>
-Project Manager lists the project in standard automake heirarchy organized into groups of targets. Groups corresponds to directories in your project and targets corresponds to normal automake targets (not to be confused with make targets). Project manager view actually has two parts; one part (lower one) shows complete project heirarchy and the other part (upper one) lists important targets directly. Important targets constitute executable and library targets -- making them extremely accessible in the project view. This is particularly useful in big projects where the heirarchy could be deep and hard to navigate from the tree alone. Targets are in turn composed of source files.
+Anjuta has a powerful project manager plugin which can open pretty much any automake/autoconf based project on the planet. It might fail on some oddly configured projects, but as long as the project uses automake/autoconf in a typical way, it should work.
</p>
<p>
-Each of the project groups and targets is configurable in standard automake way. You can set complier and linker flags directly for each target, or set configure variables. Groups allow setting installation destinations for the targets.
-</p>
-<p>
-Just like file manager, project manager view also has convenience actions for the source files and targets accessible from the context menu.
+The neat thing is that Anjuta does not store any project information beyond what
+is already available in the project structure. That is, there is no separate
+project data maintained by Anjuta and all project processing is done
+directly within the project structure. This allows a project to be
+maintained or developed outside Anjuta without any need to convert to or from
+an Anjuta-specific format. Since technically Anjuta
+projects are just automake projects, mixed development (with both Anjuta and
+non-Anjuta users) or switching back and forth between Anjuta and other
+tools is quite possible without any hindrance.
+</p>
+<p>
+The project manager window displays the project's automake hierarchy organized
+into groups of targets. Groups correspond to directories in your project and targets
+correspond to normal automake targets (not to be confused with make targets).
+The project manager window actually
+has two parts: the lower part shows the complete project hierarchy and the upper part
+lists important targets directly. Important targets include executable
+and library targets; the view makes these easily accessible.
+This is particularly useful in large projects where the hierarchy
+can be deep and hard to navigate from the tree alone. Targets are, in
+turn, composed of source files.
+</p>
+<p>
+Each project group and target is configurable in the standard
+automake way. You can set compiler and linker
+flags directly for each target, or set configure variables. Groups allow
+you to set an installation destination for their targets.
+</p>
+<p>
+Just like the file manager, the project manager view also has convenience actions
+(accessible from the context menu) for source
+files and targets.
</p>
<h2>Project wizards</h2>
<p>
-The project wizard plugin uses a powerful template processing engine called <a href="http://autogen.sourceforge.net/";>autogen</a>. All new projects are created from templates that are written in autogen syntax. Project wizard lets you create new projects from a selection of project templates. The selection includes simple generic, flat (no subdirectory), gtk+, gnome, java, python projects and more. New templates can be easily downloaded and installed since they are just a collection of text files.
+The project wizard plugin uses a powerful template processing engine called <a href="http://autogen.sourceforge.net/";>autogen</a>. All new projects are created from templates that are written in autogen syntax. The project wizard lets you create new projects from a selection of project templates. The selection includes simple generic, flat (no subdirectory), GTK+, GNOME, Java, Python projects and more. New templates can be easily downloaded and installed since each template is just a collection of text files.
</p>
<h2>Source Code Editor</h2>
<p>
-There are two editors currently available in Anjuta; scintilla based (classic) editor and the new gtksourceview based editor. Except for some minor differences, both are equally good and can be used interchangably. Depending on your taste of editing, either of them can be choosen. Some of the editor features are:
+There are two editors currently available in Anjuta; the Scintilla-based (classic) editor and the new GtkSourceView-based editor. Except for some minor differences, both are equally functional and can be used interchangeably. Depending on your taste in editing, you can choose either one. Editor features include:
</p>
<ul>
- <li> Syntax highlighting: Supports syntax highlighting for almost all common programing languages. Syntax highlighting for new languages can be easily added by added proprties file, lexer parser (for scintilla editor) or lang files (for sourceview editor).</li>
-
- <li> Smart Indentation: Code automatically indentated as you type based on the language and your indentation settings. Currently only available for C and C++. For the rest, it only does basic indentation.</li>
-
- <li> Autoindentation: Indent current line or a selection of lines as per your indentation settings as if they were re-typed taking into account Smart Indentation.</li>
-
- <li> Automatic code formatting (only C and C++): Source code reformatting using 'indent' program. Full range of indent options avaiable.</li>
-
- <li> Code folding/hiding: Fold code blocks, functions, balanced texts to hide them in heirachial order. Unfold to unhide them.</li>
-
- <li> Line numbers/markers display: Left margins to show line numbers, markers and folding points.</li>
-
- <li> Text zooming: Zoom texts using scrollwheel or menu.</li>
-
- <li> Code autocompletion: Automatic code completion for known symbols. Type ahead suggestions to choose for completion.</li>
-
- <li> Calltips for function prototypes: Provides helpful tips for typing function calls with their prototype and arguments hint.</li>
-
- <li> Indentation guides: Guides to make it easier to see indentation levels.</li>
-
- <li> Bookmarks: Set or unset bookmarks and navigation.</li>
-
- <li> Multiple split views: Multiple views for the same file (split inside the same editor). Useful when typing in a file while referencing the same file at another location or copy-pasting within the same file to/from different locations without having to scroll back and forth.</li>
-
- <li> Incremental Search: Search as you type in the search field for instant search. Useful when you want to avoid typing the full search when the first few characters are enough to reach the point.</li>
-
- <li> Powerful search and replace: Supports string and regexp search expressions, search in files, search in project etc.</li>
-
- <li> Jump to line number: Instant jump to line number.</li>
-
- <li> Build messages highlight: Error/warning/information messages are indicated in the editor with helpful (and appropriately colored) underlines. Very useful when you are strolling throught the file correcting all build errors without having to use build outputs to navigate indivitual errors.</li>
-
- <li> Tabs reordering: Reorder editor tabs as per your convenience.</li>
-
- <li> Notifications for files modified outside Anjuta while they are open.</li>
+ <li> Syntax highlighting: The editor supports syntax highlighting for almost all common programing languages. Syntax highlighting for new languages can be easily added by adding a properties file, a lexer parser (for the Scintilla editor) or lang files (for the GtkSourceView editor).</li>
+
+ <li> Smart Indentation: Code is automatically indented as you type based on the language and your indentation settings. (Smart indentation is currently only available for C and C++; for other languages, Anjuta performs only basic indentation.)</li>
+
+ <li> Autoindentation: The editor can indent the current line or a selection of lines according to your indentation settings.</li>
+
+ <li> Automatic code formatting (only C and C++): The editor can reformat source code using the <code>indent</code> program. The full range of <code>indent</code> options is available.</li>
+
+ <li> Code folding/hiding: You can fold code blocks and functions to hide them hierarchically, and can unfold them to unhide them.</li>
+
+ <li> Line numbers/markers display: The editor has left margins which display line numbers, markers and fold points.</li>
+
+ <li> Text zooming: You can zoom (change the editor font size) using either the scroll wheel or menu commands.</li>
+
+ <li> Code autocompletion: The editor can autocomplete known symbols, and provides type-ahead suggestions to choose for completion.</li>
+
+ <li> Calltips for function prototypes: When you are typing a function call, the editor provides a helpful tip showing the parameters from the function's prototype.</li>
+
+ <li> Indentation guides: The editor has guides to make it easier to see indentation levels.</li>
+
+ <li> Bookmarks: You can set or unset bookmarks for convieniently navigating to frequent destinations in your source code.</li>
+
+ <li> Multiple split views: The editor provides multiple views for the same file (split inside the same editor). This allows you to enter text in a file while referring to the same file at another location, or to copy/paste within the same file at different locations without having to scroll back and forth.</li>
+
+ <li> Incremental Search: The editor can search instantly as you type a search string in the search box. This is useful when you want to avoid typing a full search string when the first few characters are enough to reach the desired location.</li>
+
+ <li> Powerful search and replace: The editor supports searching for strings and regular expressions, searching in files or searching all files in your project.</li>
+
+ <li> Jump to line number: You can instantly jump to any line number in a source file.</li>
+
+ <li> Build message highlighting: Error/warning/information messages are indicated in the editor with helpful (and appropriately colored) underlines. This lets you navigate through a source file correcting all build errors without having to use the build output to jump to errors individually.</li>
+
+ <li> Tabs reordering: You can reorder editor tabs as you like.</li>
+
+ <li> Change notifications: Anjuta notifies you when a file is modified outside Anjuta while it is open in Anjuta.</li>
</ul>
<h2>Symbols view and navigation</h2>
<p>
-The symbol browser plugin shows all symbols in your project organized into their types. There are tree views in symbol browser plugin; one showing the global symbol tree, another showing symbols in current file and the third one providing a view to search the symbols. All the symbols can be navigated to their respective definitions and declarations. Symbols in current file can also be navigated quickly from toolbar.
+The symbol browser plugin shows all symbols in your project organized by type. There are three views in the symbol browser: one showing the global symbol tree, another showing symbols in the current file and a third view for searching symbols. You can navigate to any symbol's definition or declaration.
</p>
<p>
-When anjuta is started for first time, it also indexes symbols from all installed libraries for autocompletion and calltips. This provides instant reference to library functions used in the project. The libraries that should be referenced can be selected from symbol browser preferences.
+When Anjuta is started for the first time, it also indexes symbols from all installed libraries for autocompletion and calltips. This provides an instant reference to library functions used in the project. The libraries that should be referenced can be selected from the symbol browser preferences.
</p>
<h2>Integrated Debugger</h2>
<p>
-Anjuta provides a full source level debugger (currently backed by gdb, but will have other debugger backends soon). The debugger provides everything that can be expected from a typical source debugger such as breakpoints, watches, source navigations, stack trace, threads, disassembly view, registers, local variables, memory dumps etc. You can also set up breakpoints and watches without first having the debugger running. They are saved in session so the next debugging session would still have them.
+Anjuta provides a full source-level debugger (currently backed by gdb, but there will be other debugger backends soon). The debugger provides everything that can be expected from a typical source debugger including breakpoints, watches, source navigation, stack traces, threads, a disassembly view, registers, local variables, and memory dumps. You can also set up breakpoints and watches without first having the debugger running. They are saved in your session so that the next debugging session will still have them.
</p>
<p>
-Program execution under the debugger can be performed in single step, step over, step out, continued execution, run to cursor, pause program or attach to process etc. All programs in the project can be started in termial and can be provided arguments. Programs linking shared libraries within the project are also started correctly using libtool to ensure non-installed libraries are picked up rather than installed ones.
+You can control program execution under the debugger in various ways: you can single step, step over, step out, continue execution, run to the cursor, pause the program, or attach to a running process. All programs in a project can be started in a terminal window and can be provided arguments. When a program links shared libraries within a project, the debugger starts the program correctly using libtool to ensure that non-installed libraries are picked up rather than installed ones.
</p>
-<h2>Integrated glade user interface designer</h2>
+<h2>Integrated Glade user interface designer</h2>
<p>
-<a href="screenshots/anjuta-2.1/anjuta-2.1.2-9.png"><img style="border: 0; padding: 10px" src="screenshots/anjuta-2.1/anjuta-2.1.2-9-thumb.png" align="right"></a>
-<a href="http://glade.gnome.org/";>Glade</a> is the GTK+/GNOME wysiwyg graphical user interface designer which lets you create UIs (dialogs and windows) for your application visualy. Glade files can be directly edited within Anjuta. When a glade file is opened or created, glade plugin is started and brings up the designer view, palettes, properties editor and widgets view. The project can have any number of glade files and can be conveniently opened simultaneous (however, only one can be edited at a time).
+<a href="screenshots/anjuta-2.1.2-9.png"><img style="border: 0; padding: 10px" src="screenshots/anjuta-2.1.2-9-thumb.png" align="right"></a>
+<a href="http://glade.gnome.org/";>Glade</a> is the GTK+/GNOME WYSIWYG graphical user interface designer which lets you create user interfaces (dialogs and windows) for your application visualy. Glade files can be directly edited within Anjuta. When a Glade file is opened or created, the Glade plugin is started and brings up the designer view, palettes, properties editor and widgets view. The project can have any number of Glade files and, conveniently, more than one can be opened simultaneously (however, only one can be edited at a time).
</p>
<h2>Class generator and file wizard</h2>
<p>
-With class generator plugin, you can create c++ and GObject classes easily and add them to your projects. Similarly, file wizard can create templates for your new source files.
+With the class generator plugin, you can create C++ and GObject classes easily and add them to your projects. Similarly, the file wizard can create templates for new source files.
</p>
-<h2>Valgrind plugin and gprof profiler plugin</h2>
+<h2>Valgrind plugin and gprof profiler plugins</h2>
<p>
-Integrated valgrind plugin can be used to profile programs for memory leaks and corruptions.
+The integrated valgrind plugin can be used to profile programs for memory leaks and corruptions.
</p>
-<h2>Integrated devhelp API help browser</h2>
+<h2>Integrated Devhelp API help browser</h2>
<p>
-<a href="screenshots/anjuta-2.1/anjuta-2.1.2-8.png"><img style="border: 0; padding: 10px" src="screenshots/anjuta-2.1/anjuta-2.1.2-8-thumb.png" align="right"></a>
-<a href="http://developer.imendio.com/projects/devhelp";>Devhelp</a> is the GTK+/GNOME developer's help browser. It is very conveniently integrated into Anjuta to give instant API help. Press Shift+F1 and you get the API documentation of the current symbol in editor. Make sure you have enabled Devhelp plugin for the project to use it. You can browse all the installed help documents from the tree view or search for symbols in the search view.
+<a href="screenshots/anjuta-2.1.2-8.png"><img style="border: 0; padding: 10px" src="screenshots/anjuta-2.1.2-8-thumb.png" align="right"></a>
+<a href="http://developer.imendio.com/projects/devhelp";>Devhelp</a> is the GTK+/GNOME developer's help browser. It is conveniently integrated into Anjuta to give instant API help. Press Shift+F1 to jump to the API documentation of the symbol at the editor cursor. Make sure you have enabled the Devhelp plugin for the project. In Devhelp, you can browse all installed help documents from the tree view and can search for symbols in the search view.
</p>
<!--
* Bookmarks: Navigate through all the bookmarks in the file.
Modified: trunk/www/htdocs/home.php
==============================================================================
--- trunk/www/htdocs/home.php (original)
+++ trunk/www/htdocs/home.php Sat Jan 31 14:15:28 2009
@@ -1,56 +1,57 @@
- <p>
- <?php
- require("anjuta_news.html");
- ?>
- </p>
- <p>
- Members submit news <a href="http://sourceforge.net/news/submit.php?group_id=14222";
- >here</a>. News Sync takes place every hour, so submitted news
- may not be available immediately here.
- </p>
-
- <h3>Introduction</h3>
- <p>
- Anjuta is a versatile Integrated Development Environment (IDE)
- for C and C++ on GNU/Linux. It has been written for GTK/GNOME
- and features a number of advanced programming facilities.
- These include project management, application wizards, an
- on-board interactive debugger, and a powerful source editor
- with source browsing and syntax highlighting.
- </p><p>
- Anjuta is an effort to marry the flexibility and power of text-based
- command-line tools with the ease-of-use of the GNOME graphical user
- interface. That is why it has been made as user-friendly as possible.
- </p><p>
- Any sort of suggestions or patches for Anjuta are also most welcome.
- </p><p>
- Remember, this program is under the license of the GPL.<br>
- Please read the file COPYING that comes with the distribution for details.
- </p>
-<!--
- <h3>Copyright (C) <a href="http://naba.co.in/";>Naba Kumar</a></h3>
- <p>
- This program is free software; you can redistribute it and/or modify it under the terms of
- the GNU General Public License as published by the Free Software Foundation, either
- version 2 of the License, or (at your discretion) any later version.
- </p>
- <p>
- This program is distributed in the hope that it will be useful, but WITHOUT ANY
- WARRANTY, without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
- PARTICULAR PURPOSE. See the GNU General Public License for more details.
- <p></p>
- You should have received a copy of the GNU General Public License along with this program;
- if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330,
- Boston, MA 02111-1307 USA
- </p>
--->
- <h3>Help wanted!</h3>
- <p>
- <ul>
- <li>Software Developers [New Code, Fixes, etc...]
- <li>Editors [Manuals, Articles]
- <li>Artists [Icons, images, splash]
- </ul>
- Please go to the mailing list section to join or subscribe to the
- development mailing list to start contributing.
- </p>
+ <p>
+ <?php
+ require("anjuta_news.html");
+ ?>
+ </p>
+ <p>
+ Members submit news <a href="http://sourceforge.net/news/submit.php?group_id=14222";
+ >here</a>. News is synchronized every hour, so submitted news
+ may not be available immediately on this page.
+ </p>
+
+ <h3>Introduction</h3>
+ <p>
+ Anjuta is a versatile Integrated Development Environment (IDE)
+ for C and C++ on GNU/Linux. It has been written for GTK/GNOME
+ and features a number of advanced programming facilities
+ including project management, application wizards, an
+ interactive debugger and a powerful source editor
+ with source browsing and syntax highlighting.
+ </p><p>
+ Anjuta is an effort to marry the flexibility and power of text-based
+ command-line tools with the ease of use of the GNOME graphical user
+ interface. That is why it has been made as user-friendly as possible.
+ </p><p>
+ Any sort of suggestions or patches for Anjuta are most welcome.
+ </p><p>
+ Anjuta is licensed under the GNU GPL.
+ Please read the file COPYING that comes with the distribution for details.
+ </p>
+<!--
+ <h3>Copyright (C) <a href="http://naba.co.in/";>Naba Kumar</a></h3>
+ <p>
+ This program is free software; you can redistribute it and/or modify it under the terms of
+ the GNU General Public License as published by the Free Software Foundation, either
+ version 2 of the License, or (at your discretion) any later version.
+ </p>
+ <p>
+ This program is distributed in the hope that it will be useful, but WITHOUT ANY
+ WARRANTY, without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+ PARTICULAR PURPOSE. See the GNU General Public License for more details.
+ <p></p>
+ You should have received a copy of the GNU General Public License along with this program;
+ if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330,
+ Boston, MA 02111-1307 USA
+ </p>
+-->
+ <h3>Help wanted!</h3>
+ <p>
+ We welcome help from
+ <ul>
+ <li>software developers (new code, bug fixes)
+ <li>editors (manuals, articles)
+ <li>artists (icons, images, splash screens)
+ </ul>
+ Please go to the mailing list section to join or subscribe to the
+ development mailing list to start contributing.
+ </p>
Modified: trunk/www/htdocs/tasks.php
==============================================================================
--- trunk/www/htdocs/tasks.php (original)
+++ trunk/www/htdocs/tasks.php Sat Jan 31 14:15:28 2009
@@ -222,17 +222,17 @@
?>
<p>
-These are the tasks that have been defined and being undertaken. Many of the tasks have bounties assined to prioritize their development and to encourage more contribution to critical tasks in Anjuta. Anyone interested can pick up any tasks and contribute to Anjuta. It is advisable to announce and discuss it first in anjuta-devel mailing list before undertaking any of the tasks to ensure that no duplicate work is being done. It also ensures the tasks are marked 'Assigned' so that other people know who are working on them (and possibly to collaborate the work).
+These are Anjuta development tasks that have been defined and are being undertaken. Many tasks have bounties assigned to prioritize their development and to encourage more contribution to critical tasks in Anjuta. Anyone interested can pick up any tasks and contribute to Anjuta. Before undertaking any task, it is advisable to announce and discuss it first on the anjuta-devel mailing list to ensure that no duplicate work is being done. This also ensures that tasks in progress are marked 'Assigned' so that other people know who are working on them (and can possibly collaborate on the work).
</p>
<p>
-For a task to be assigned, it is mandatory to <a href='http://bugzilla.gnome.org/enter_bug.cgi?product=anjuta'>create a bugzilla entry</a> for tracking its development. Put the task title as bugzilla summary and task description as the bugzilla summary. If the task has a bounty, please also suffix the bugzilla summary with 'Bounty: '.
+In order for a task to be marked as assigned, you must <a href='http://bugzilla.gnome.org/enter_bug.cgi?product=anjuta'>create a Bugzilla entry</a> for tracking its development. Enter the task title as the Bugzilla summary and the task description as the Bugzilla description. If the task has a bounty, please also suffix the Bugzilla summary with 'Bounty: '.
</p>
<p>
-Tasks with bounties are little different than other general tasks. For them to be marked 'Assigned' we need to first make sure the contributor is indeed suitable for the task. If you are new to Anjuta developemnt, it is therefore suggested to convince the lead developer in the mailing list discussion that you can perform the task. The contribution/patch is subject to code reviews and quality checks. Means there will be constant feedbacks and suggestions until the code is acceptatble.
+Tasks with bounties are little different than other general tasks. Before these can be marked Assigned we need to first make sure that the contributor is indeed suitable for the task. If you are new to Anjuta development, we suggest that you convince the lead developer in the mailing list discussion that you can perform the task. Your contribution or patch is subject to code reviews and quality checks. This means that you will receive feedback and suggestions until the code is acceptable.
</p>
<?php
echo "<h1>Pending Tasks</h1>\n";
-echo "Click on task titles for full descriptions and on bugzilla ids for development updates.<br>";
+echo "Click on task titles for full descriptions and on Bugzilla ids for development updates.<br>";
echo "<table cellspacing=0 cellpadding=5 border=1 width='100%'>";
echo "<tr><th>Category</th><th>Summary</th><th>Bounty</th><th>Status</th><th>Bugzilla</th>";
echo $index_html;
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
