[doc] [gentle-introduction] fixed image references

fabpot · fabpot · commit 9868c2070b32 · 2010-04-01T05:26:56.000Z
diff --git a/gentle-introduction/en/02-Exploring-Symfony-s-Code.markdown b/gentle-introduction/en/02-Exploring-Symfony-s-Code.markdown
@@ -18,7 +18,7 @@ The MVC architecture separates the business logic (model) and the presentation (
 
 Figure 2-1 - The MVC pattern
 
-![The MVC pattern](/images/book/F0201.png "The MVC pattern")
+![The MVC pattern](http://www.symfony-project.org/images/book/1_4/F0201.png "The MVC pattern")
 
 ### MVC Layering
 
@@ -332,7 +332,7 @@ And the last thing is that the view logic can be easily translated as a simple c
 
 Figure 2-2 - Symfony workflow
 
-![Symfony workflow](/images/book/F0202.png "Symfony workflow")
+![Symfony workflow](http://www.symfony-project.org/images/book/1_4/F0202.png "Symfony workflow")
 
 That means that the list of posts described in our example would require only three files to work in symfony, as shown in Listings 2-11, 2-12, and 2-13.
 
@@ -419,7 +419,7 @@ Figure 2-3 shows a sample code organization for a weblog project, in a project/a
 
 Figure 2-3 - Example of code organization
 
-![Example of code organization](/images/book/F0203.png "Example of code organization")
+![Example of code organization](http://www.symfony-project.org/images/book/1_4/F0203.png "Example of code organization")
 
 ### File Tree Structure
 
diff --git a/gentle-introduction/en/04-The-Basics-of-Page-Creation.markdown b/gentle-introduction/en/04-The-Basics-of-Page-Creation.markdown
@@ -53,7 +53,7 @@ The default `index` action will not be used in this chapter, so you can remove t
 
 Figure 4-1 - The default generated index page
 
-![The default generated index page](/images/book/F0401.jpg "The default generated index page")
+![The default generated index page](http://www.symfony-project.org/images/book/1_4/F0401.jpg "The default generated index page")
 
 Adding a Page
 -------------
diff --git a/gentle-introduction/en/06-Inside-the-Controller-Layer.markdown b/gentle-introduction/en/06-Inside-the-Controller-Layer.markdown
@@ -627,7 +627,7 @@ The default login and secure pages are pretty simple, and you will probably want
 
 Figure 6-1 - The default secure action page
 
-![The default secure action page](/images/book/F0601.jpg "The default secure action page")
+![The default secure action page](http://www.symfony-project.org/images/book/1_4/F0601.jpg "The default secure action page")
 
 Listing 6-22 - Default Security Actions Are Defined in `apps/frontend/config/settings.yml`
 
@@ -745,7 +745,7 @@ Symfony actually sees the processing of a request as a chain of filters. When a
 
 Figure 6-3 - Sample filter chain
 
-![Sample filter chain](/images/book/F0603.png "Sample filter chain")
+![Sample filter chain](http://www.symfony-project.org/images/book/1_4/F0603.png "Sample filter chain")
 
 This process justifies the structure of the filter classes. They all extend the `sfFilter` class, and contain one `execute()` method, expecting a `$filterChain` object as parameter. Somewhere in this method, the filter passes to the next filter in the chain by calling `$filterChain->execute()`. See Listing 6-28 for an example. So basically, filters are divided into two parts:
 
diff --git a/gentle-introduction/en/07-Inside-the-View-Layer.markdown b/gentle-introduction/en/07-Inside-the-View-Layer.markdown
@@ -130,7 +130,7 @@ The template shown in Listing 7-1 is not a valid XHTML document. The `DOCTYPE` d
 
 Figure 7-1 - Decorating a template with a layout
 
-![Decorating a template with a layout](/images/book/F0701.png "Decorating a template with a layout")
+![Decorating a template with a layout](http://www.symfony-project.org/images/book/1_4/F0701.png "Decorating a template with a layout")
 
 Listing 7-5 shows the default page layout, located in the application `templates/` directory.
 
@@ -226,7 +226,7 @@ A partial is a reusable chunk of template code. For instance, in a publication a
 
 Figure 7-2 - Reusing partials in templates
 
-![Reusing partials in templates](/images/book/F0702.png "Reusing partials in templates")
+![Reusing partials in templates](http://www.symfony-project.org/images/book/1_4/F0702.png "Reusing partials in templates")
 
 Just like templates, partials are files located in the `templates/` directory, and they contain HTML code with embedded PHP. A partial file name always starts with an underscore (`_`), and that helps to distinguish partials from templates, since they are located in the same `templates/` folders.
 
@@ -318,7 +318,7 @@ For this example, shown in Listings 7-11 and 7-12, the component will be kept in
 
 Figure 7-3 - Using components in templates
 
-![Using components in templates](/images/book/F0703.png "Using components in templates")
+![Using components in templates](http://www.symfony-project.org/images/book/1_4/F0703.png "Using components in templates")
 
 Listing 7-11 - The Components Class, in `modules/news/actions/components.class.php`
 
@@ -384,7 +384,7 @@ Imagine a layout with one zone for the template and two slots: one for the sideb
 
 Figure 7-4 - Layout slots defined in a template
 
-![Layout slots defined in a template](/images/book/F0704.png "Layout slots defined in a template")
+![Layout slots defined in a template](http://www.symfony-project.org/images/book/1_4/F0704.png "Layout slots defined in a template")
 
 Seeing some code will clarify things further. To include a slot, use the `include_slot()` helper. The `has_slot()` helper returns `true` if the slot has been defined before, providing a fallback mechanism as a bonus. For instance, define a placeholder for a `'sidebar'` slot in the layout and its default content as shown in Listing 7-14.
 
diff --git a/gentle-introduction/en/08-Inside-the-Model-Layer.markdown b/gentle-introduction/en/08-Inside-the-Model-Layer.markdown
@@ -63,7 +63,7 @@ How do you translate a database structure into a schema? An example is the best
 
 Figure 8-1 - A blog database table structure
 
-![A blog database table structure](/images/book/F0801.png "A blog database table structure")
+![A blog database table structure](http://www.symfony-project.org/images/book/1_4/F0801.png "A blog database table structure")
 
 The related `schema.yml` file should look like Listing 8-3.
 
diff --git a/gentle-introduction/en/09-Links-and-the-Routing-System.markdown b/gentle-introduction/en/09-Links-and-the-Routing-System.markdown
@@ -26,7 +26,7 @@ This URL conveys information about the application's architecture and database.
 
 Figure 9-1 - URLs appear in many places, such as in search results
 
-![URLs appear in many places, such as in search results](/images/book/F0901.png "URLs appear in many places, such as in search results")
+![URLs appear in many places, such as in search results](http://www.symfony-project.org/images/book/1_4/F0901.png "URLs appear in many places, such as in search results")
 
   * If one URL has to be changed (for instance, if a script name or one of its parameters is modified), every link to this URL must be changed as well. It means that modifications in the controller structure are heavyweight and expensive, which is not ideal in agile development.
 
@@ -52,7 +52,7 @@ The benefits are immense:
 
 Figure 9-2 - URLs can convey additional information about a page, like the publication date
 
-![URLs can convey additional information about a page, like the publication date](/images/book/F0902.png "URLs can convey additional information about a page, like the publication date")
+![URLs can convey additional information about a page, like the publication date](http://www.symfony-project.org/images/book/1_4/F0902.png "URLs can convey additional information about a page, like the publication date")
 
   * URLs written in paper documents are easier to type and remember. If your company website appears as `http://www.example.com/controller/web/index.jsp?id=ERD4` on your business card, it will probably not receive many visits.
   * The URL can become a command-line tool of its own, to perform actions or retrieve information in an intuitive way. Applications offering such a possibility are faster to use for power users.
diff --git a/gentle-introduction/en/12-Caching.markdown b/gentle-introduction/en/12-Caching.markdown
@@ -36,7 +36,7 @@ Actions displaying static information (not depending on database or session-depe
 
 Figure 12-1 - Caching an action
 
-![Caching an action](/images/book/F1201.png "Caching an action")
+![Caching an action](http://www.symfony-project.org/images/book/1_4/F1201.png "Caching an action")
 
 For instance, consider a `user/list` action that returns the list of all users of a website. Unless a user is modified, added, or removed (and this matter will be discussed later in the "Removing Items from the Cache" section), this list always displays the same information, so it is a good candidate for caching.
 
@@ -96,7 +96,7 @@ Chapter 7 explained how to reuse code fragments across several templates, using
 
 Figure 12-2 - Caching a partial or component
 
-![Caching a partial or component](/images/book/F1202.png "Caching a partial or component")
+![Caching a partial or component](http://www.symfony-project.org/images/book/1_4/F1202.png "Caching a partial or component")
 
 For instance, Listing 12-4 shows how to edit the `cache.yml` file to enable the cache on a `_my_partial.php` partial located in the `user` module. Note that the `with_layout` setting doesn't make sense in this case.
 
@@ -141,7 +141,7 @@ Action caching applies to only a subset of actions. For the other actions--those
 
 Figure 12-3 - Caching a template fragment
 
-![Caching a template fragment](/images/book/F1203.png "Caching a template fragment")
+![Caching a template fragment](http://www.symfony-project.org/images/book/1_4/F1203.png "Caching a template fragment")
 
 For instance, you may have a list of users that shows a link of the last-accessed user, and this information is dynamic. The `cache()` helper defines the parts of a template that are to be put in the cache. See Listing 12-5 for details on the syntax.
 
@@ -485,7 +485,7 @@ The last number on the right side of the debug toolbar is the duration of the re
 
 Figure 12-4 - Web debug toolbar for pages using caching
 
-![Web debug toolbar for pages using caching](/images/book/F1204.png "Web debug toolbar for pages using caching")
+![Web debug toolbar for pages using caching](http://www.symfony-project.org/images/book/1_4/F1204.png "Web debug toolbar for pages using caching")
 
 The debug toolbar also shows the number of database queries executed during the processing of the request, and the detail of the durations per category (click the total duration to display the detail). Monitoring this data, in conjunction with the total duration, will help you do fine measures of the performance improvements brought by the cache.
 
@@ -501,7 +501,7 @@ When the web debug toolbar is enabled, the cached elements are identified in a p
 
 Figure 12-5 - Identification for cached elements in a page
 
-![Identification for cached elements in a page](/images/book/F1205.png "Identification for cached elements in a page")
+![Identification for cached elements in a page](http://www.symfony-project.org/images/book/1_4/F1205.png "Identification for cached elements in a page")
 
 HTTP 1.1 and Client-Side Caching
 --------------------------------
diff --git a/gentle-introduction/en/14-Admin-Generator.markdown b/gentle-introduction/en/14-Admin-Generator.markdown
diff --git a/gentle-introduction/en/16-Application-Management-Tools.markdown b/gentle-introduction/en/16-Application-Management-Tools.markdown
diff --git a/gentle-introduction/en/19-Mastering-Symfony-s-Configuration-Files.markdown b/gentle-introduction/en/19-Mastering-Symfony-s-Configuration-Files.markdown
