[server/session] Roll back in connection exit
This was changed in commit 8b35a898b334 "[server] remove cnxset
tracking, it is now unneeded".
When exiting a CubicWeb Connection, the database connection is put back
into the common pool. At that point anything done during the lifetime
of the CubicWeb Connection needs to be committed or rolled back.
Do a proper rollback to finish the transaction, as was happening before
the above-mentionned commit.
This showed up on testing with postgresql, when a DB schema modification
was blocked by an old connection that was still "in transaction".
=========================================
Refactoring the CSSs with UI properties
=========================================
Overview
=========
Managing styles progressively became difficult in CubicWeb. The
introduction of uiprops is an attempt to fix this problem.
The goal is to make it possible to use variables in our CSSs.
These variables are defined or computed in the uiprops.py python file
and inserted in the CSS using the Python string interpolation syntax.
A quick example, put in ``uiprops.py``::
defaultBgColor = '#eee'
and in your css::
body { background-color: %(defaultBgColor)s; }
The good practices are:
- define a variable in uiprops to avoid repetitions in the CSS
(colors, borders, fonts, etc.)
- define a variable in uiprops when you need to compute values
(compute a color palette, etc.)
The algorithm implemented in CubicWeb is the following:
- read uiprops file while walk up the chain of cube dependencies: if
cube myblog depends on cube comment, the variables defined in myblog
will have precedence over the ones in comment
- replace the %(varname)s in all the CSSs of all the cubes
Keep in mind that the browser will then interpret the CSSs and apply
the standard cascading mechanism.