[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'
/* styles for the calendar popup widget used to edit date fields
*
* :organization: Logilab
* :copyright: 2003-2010 LOGILAB S.A. (Paris, FRANCE), all rights reserved.
* :contact: http://www.logilab.fr/ -- mailto:contact@logilab.fr
*/
div.calhelper {
background: url("calendar.gif") no-repeat;
border: 4px solid red;
padding-left:18px;
width: 10px;
height: 10px;
display: inline;
}
div.calpopup {
position: absolute;
margin-left: 130px;
margin-top: -16px;
width: 17em;
}
table.popupCalendar {
text-align: center;
border: 1px solid #ccc;
z-index: 400;
}
table.popupCalendar th {
border:1px solid #ccc;
background : #d9d9c1;
color: black;
padding: 2px 3px;
}
table.popupCalendar th.calTitle,
table.popupCalendar th.prev,
table.popupCalendar th.next {
color: white;
padding: 0px;
background : #acac95;
}
table.popupCalendar th.prev,
table.popupCalendar th.next {
color: #ff4500;
font-size: 50%;
font-weight: bold;
padding: 2px 0px;
}
table.popupCalendar td {
width: 2em;
height: 2em;
background : #f6f5e1;
font-size: 85%;
border:1px solid #ccc;
}
table.popupCalendar td.today {
border: 2px solid black;
}