[Cubicweb] floating ideas around
sylvain.thenault at logilab.fr
Mon Jan 13 16:35:09 CET 2014
On 10 janvier 21:11, Nicolas Chauvat wrote:
> * Idea 2: dependencies between AppObjects
> Assuming Idea 1 gets implemented, we may get to a point where an
> AppObject is loaded without the other AppObject it relies on being
> also loaded. For example view A is loaded, but it will call another
> view B that is not loaded. This would result in an exception of the
> kind "object not found in registry" when A is executed.
> To prevent that problem to be detectable only at runtime, a
> dependency mechanism could be introduced to allow appobjects to
> explicitly state that they need another appobject to execute
> Once the registries are loaded, a consistency check could be
> performed to detect the missing appobjects.
> A bit more evoluted would be, if A is explicitly loaded with the
> option "include dependencies", to look for and load the dependencies
> of A, namely B.
notice there already exists some code to handle parent classes wrt registration.
Sylvain Thénault, LOGILAB, Paris (01.45.32.03.12) - Toulouse (05.62.17.16.42)
Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations
Développement logiciel sur mesure: http://www.logilab.fr/services
CubicWeb, the semantic web framework: http://www.cubicweb.org
More information about the Cubicweb