[Cubicweb] Understanding _cw

Christophe de Vienne christophe at unlish.com
Fri May 16 15:03:33 CEST 2014

Le 16/05/2014 14:46, Sylvain Thénault a écrit :
> On 16 mai 14:33, Christophe de Vienne wrote:
>> Le 16/05/2014 14:15, Sylvain Thénault a écrit :
>>> ok, fine. I fully agree that everything that allows cubicweb to look similar to
>>> other popular framework such as pyramid is a good step forward by easing its
>>> adoption. Ultimatly, having cubicweb specificities on top of a generic web
>>> framework as pyramid would be awesome (IMO).
>> Well, I am currently working a bit with pyramid (for which I help a
>> client to build an openerp frontend, with lots form autogeneration,
>> non-trivial acls, resource traversal _and_ url dispatch etc), while
>> getting my hand on the cw internals thanks to the oauth and wsme cubes.
>> And it strikes me everytime how similar the two frameworks are in some
>> areas, which are the ones CW has little added value (I have in mind the
>> http request handling & dispatch, url resolver, authentication,
>> interface with controllers, source scan for registering objects, auto
>> reload...).
>> The things CW is good at (rql, hooks, orm & views) could totally fit on
>> top of these basic features.
> You get me.
>> I pretty convinced that pyramid could be the base of cw, and that a
>> progressive path exists to get there.
>> I want to experiment around this idea and be able to really demonstrate
>> the feasibility before putting it forward too much, but if someone is
>> interested to dig this subject with me you are very welcome to!
> I'm definitly interested but unfortunatly lack time to really help in an other
> way than responding to emails on the mailing list. But if the path to reach this
> becomes clearer, we may find some resources at Logilab to help.

That is all I need to invest some time on that. It will not be very soon
though, we have a startup to take care of after all :-)


More information about the Cubicweb mailing list