[Argil-svn] SF.net SVN: argil: [494] trunk/docs

[<tsw...@us...>]

Revision: 494
          http://argil.svn.sourceforge.net/argil/?rev=494&view=rev
Author:   tswicegood
Date:     2007-02-20 17:06:13 -0800 (Tue, 20 Feb 2007)

Log Message:
-----------
Update all of the docs to be reflect the name change

Modified Paths:
--------------
    trunk/docs/CodingStandard
    trunk/docs/HowTos/BookmarkApp
    trunk/docs/HowTos/HelloWorld
    trunk/docs/Manifesto
    trunk/docs/OneMinuteTutorial

Added Paths:
-----------
    trunk/docs/ArgilAjaxApi
    trunk/docs/InstallingArgil

Removed Paths:
-------------
    trunk/docs/InstallingPipes
    trunk/docs/PipesAjaxApi

Copied: trunk/docs/ArgilAjaxApi (from rev 477, trunk/docs/PipesAjaxApi)
===================================================================
--- trunk/docs/ArgilAjaxApi	                        (rev 0)
+++ trunk/docs/ArgilAjaxApi	2007-02-21 01:06:13 UTC (rev 494)
@@ -0,0 +1,5 @@
+Argil Javascript/AJAX API
+=========================
+As I move past version 0.1 and toward 0.2, this page will contain an outline
+of the Javascript API.
+

Modified: trunk/docs/CodingStandard
===================================================================
--- trunk/docs/CodingStandard	2007-02-20 23:57:43 UTC (rev 493)
+++ trunk/docs/CodingStandard	2007-02-21 01:06:13 UTC (rev 494)
@@ -1,13 +1,13 @@
-Pipes Coding Standard
+Argil Coding Standard
 =====================
-Pipes does not adhere to the *Coding Standard* set forth by PEAR.  That
-is actually a [formatting standard][1], which Pipes does have.  Our coding
+Argil does not adhere to the *Coding Standard* set forth by PEAR.  That
+is actually a [formatting standard][1], which Argil does have.  Our coding
 standard actually focuses on standard level of code:
 
 
 Interface usage
 :	There should be no [concrete class dependencies][2].  Type hinting is
-	strongly encouraged throughout, however it should hit to an interface,
+	strongly encouraged throughout, however it should hint to an interface,
 	not directly to a class.
 
 Method length

Modified: trunk/docs/HowTos/BookmarkApp
===================================================================
--- trunk/docs/HowTos/BookmarkApp	2007-02-20 23:57:43 UTC (rev 493)
+++ trunk/docs/HowTos/BookmarkApp	2007-02-21 01:06:13 UTC (rev 494)
@@ -1,16 +1,16 @@
 How to build a simple bookmark application
 ==========================================
-Pipes is a rapid application development framework that provides the tools
+Argil is a rapid application development framework that provides the tools
 necessary to quickly, and efficiently create database powered applicaitons.
 
 
 Getting Started
 ---------------
-Make sure you have [installed](../InstallingPipes) Pipes.  If this is your 
+Make sure you have [installed](../InstallingArgil) Argil.  If this is your 
 first application, you will need to start off by creating a *project* for it
 to reside in.  To do that, you will need to run the following command:
 
-    $ pipes start MyProject
+    $ argil start MyProject
 
 
 ### What is a project? ###
@@ -22,7 +22,7 @@
 
 A look at what was created
 --------------------------
