cubicweb: comparison doc/tutorials/base/customizing-the-application.rst

equal deleted inserted replaced

-:be86a3a86af7
+:72ba5f5278e0
 content such as HTML or Restructured text.
 * a `Community` may be linked to a `Blog` using the `community_blog` relation
 - ``*`` means a community may be linked to 0 to N blog, ``?`` means a blog may
-be linked to 0 to 1 community. For completeness, remember that you can also
+be linked to 0 to 1 community. For completeness, you can also use ``+`` for
-use ``+`` for 1 to N, and ``1`` for single, mandatory relation (e.g. one to one);
+1 to N, and ``1`` for single, mandatory relation (e.g. one to one);
 - this is a composite relation where `Community` (e.g. the subject of the
 relation) is the composite. That means that if you delete a community, its
 blog will be deleted as well.
 .. _TutosBaseCustomizingTheApplicationCustomViews:
 Defining your views
 ~~~~~~~~~~~~~~~~~~~
-|cubicweb| provides a lot of standard views in directory
+|cubicweb| provides a lot of standard views in the directory
 :file:`cubicweb/web/views/`. We already talked about 'primary' and 'list' views,
 which are views which apply to one ore more entities.
 A view is defined by a python class which includes:
 - an identifier: all objects used to build the user interface in |cubicweb| are
 recorded in a registry and this identifier will be used as a key in that
-registry. There may be multiple views for the same identifier.
+registry to store the view. There may be multiple views for the same identifier.
 - a *selector*, which is a kind of filter telling how well a view suit to a
 particular context. When looking for a particular view (e.g. given an
 identifier), |cubicweb| computes for each available view with that identifier
 a score which is returned by the selector. Then the view with the highest
 * We set on it a selector telling that it only applies when trying to display
 some entity of the `Community` type. This is enough to get an higher score than
 the default view for entities of this type.
-* View applying to entities usually have to define `cell_call` as entry point,
+* A view that applies to an entity usually have to define the method
-and are given `row` and `col` arguments tell to which entity in the result set
+`cell_call` as an entry point. This method will received the arguments
-the view is applied. We can then get this entity from the result set
+`row` and `col` that tell to which entity in the result set the view is
-(`self.cw_rset`) by using the `get_entity` method.
+applied. We can then get this entity from the result set (`self.cw_rset`) by
+using the `get_entity` method.
 * To ease thing, we access our entity's attribute for display using its
 printable_value method, which will handle formatting and escaping when
 necessary. As you can see, you can also access attributes by their name on the
 entity to get the raw value.
 to build our page using true object oriented programming techniques, that no
 template language provides.
 A library of standard cubes is available from `CubicWeb Forge`_, to address a
-lot of common concerns such has manipulating people, files, things to do, etc. In
+lot of common concerns such has manipulating files, people, things to do, etc. In
 our community blog case, we could be interested for instance in functionalities
 provided by the `comment` and `tag` cubes. The former provides threaded
 discussion functionalities, the latter a simple tag mechanism to classify content.
 Let's say we want to try those. We will first modify our cube's :file:`__pkginfo__.py`
 file:
 So in the case above we activated comments on `BlogEntry` entities and tags on
 both `Community` and `BlogEntry`. Various views from both `comment` and `tag`
 cubes will then be automatically displayed when one of those relations is
 supported.
-Let's synchronize the data model as we've done earlier: ::
+Let's install the cubes and synchronize the data model as we've done earlier: ::
 $ cubicweb-ctl stop myblog
 $ cubicweb-ctl shell myblog
 entering the migration python shell

changeset 12366	72ba5f5278e0
parent 12365	be86a3a86af7
child 12367	77342fae06fb