Consider that view is the default is wrong, we should invoke call on the object, this change fix listboxes used on frontpage of a website.

See merge request !1115

previous are not installed yet

See merge request !1114

Consider that view is the default is wrong, we should invoke call on the object, this change fix listboxes used on frontpage of a website.

1. can add image
2. add edit, visible workflow

Since cb44242a some Configurator's message changed thus adjust tests.

that is to store the interface from which the message is imported.

Configurator is a tool to install ERP5 / Wendelin thus use more generic title. Fix layout. Fix typos.

so tests can run locally without reporting to an external server

this change follows 0c7a763e

Increase check interval from 5s to 10s (no need of so much checks for a installtion process lasting > 10 minutes).

IntrospectionTool: Move LogMixin here, introduced 11 years ago but never finished nor used elsewhere.

ZODB Components: Migration dialog: Some modules will never be migrated so they should not be displayed.

TargetSolver: Remove Defer and Redirect as registerTargetSolver() has been removed from SimulationTool in 2005 and this has been broken since then.

Use spinner gif to indicate progress instead of progress bar indicator (which is not properly calculating the progress anyway).

this was not working either when testnode does not pass log_directory

the case where --log_directory was not passed was not properly supported

error in the merge

Test nodes already share a folder with a `suite.log` (and a quick and dirty application to view the log live).

The path of this folder is now passed to test runner so that they can also put some log files there. 

ERP5 test runner uses it by writing the `Z2.log` and `zLOG.log` on the running tests there. 

Slapos SR tests also uses it.

See merge request !948

From there we can now access zLOG.log and Z2.log for erp5 and snapshots
from slapos software release tests

Just propagate it as SLAPOS_TEST_LOG_DIRECTORY, then tests (running with
python setup.py test) will be able to use it if they wish.

Each runUnitTest will use a subdirectory in the log directory used by
runTestSuite.

Log files will be created in this directory.

This way, test suite can place some log files in this directory, so that
we can inspect when tests are running.