-The `pipes` program just created a skeleton project directory and config
+The `argil` program just created a skeleton project directory and config
 file.  To view the files it just created, look in the new `./MyProject' 
 directory.  You should see something like this:
 
@@ -45,14 +45,14 @@
 
 Setting up the configuration
 ----------------------------
-Pipes has adopted *convention over configuration*, so you won't spend much time
+Argil has adopted *convention over configuration*, so you won't spend much time
 editing `MyProject/config.php`, but to start with, you'll want to make sure
 your PDO connection is properly set up.  Line 10 of the config file will look
 like:
 
-    $config['pdo'] = new PDO('mysql:host=localhost;dbname=pipes_demo', 'root', '');
+    $config['pdo'] = new PDO('mysql:host=localhost;dbname=argil_demo', 'root', '');
 
-The `pipes_demo` database was assumed based on the project you created.  This 
+The `argil_demo` database was assumed based on the project you created.  This 
 also attempts to connect to the `localhost` using the `root` account with no
 password as that is the default setup for MySQL.  It is not a secure means of
 connecting to the database, so it is *strongly* suggested that you change this
@@ -76,11 +76,11 @@
 
 There are three *conventions* to note here:
 
-1.  The name of the table is a simple plural.  Pipes assumes all databases will
+1.  The name of the table is a simple plural.  Argil assumes all databases will
     be named in a simple plural form - just add *s* to the end of the name.
 2.  The primary ID field is the non-plural name of the table with a "_id"
     suffix.
-3.  Pipes does not use a built-in sequence, such as MySQL's `auto_increment`.
+3.  Argil does not use a built-in sequence, such as MySQL's `auto_increment`.
     Instead, it will create and use a universal `sequences` table to track
     the universal unique ID.
 
@@ -88,10 +88,10 @@
 Creating the MVC scaffolding
 ----------------------------
 Once the data storage has been defined in the database, you need to run the
-`pipes` script again to create the MVC scaffolding.  To do so, switch into
+`argil` script again to create the MVC scaffolding.  To do so, switch into
 the `MyProject` directory you created earlier and run
 
-    $ pipes create Bookmark --with=Tag
+    $ argil create Bookmark --with=Tag
 
 This will create the files necessary for a basic CRUD application.  Here are
 the files it created:
@@ -113,12 +113,12 @@
 
 
 You can explore these files on your own.  You'll notice that there is not
-much in any of them.  Pipes uses *metaprogramming*, or more correctly, a subset
-termed *[CategoryReflection][note-1]*.  This basically means that the Pipes is
+much in any of them.  Argil uses *metaprogramming*, or more correctly, a subset
+termed *[CategoryReflection][note-1]*.  This basically means that the Argil is
 capable of looking at where the code exists, what its name is, and figuring out
 what to do from there.
 
-> Future versions of Pipes will also be capable of [Code Generation][note-2] to 
+> Future versions of Argil will also be capable of [Code Generation][note-2] to 
 > allow for greater flexibility.  While meta-programming allows for quick 
 > prototyping, it does create a [tight coupling][note-3] which makes the 
 > code less portable.
@@ -128,7 +128,7 @@
 -------------------------
 Your application is now ready to load.
 
-    http://localhost/pipes/index.php/Bookmark/
+    http://localhost/argil/index.php/Bookmark/
 
 That will bring up a page that has 'title', 'url', and 'description', and a
 link to add a new bookmark.  Click the *Add New* link to be taken to a form to
@@ -140,7 +140,7 @@
 
 Creating the interface for Tags
 -------------------------------
-One thing your app can't do yet is handle Tags.  Though Pipes realizes there is
+One thing your app can't do yet is handle Tags.  Though Argil realizes there is
 a connection there, it doesn't know immediately how to display those related
 items.  Since all of the required code is in place, all we have to do is edit
 the view files to make it display properly.
@@ -165,7 +165,7 @@
 To:
 
     <?php $form = $this->form($this->model); ?>
-    <div pipes:for="tags">
+    <div argil:for="tags">
         <label for="form__bookmark__tags">Tags</label>
         <input id="form__bookmark__tags" \
             type="text" 
@@ -182,12 +182,12 @@
 
     <?php $form = $this->form($this->model); ?>
 
-The `form()` call above calls the PipesCore_Helpers_Form object to work
+The `form()` call above calls the ArgilCore_Helpers_Form object to work
 as a Helper.  Helpers can be in any project and are accessed in Views by
 calling `$this->helperName()`.  All this line does is start the generating
 of a Form object.
 
-    <div pipes:for="tags">
+    <div argil:for="tags">
 
 This line uses an XML Namespace to signify that this should be used by the
 Form object to be displayed whenever a `tags` element is encountered while
@@ -198,7 +198,7 @@
             type="text" 
             name="bookmark[tags]" ...
  
-All form elements in Pipes contain IDs that are mapped out as 
+All form elements in Argil contain IDs that are mapped out as 
 `form__<model_name>__<column_name>`.  All form elements that are to be 
 submitted should also have a name in the format of `<model_name>[<column_name>]`
 
@@ -212,7 +212,7 @@
             ?>" />
 
 The `value` of the `input` tag uses a new foreach().  By calling the `tags`
-attribute on the Model, we're asking Pipes to find any related objects.  The
+attribute on the Model, we're asking Argil to find any related objects.  The
 text of a tag's name is in it's `name` attribute, so we're just creating a list
 of space-separated tags as the value.
 
@@ -246,7 +246,7 @@
 
 Of course, you can make those labels anything you would like.  Another thing
 you might have noticed is that the `url` input box is a `textarea`.  This is
-because Pipes sees the `BLOB` data type and thinks it should display something
+because Argil sees the `BLOB` data type and thinks it should display something
 to accomodate it.  Since we want it to act like a normal string, just one with
 a lot of storage, we can set another override in the Meta file and it will
 automatically display as a text input.  Change 'url' to look like:
@@ -263,7 +263,7 @@
 ------------------------------
 Now that you can add Tags to Bookmark entries, you'll want to be able to see
 them on the browse page.  To do this, you'll need to edit the 
-`MyProject/PipesDemo/Views/Bookmark/browse.php` file and tell it how to display
+`MyProject/ArgilDemo/Views/Bookmark/browse.php` file and tell it how to display
 the Tags.  In this case, change:
 
     foreach ($this->modelList as $model) {
@@ -274,7 +274,7 @@
 
     foreach ($this->modelList as $model) {
     ?>
-        <td pipes:for="tags">
+        <td argil:for="tags">
             <?php 
             foreach ($model->tags as $tag) {
                 echo $tag->name . ' ';
@@ -286,7 +286,7 @@
     <?php
     }
 
-Again, we're using `pipes:for` to specify that when we get to the `tags` 
+Again, we're using `argil:for` to specify that when we get to the `tags` 
 element, we already have it determined how we want it to display.  This uses
 the same `foreach` that is used in the `edit.php` template to display the tag
 name as a space-separated list.  Save the file, and refresh your browse and now
@@ -296,10 +296,10 @@
 Making URLs links
 -----------------
 One last change to make is to make the URL fields on the browse page links.  As
-you might guess, it's just a matter of adding a new `pipes:for` field.  In this
-case, before `<td pipes:for="tags">`, add in the following:
+you might guess, it's just a matter of adding a new `argil:for` field.  In this
+case, before `<td argil:for="tags">`, add in the following:
 
-    <td pipes:for="url">
+    <td argil:for="url">
         <a href="<?php echo $model->url; ?>"><?php echo $model->url; ?></a>
     </td>
  
@@ -310,13 +310,13 @@
 
 Conclusion and Final Notes
 --------------------------
-This tutorial covers basic use of Pipes.  It shows you how to create a new 
+This tutorial covers basic use of Argil.  It shows you how to create a new 
 project, make sure it's configured, and how to edit the view files to create
 some custom displays on the edit and browse pages.
 
 There are a few things missing:
 
-1.  First, the tags aren't clickable.  As of this release, Pipes does not have
+1.  First, the tags aren't clickable.  As of this release, Argil does not have
     a tag action in the Controller to handle displaying elements by tags.  This
     functionality will be in future releases.
 2.  There is now user authentication built-in.  This is planned for version 0.2.

Modified: trunk/docs/HowTos/HelloWorld
===================================================================
--- trunk/docs/HowTos/HelloWorld	2007-02-20 23:57:43 UTC (rev 493)
+++ trunk/docs/HowTos/HelloWorld	2007-02-21 01:06:13 UTC (rev 494)
@@ -1,25 +1,25 @@
 How to build a simple Hello World application
 =============================================
-Although Pipes is designed to be used in a database driven environment with 
+Although Argil is designed to be used in a database driven environment with 
 dynamic content, it works equally well to serve up static content.  This
 quick tutorial will walk you through the process of creating a controller
 to return static contents and introduce you to the Controller and View in
-Pipes.
+Argil.
 
 
 Hello World in Sixty Seconds
 ----------------------------
-*Step One* [Install](../InstallingPipes) Pipes
+*Step One* [Install](../InstallingArgil) Argil
 
-*Step Two* Create a project by running `pipes start MyProject`
+*Step Two* Create a project by running `argil start MyProject`
 
 *Step Three*  Create the `MyProject/Controllers/HelloWorldController.php` file
 
     <?php    
-    require_once 'Pipes/Controller.php';
+    require_once 'Argil/Controller.php';
 
     class MyProject_Controllers_HelloWorldController 
-        extends Pipes_Controller 
+        extends Argil_Controller 
     {
 
     }
@@ -33,19 +33,19 @@
 *Step Six* Read on to understand what you just did...
 
 
-What is Pipes?
+What is Argil?
 --------------
-In buzzwords, Pipes is a rapid application development framework utilizing
+In buzzwords, Argil is a rapid application development framework utilizing
 the MVC design pattern.  In laymen's terms, it's a quick way to get from
 idea in your head to working idea in code.
 
 
 First Step
 ----------
-The step is to create a project.  To do this, you will execute the 'pipes'
+The step is to create a project.  To do this, you will execute the 'argil'
 program from the command line to start your project:
 
-    $ /path/to/pipes start MyProject --disable-database
+    $ /path/to/argil start MyProject --disable-database
 
 
 ### What is a project? ###
@@ -56,9 +56,9 @@
 
 
 ### Configuration - not so much ###
-The `pipes start ...` command above created a directory called `./MyProject`.
+The `argil start ...` command above created a directory called `./MyProject`.
 That directory contains the normal sub-directories and files required for
-Pipes to run.  While Pipes uses convention over configuration for the majority
+Argil to run.  While Argil uses convention over configuration for the majority
 of the heavily lifting, it does need a few things defined so it can run.  If 
 you opening the 'MyProject/config.php' file, you will see a file that looks 
 roughly like:
@@ -67,7 +67,7 @@
     
 	$config = array(
 	    'projects' => array(
-	        'PipesCore',
+	        'ArgilCore',
 	        'MyProject'
 	    )
 	);
@@ -77,12 +77,12 @@
 
 The `$config` variable is what will be returned at the end of the config file.
 The item of interest in it right now is the array `projects`.  You'll note that
-it currently contains two values, `PipesCore` and `MyProject`.  The latter 
-you'll recognize as project name you gave `pipes` earlier.  The `PipesCore` 
-line is included to give you access to core pieces of Pipes, such as tagging,
+it currently contains two values, `ArgilCore` and `MyProject`.  The latter 
+you'll recognize as project name you gave `argil` earlier.  The `ArgilCore` 
+line is included to give you access to core pieces of Argil, such as tagging,
 while allowing you to easily override them by providing your own.
 
-Several parts of Pipes, including all Model related objects, Views, and Helpers
+Several parts of Argil, including all Model related objects, Views, and Helpers
 (Controllers are upcoming) are loaded via file loaders that use the `projects`
 to determine the prefix of the class you are loaded.  They are checked in 
 reverse order.
@@ -90,14 +90,14 @@
 
 ### MyProject/Public ###
 The other file worth noting is `MyProject/Public`.  This contains a sample
-bootstrap file to get Pipes running.  Generally, you will want to make a 
+bootstrap file to get Argil running.  Generally, you will want to make a 
 symlink of this directory to some publicly accessible directory inside your 
 document root.
 
 
 Creating the Controller
 -----------------------
-An intregal, and required, part of Pipes is the Controller.  Though the 
+An intregal, and required, part of Argil is the Controller.  Though the 
 Controller is required in order for any application to work, its use is 
 straight forward and simple.  You need to create a new file in the 
 `MyProject/Controllers` directory called `HelloWorldController.php`. The
@@ -105,22 +105,22 @@
 
     <?php
 
-    require_once 'Pipes/Controller.php';
+    require_once 'Argil/Controller.php';
 
-    class MyProject_Controllers_HelloWorldController
+    class MyProject_Controllers_HelloWorldController extends Argil_Controller
     {
 
     }
 
 ### PEAR Class Naming Convention ###
 If you're familiar with PEAR, you'll notice that this file uses the PEAR
-class naming convention.  This is true of all files in Pipes, every *_* is
+class naming convention.  This is true of all files in Argil, every *_* is
 equivalent to another directory level in the filesystem.
 
 
 Creating the View
 -----------------
-That's it for the Controller - really.  In it's current form, Pipes favors
+That's it for the Controller - really.  In it's current form, Argil favors
 meta-programming, meaning that by extending an abstract super-class, it can
 figure out what to do from there.  Now, on to the view.
 
@@ -135,13 +135,13 @@
     <h1>Hello World!</h1>
 
 Assuming you have a copy or symlink of `MyProject/Public/index.php` accessible
-at `http://localhost/pipes/`, load the URL to see your handy work:
+at `http://localhost/argil/`, load the URL to see your handy work:
     
