fix stupid sed
authorSylvain Thénault <sylvain.thenault@logilab.fr>
Wed, 03 Feb 2010 20:33:49 +0100
changeset 4442 7bc0e4ed4109
parent 4441 550cf406dbc6
child 4443 83ff2bb898a5
fix stupid sed
doc/book/en/development/datamodel/definition.rst
doc/book/en/development/devcore/vreg.rst
doc/book/en/development/devweb/css.rst
doc/book/en/development/devweb/index.rst
doc/book/en/development/devweb/internationalization.rst
doc/book/en/development/devweb/request.rst
doc/book/en/development/devweb/views.rst
doc/book/en/development/entityclasses/data-as-objects.rst
doc/book/en/development/migration/index.rst
doc/book/en/development/webstdlib/editcontroller.rst
doc/book/en/intro/concepts/index.rst
--- a/doc/book/en/development/datamodel/definition.rst	Wed Feb 03 19:26:35 2010 +0100
+++ b/doc/book/en/development/datamodel/definition.rst	Wed Feb 03 20:33:49 2010 +0100
@@ -283,7 +283,7 @@
 
 * in this expression, the variables X and U are pre-defined references
   respectively on the current entity (on which the action is verified) and
-  on the user who send the._cwuest
+  on the user who send the request
 
 * it is possible to use, in this expression, a special relation
   "has_<ACTION>_permission" where the subject is the user and the
--- a/doc/book/en/development/devcore/vreg.rst	Wed Feb 03 19:26:35 2010 +0100
+++ b/doc/book/en/development/devcore/vreg.rst	Wed Feb 03 20:33:49 2010 +0100
@@ -155,7 +155,7 @@
 ``````````````````````
 
 Selectors are to be used whenever arises the need of dispatching on the shape or
