[repository] #1460066: backport datafeed cube as cubicweb source
* add some attributes to CWSource to handle this kind of source
(not natural to put everything in 'config' string). Adding a CWSource
subclass has been attempted then rollbacked because it adds pain
to handle multi-sources planning and it introduce an ambiguity on
a generic relation (cw_source), which may be a penalty in multiple
case
* data feed sources are a new kind of source, namely 'copy based',
which have no effect on the query planner
* a data feed source is associated to a list of url and a parser (appobjects
in the 'parsers' registry
* entities imported by a data feed have cwuri set to their url on the distant
site, their cw_source relation point to the data feed source, though their
source stored in the entities table (returned by cw_metainformation) is their
physical source, hence 'system'
=========================================
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.
FAQ
====
- How do I keep the old style?
Put ``STYLESHEET = [data('cubicweb.old.css')]`` in your uiprops.py
file and think about something else.
- What are the changes in cubicweb.css?
Version 3.9.0 of cubicweb changed the following in the default html
markup and css:
=============== ==================================
old new
=============== ==================================
.navcol #navColumnLeft, #navColumnRight
#contentcol #contentColumn
.footer #footer
.logo #logo
.simpleMessage .loginMessage
.appMsg (styles are removed from css)
.searchMessage (styles are removed from css)
=============== ==================================
Introduction of the new cubicweb.reset.css based on Eric Meyer's
reset css.
Lots of margin, padding, etc.