-    http://localhost/pipes/index.php/HelloWorld
+    http://localhost/argil/index.php/HelloWorld
 
 
 ### No Actions?! ###
-Pipes does not require actions when all that is being done rendering static
+Argil does not require actions when all that is being done rendering static
 content.  This removes one extra step for static pages.  In dynamic settings,
 however, actions are extremely useful by allowing you to assign variables,
 loading additional information, etc., that are to be used by the View.  For
@@ -168,22 +168,22 @@
 Conclusion
 ----------
 This introduces you to the concept of projects, Controllers, and Views within
-Pipes.  This just scratches the surface of what Pipes is and will be capable
+Argil.  This just scratches the surface of what Argil is and will be capable
 of by demonstrating how to create a simple HelloWorld application by hand.
-Using the other parameter in the `pipes` program, `create`, these files would
+Using the other parameter in the `argil` program, `create`, these files would
 be created for you, but only if you are using a database.
 
 
 Final Note on Development
 -------------------------
-It should be noted that as of the writing of this how-to, Pipes is at its
+It should be noted that as of the writing of this how-to, Argil is at its
 very early stages of development.  While it does have a lot of features
 included in this first release, it is probably not ready for a production
 environment unless you are ready to keep up with a rapid pace of development.
 While every reasonable effort has been made to make wise choices up front
