[entity] introduce a new 'adapters' registry This changeset introduces the notion in adapters (as in Zope Component Architecture) in a cubicweb way, eg using a specific registry of appobjects. This allows nicer code structure, by avoid clutering entity classes and moving code usually specific to a place of the ui (or something else) together with the code that use the interface. We don't use actual interface anymore, they are implied by adapters (which may be abstract), whose reg id is an interface name. Appobjects that used to 'implements(IFace)' should now be rewritten by: * coding an IFaceAdapter(EntityAdapter) defining (implementing if desired) the interface, usually with __regid__ = 'IFace' * use "adaptable('IFace')" as selector instead Also, the implements_adapter_compat decorator eases backward compatibility with adapter's methods that may still be found on entities implementing the interface. Notice that unlike ZCA, we don't support automatic adapters chain (yagni?). All interfaces defined in cubicweb have been turned into adapters, also some new ones have been introduced to cleanup Entity / AnyEntity classes namespace. At the end, the pluggable mixins mecanism should disappear in favor of adapters as well.

     1

.. _Part2:

     2

     3

----------------------

     4

Repository development

     5

----------------------

     6

     7

This part is about developing applications with the *CubicWeb*

     8

framework. It is not concerned with the web system, which is a

     9

separate layer and has its own whole chapter.

    10

    11

.. toctree::

    12

   :maxdepth: 2

    13

   :numbered:

    14

    15

   cubes/index

    16

   vreg.rst

    17

   datamodel/index

    18

   entityclasses/index

    19

   devcore/index

    20

   repo/index

    21

   testing.rst

    22

   migration.rst

    23

   profiling.rst