[breadcrumbs] make it easier to redefine html structure of breadcrumbs component

merge

add textparser object, designed to trigger some actions from textual content such as email or checkin-message (unused in the library itself yet, see email cube)

more helpful error message

add XX reminder

ensure pb is not None

fix rgx_action to ensure eids given to .execute are correctly typed

try to update ldap tests to make them work from the DMZ (eg using another ldap directory)

no progress bar in apycot environment

merge

test and fix case where remove_unsused_solutions remove some solutions that should be kept

added days_in_year function

merge

deactivate toolbox until 3.6

cleanup

[common] add tr, th and td tags

new argument to provide extra content

introduce render_entity_toolbox on default primary view to display components in the ctxtoolbar context, such as pdf icon, notification registration (nosylist)...

stop calling render_entity_metadata in primary view, provides a contextual compontent instead, displayed by default in the navbottom section.

display entity type in metadata section instead of default title of primary view

PUCE_UP make me thing it will fold something on click, use PUCE_DOWN instead (as for actions box menus)

merge

prepare support for a 'context toolbar', used in tracker but will much probably be backported in default primary view. Turn pdfview component into a toolbar element

missing space between label and value

[web] safety belt to avoid overriding pageid with loadxhtml() HtmlHeaders.define_var() now accepts a third optional 'override' paramater. If set to False, the variable won't be evaluated if it's already defined in the page.

merge

fix necessary when adding a cube which isn't listed in fs dependencies of the instance

more sensible default values to c-c "create" inputs * db name default to instance name * db user default to user's login on 'user' mode * admin account login default to 'admin' note: dirty hack to make default_instance_id method available

[javascript] fid form / onfailure behaviour If onfailure is specified, it should be done _before_ any default / standard CW action is done. The callback signature should be the same as the onsuccess one. If the onfailure callback returns true, the default actions will still take place afterwards, otherwise (i.e. return false), the processing stops directly after the callback.

add set_page_data as well