nojhan/weboob-devel
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Some missing renames of ICap to Cap

Browse source 
refs #1424
This commit is contained in:
Laurent Bachelier 2014-07-08 11:58:37 +02:00 • committed by Florent
commit dd4a66be77
3 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/source/guides/capability.rst
View file

@ -12,9 +12,9 @@ Prefer returning objects
^^^^^^^^^^^^^^^^^^^^^^^^
Python is an object-oriented language, so when your capability supports entities (for example
:class:`weboob.capabilities.video.BaseVideo` with the :class:`weboob.capabilities.video.ICapVideo` capability),
:class:`weboob.capabilities.video.BaseVideo` with the :class:`weboob.capabilities.video.CapVideo` capability),
you have to create a class derived from :class:`weboob.capabilities.base.BaseObject`, and create an unique method
to get it (for example :func:`get_video() <weboob.capabilities.video.ICapVideo.get_video>`), instead of several methods like
to get it (for example :func:`get_video() <weboob.capabilities.video.CapVideo.get_video>`), instead of several methods like
``get_video_url()``, ``get_video_preview()``, etc.
An object has an unique ID.

2
docs/source/overview.rst
View file

@ -23,7 +23,7 @@ Capabilities
The core library defines capabilities. They represent features common to various websites.
For example, http://www.youtube.com and http://www.dailymotion.com are both videos
providers: Weboob defines the ``ICapVideo`` capability.
providers: Weboob defines the ``CapVideo`` capability.
Each backend interfaces a website and implements one or many of these
capabilities. Backends can be configured, which means that the end-user can