-in regards to the internal API of Pipes, it is entirely possible that it will 
+in regards to the internal API of Argil, it is entirely possible that it will 
 change slightly until a release is reached.  The first intended stable release
 and API freeze is planned for version 0.5 (see misc/Roadmap.txt).
 
-If you're interested in keeping up with Pipes development, be sure to join
-the [pipes-talk Google Group](http://groups-beta.google.com/group/pipes-talk/).
+If you're interested in keeping up with Argil development, be sure to join
+the [argil-talk mailing list](https://lists.sourceforge.net/lists/listinfo/argil-talk).

Copied: trunk/docs/InstallingArgil (from rev 477, trunk/docs/InstallingPipes)
===================================================================
--- trunk/docs/InstallingArgil	                        (rev 0)
+++ trunk/docs/InstallingArgil	2007-02-21 01:06:13 UTC (rev 494)
@@ -0,0 +1,33 @@
+Installing Argil
+================
+Argil can currently be manually installed or installed via Subversion.
+
+
+Manually installing Argil
+-------------------------
+* Downloaded the latest release tarball (see http://phpinargil.org for latest)
+* Uncompress tarball into readable directory
+* Continue to *Steps for Manual and SVN installations*
+
+
+Installing Argil from Subversion
+--------------------------------
+* Checkout the latest tag from the SVN repo (i.e. http://phpinargil.googlecode.com/svn/tags/0.1)
+  (See notes on release numbers for more information about what release numbers mean)
+* Continue to *Steps for Manual and SVN installations*
+
+
+Steps for Manual and SVN installations
+--------------------------------------
+* Create sym-link of `scripts/argil` into an executable path (see *Copying 
+  `argil`* if you plan on making a copy of the `argil` script)
+* Run `argil` from the command line to make sure everything is working
+
+
+Copying `argil`
+---------------
+If you plan on copying the `argil` executable, you will need to edit the
+`set_include_path()` call on line 4 to make sure it points to the `src/`
+directory in the Argil tree.  Alternatively, you can copy `src/Argil/`,
+`src/ArgilCore`, and `src/ArgilImpl` into the PHP's `include_path` and
+comment out line 4 all together.

Deleted: trunk/docs/InstallingPipes
===================================================================
--- trunk/docs/InstallingPipes	2007-02-20 23:57:43 UTC (rev 493)
+++ trunk/docs/InstallingPipes	2007-02-21 01:06:13 UTC (rev 494)
@@ -1,33 +0,0 @@
-Installing Pipes
-================
-Pipes can currently be manually installed or installed via Subversion.
-
-
-Manually installing Pipes
--------------------------
-* Downloaded the latest release tarball (see http://phpinpipes.org for latest)
-* Uncompress tarball into readable directory
-* Continue to *Steps for Manual and SVN installations*
-
-
-Installing Pipes from Subversion
---------------------------------
-* Checkout the latest tag from the SVN repo (i.e. http://phpinpipes.googlecode.com/svn/tags/0.1)
-  (See notes on release numbers for more information about what release numbers mean)
-* Continue to *Steps for Manual and SVN installations*
-
-
-Steps for Manual and SVN installations
---------------------------------------
-* Create sym-link of `scripts/pipes` into an executable path (see *Copying 
-  `pipes`* if you plan on making a copy of the `pipes` script)
-* Run `pipes` from the command line to make sure everything is working
-
-
-Copying `pipes`
----------------
-If you plan on copying the `pipes` executable, you will need to edit the
-`set_include_path()` call on line 4 to make sure it points to the `src/`
-directory in the Pipes tree.  Alternatively, you can copy `src/Pipes/`,
-`src/PipesCore`, and `src/PipesImpl` into the PHP's `include_path` and
-comment out line 4 all together.

Modified: trunk/docs/Manifesto
===================================================================
--- trunk/docs/Manifesto	2007-02-20 23:57:43 UTC (rev 493)
+++ trunk/docs/Manifesto	2007-02-21 01:06:13 UTC (rev 494)
@@ -1,19 +1,19 @@
-PHP In Pipes Express Scaffolding Manifesto
-==========================================
+Argil Framework
+===============
 There are no PHP 5 MVC frameworks that do the work for you.  The best code is 
-self generating - that's what Pipes is all about.  By creating a simple MVC
-framework and command line tool to go along with it,  Pipes automates the grunt
+self generating - that's what Argil is all about.  By creating a simple MVC
+framework and command line tool to go along with it,  Argil automates the grunt
 work required to make your code function.
 
-*Note*: This document represents what Pipes will be.  This isn't poured in
-concrete yet, but this is the Manifesto that outlines where Pipes is headed on
+*Note*: This document represents what Argil will be.  This isn't poured in
+concrete yet, but this is the Manifesto that outlines where Argil is headed on
 its way to v1.0.
 
 
 Three Things Matter: Generate, Generate, Generate
 -------------------------------------------------
 The best code generates itself.  Generated code is already tested, already 
-proven, and doesn't have typos.  Pipes provides the tool to take your database
+proven, and doesn't have typos.  Argil provides the tool to take your database
 and generate the objects needed to make a basic app work.  Then you focus on the
 custom logic needed to make everything tick.
 
@@ -22,7 +22,7 @@
 ----------------------------
 You should only need to design once: when you outline your database structure.
 There are numerous tools available to help you create a database, but not as 
-many to help you create code.  Pipes allows you to create the database tables
+many to help you create code.  Argil allows you to create the database tables
 you want then it figures out what to do with all that data.
 
 
@@ -39,7 +39,7 @@
 ----------------------------------------
 OO code isn't for everyone, but good decoupling practices generally follow an
 OO style.  Most systems introduce "flexibility" by forcing you to adhere to
-their naming style while Pipes implements its flex-points by using native PHP
+their naming style while Argil implements its flex-points by using native PHP
 callbacks.
 
 
@@ -47,7 +47,7 @@
 -----------------------------------------------
 The DOM (Document Object Model) lets you navigate a properly formed XML or 
 XHTML document - those same markup languages you want your templates to output.
-Using a defined "pipes" namespace inside those documents you can control how 
+Using a defined "argil" namespace inside those documents you can control how 
 templates are loaded.  No new markup languages to learn.
 
 
@@ -55,7 +55,7 @@
 ------------------------
 Denormalized databases are the norm, but creating all of the tables and code to
 handle that denormalization is time consuming.  By supplying a command line
-argument to the `pipes` script, it can create the code to handle your 
+argument to the `argil` script, it can create the code to handle your 
 relationships and the required database tables automatically.
 
 
@@ -63,14 +63,14 @@
 -------------------------------
 Tagging has become the defacto categorization of Web2.0 and you probably want 
 your new app to have it.  Your new framework should support tagging your new 
-tables without any fuss.  'pipes create bookmarks --with=tags' and your new
+tables without any fuss.  'argil create Bookmark --with=Tag' and your new
 bookmark controller will have tagging automatically built-in.
 
 
 Service First: Built-in web services
 ------------------------------------
 Focusing on Web2.0 means focusing on mashups.  Mashups need Web Services.  
-Pipes wraps HTTP request object for handling those requests to web services and
+Argil wraps HTTP request object for handling those requests to web services and
 has a growing catalog of Web Services that it supports out of the box, including 
 del.icio.us, Yahoo! Geocoding, Amazon ECS, Amazon SQS, and Amazon S3.
 

Modified: trunk/docs/OneMinuteTutorial
===================================================================
--- trunk/docs/OneMinuteTutorial	2007-02-20 23:57:43 UTC (rev 493)
+++ trunk/docs/OneMinuteTutorial	2007-02-21 01:06:13 UTC (rev 494)
@@ -1,22 +1,22 @@
 One Minute Tutotrial
 ====================
 
-What is Pipes
+What is Argil
 -------------
-Pipes is a rapid application development framework designed to assist 
+Argil is a rapid application development framework designed to assist 
 developers in creating MVC applications quickly and effectiently.
 
 
-How to use Pipes
+How to use Argil
 ----------------
-* [Install](./InstallingPipes) Pipes
-* Create the database you want to use - `pipes_demo`
+* [Install](./InstallingArgil) Argil
+* Create the database you want to use - `argil_demo`
 * Add a table called `messages` with the fields `message_id` and `message`
-* Run `pipes start PipesDemo`
-* Change directories to `./PipesDemo'
+* Run `argil start ArgilDemo`
+* Change directories to `./ArgilDemo'
 * Edit config.php, adjusting the PDO object to match your configuration
-* In the `./PipesDemo` directory, run `pipes create Message`
-* Create a link, or copy the files from `./PipesDemo/Public/` into a web 
+* In the `./ArgilDemo` directory, run `argil create Message`
+* Create a link, or copy the files from `./ArgilDemo/Public/` into a web 
   accessible directory.
-* Assuming the previous step copied into /pipes/ of localhost, access your
-  new application at `http://localhost/pipes/index.php/Message`
+* Assuming the previous step copied into /argil/ of localhost, access your
+  new application at `http://localhost/argil/index.php/Message`

Deleted: trunk/docs/PipesAjaxApi
===================================================================
--- trunk/docs/PipesAjaxApi	2007-02-20 23:57:43 UTC (rev 493)
+++ trunk/docs/PipesAjaxApi	2007-02-21 01:06:13 UTC (rev 494)
@@ -1,5 +0,0 @@
-Pipes Javascript/AJAX API
-=========================
-As I move past version 0.1 and toward 0.2, this page will contain an outline
-of the Javascript API.
-


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.