-content of a result set or whatever else context (value in._cwuest form params,
+content of a result set or whatever else context (value in request form params,
 authenticated user groups, etc...). That is, almost all the time.
 
 XXX add and example of a single view w/ big "if" inside splitted into two views
--- a/doc/book/en/development/devweb/css.rst	Wed Feb 03 19:26:35 2010 +0100
+++ b/doc/book/en/development/devweb/css.rst	Wed Feb 03 20:33:49 2010 +0100
@@ -7,7 +7,7 @@
 
 XXX external_resources variable
     naming convention
-   ._cwuest.add_css
+    request.add_css
 
 
 Extending / overriding existing styles
--- a/doc/book/en/development/devweb/index.rst	Wed Feb 03 19:26:35 2010 +0100
+++ b/doc/book/en/development/devweb/index.rst	Wed Feb 03 20:33:49 2010 +0100
@@ -6,7 +6,7 @@
 .. toctree::
    :maxdepth: 1
 
-  ._cwuest
+   request
    publisher
    controllers
    property
--- a/doc/book/en/development/devweb/internationalization.rst	Wed Feb 03 19:26:35 2010 +0100
+++ b/doc/book/en/development/devweb/internationalization.rst	Wed Feb 03 20:33:49 2010 +0100
@@ -35,7 +35,7 @@
 
   OR
 
- * by using the equivalent._cwuest's method ::
+ * by using the equivalent request's method ::
 
      class NoResultView(EmptyRsetView):
          """default view when no result has been found"""
@@ -50,10 +50,10 @@
 itself, but not its translation (it's actually another name for the
 `unicode` builtin).
 
-In the other hand the._cwuest's method `self._cw._` is meant to retrieve the
-proper translation of translation strings in the._cwuested language.
+In the other hand the request's method `self._cw._` is meant to retrieve the
+proper translation of translation strings in the requested language.
 
-Finally you can also use the `__` attribute of._cwuest object to get a
+Finally you can also use the `__` attribute of request object to get a
 translation for a string *which should not itself added to the catalog*,
 usually in case where the actual msgid is created by string interpolation ::
 
--- a/doc/book/en/development/devweb/request.rst	Wed Feb 03 19:26:35 2010 +0100
+++ b/doc/book/en/development/devweb/request.rst	Wed Feb 03 20:33:49 2010 +0100
@@ -3,10 +3,10 @@
 The `Request` class (`cubicweb.web`)
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-A._cwuest instance is created when an HTTP._cwuest is sent to the web server.
+A request instance is created when an HTTP request is sent to the web server.
 It contains informations such as form parameters, user authenticated, etc.
 
-**Globally, a._cwuest represents a user query, either through HTTP or not
+**Globally, a request represents a user query, either through HTTP or not
 (we also talk about RQL queries on the server side for example).**
 
 An instance of `Request` has the following attributes:
@@ -36,21 +36,21 @@
   * `remove_cookie(cookie, key)`, forces a value to expire
 
 :URL handling:
-  * `url()`, returns the full URL of the HTTP._cwuest
+  * `url()`, returns the full URL of the HTTP request
   * `base_url()`, returns the root URL of the web application
-  * `relative_path()`, returns the relative path of the._cwuest
+  * `relative_path()`, returns the relative path of the request
 
 :And more...:
   * `set_content_type(content_type, filename=None)`, adds the header HTTP
     'Content-Type'
   * `get_header(header)`, returns the value associated to an arbitrary header
-    of the HTTP._cwuest
+    of the HTTP request
   * `set_header(header, value)`, adds an arbitrary header in the response
   * `cursor()` returns a RQL cursor on the session
   * `execute(*args, **kwargs)`, shortcut to ``.cursor().execute()``
   * `property_value(key)`, properties management (`CWProperty`)
   * dictionary `data` to store data to share informations between components
-    *while a._cwuest is executed*
+    *while a request is executed*
 
 Please note that this class is abstract and that a concrete implementation
 will be provided by the *frontend* web used (in particular *twisted* as of
--- a/doc/book/en/development/devweb/views.rst	Wed Feb 03 19:26:35 2010 +0100
+++ b/doc/book/en/development/devweb/views.rst	Wed Feb 03 20:33:49 2010 +0100
@@ -34,7 +34,7 @@
     * the `category` attribute may be used in the interface to regroup related
       objects together
 
-At instantiation time, the standard ._cw` and `rset` attributes are
+At instantiation time, the standard `_cw` and `cw_rset` attributes are
 added and the `w` attribute will be set at rendering time.
 
 A view writes to its output stream thanks to its attribute `w` (an
@@ -58,7 +58,7 @@
 
 * `view(__vid, rset, __fallback_vid=None, **kwargs)`, call the view of identifier
   `__vid` on the given result set. It is possible to give a view identifier
-  of fallback that will be used if the view._cwuested is not applicable to the
+  of fallback that will be used if the view requested is not applicable to the
   result set. This is actually defined on the AppObject class.
 
 * `wview(__vid, rset, __fallback_vid=None, **kwargs)`, similar to `view` except
@@ -176,14 +176,14 @@
 render_entity_relations method of a Blog's primary view. Here we want
 to display our blog entries in a custom way.
 
-At `line 10`, a simple._cwuest is made to build a result set with all
+At `line 10`, a simple request is made to build a result set with all
 the entities linked to the current ``Blog`` entity by the relationship
-``entry_of``. The part of the framework handling the._cwuest knows
+``entry_of``. The part of the framework handling the request knows
 about the schema and infers that such entities have to be of the
 ``BlogEntry`` kind and retrieves them (in the prescribed publish_date
 order).
 
-The._cwuest returns a selection of data called a result set. Result
+The request returns a selection of data called a result set. Result
 set objects have an .entities() method returning a generator on
 requested entities (going transparently through the `ORM` layer).
 
@@ -223,7 +223,7 @@
    :alt: a blog and all its entries
 
 **Before we move forward, remember that the selection/view principle is
-at the core of *CubicWeb*. Everywhere in the engine, data is._cwuested
+at the core of *CubicWeb*. Everywhere in the engine, data is requested
 using the RQL language, then HTML/XML/text/PNG is output by applying a
 view to the result set returned by the query. That is where most of the
 flexibility comes from.**
--- a/doc/book/en/development/entityclasses/data-as-objects.rst	Wed Feb 03 19:26:35 2010 +0100
+++ b/doc/book/en/development/entityclasses/data-as-objects.rst	Wed Feb 03 20:33:49 2010 +0100
@@ -30,9 +30,9 @@
 :Data handling:
 
   * `as_rset()`, converts the entity into an equivalent result set simulating the
-    ._cwuest `Any X WHERE X eid _eid_`
+     request `Any X WHERE X eid _eid_`
 
-  * `complete(skip_bytes=True)`, executes a._cwuest that recovers all at once
+  * `complete(skip_bytes=True)`, executes a request that recovers all at once
     all the missing attributes of an entity
 
   * `get_value(name)`, returns the value associated to the attribute name given
--- a/doc/book/en/development/migration/index.rst	Wed Feb 03 19:26:35 2010 +0100
+++ b/doc/book/en/development/migration/index.rst	Wed Feb 03 20:33:49 2010 +0100
@@ -79,7 +79,7 @@
 
 In the `repository` scripts, the following identifiers are also defined:
 
-* `checkpoint`,._cwuest confirming and executing a "commit" at checking point
+* `checkpoint`, request confirming and executing a "commit" at checking point
 
 * `schema`, instance schema (readen from the database)
 
--- a/doc/book/en/development/webstdlib/editcontroller.rst	Wed Feb 03 19:26:35 2010 +0100
+++ b/doc/book/en/development/webstdlib/editcontroller.rst	Wed Feb 03 20:33:49 2010 +0100
@@ -26,7 +26,7 @@
       for this relaiton and we then look for the new value(s)  in the parameter
       <relation name> (qualified)
    3. if the value returned is different from the initial value, an database update
-     ._cwuest is done
+      request is done
 
 3. For each entity to edit:
 
@@ -102,7 +102,7 @@
 
 * `__redirectparams`: forms parameters to add to the path
 
-* `__redirectrql`: redirection RQL._cwuest
+* `__redirectrql`: redirection RQL request
 
 * `__redirectvid`: redirection view identifier
 
--- a/doc/book/en/intro/concepts/index.rst	Wed Feb 03 19:26:35 2010 +0100
+++ b/doc/book/en/intro/concepts/index.rst	Wed Feb 03 20:33:49 2010 +0100
@@ -99,7 +99,7 @@
 Web Engine
 ----------
 
-The web engine replies to http._cwuests and runs the user interface
+The web engine replies to http requests and runs the user interface
 and most of the application logic.
 
 By default the web engine provides a default user interface based on
@@ -228,7 +228,7 @@
 Result set
 ~~~~~~~~~~
 
-Every._cwuest made (using RQL) to the data repository returns an
+Every request made (using RQL) to the data repository returns an
 object we call a Result Set. It enables easy use of the retrieved
 data, providing a translation layer between the backend's native
 datatypes and |cubicweb| schema's EntityTypes.