- It'll be, in near future, based on default Preference_viewHtmlStyle

- Search form now works asynchronous, linked with listbox gadget
UNG main javascript take care of linking it to work

- Inputs and img tags are not self-closed

Fix domain_url param for method unfoldDomain, that now receives string like "domain_url.domain_depth"

- Retrieves document list from user as JSON
- Also returns default/generic javascript used to get/update UNG listbox

Not necessary anymore, since now listbox is paging asynchronously like any other asynchronous gadget

- Implement change state button with javascript dialog
- Add div element to place listbox pagination buttons

- Refactor to apply new way to render ung listbox
- Increase performance by loading some elements only when necessary

Now unfoldDomain receives string like "domain_string.domain_depth", and does not receive 'domain_depth' param anymore
Also disable 'reset' command when rendering

Remove old listbox from main form, and add new one that links listbox from gadget

Add new UNG main listbox, based on an asynchronous gadget

See commit ef5d6d9c

This reverts partially commit 2b92f990
("expand: optimize creation of new movements by not using propertyMap+_edit").

This reverts commit ff04daef.

This was an attempt to optimize simulation.

* BusinessConfiguration_setupUNGWizardBT5 does not need 'Manager' proxy
* BusinessConfiguration_setupUNGPreferences, because it adds a 'Preference Configurator Item', needs a 'Manager' proxy

For now, default 'Text Area' and 'FCK Editor' are available by default, and only check if Xinha Editor is available

This softens dependency to activate more objects even in case of failed
activities. The downside is that 'activity_count' can't be used to limit the
number of processing nodes.

- reduce probability and cost of ConflictError by posting the
  activity result by activity
- do not post None (to force it, it's still possible to forge an
  ActiveResult object containing the None value)
- allow grouped messages to post results (previous implementation was not
  working, and this required to change the API of grouping methods)

More changes should be done so that Activity Tool provides an API to activate
an object using only its path.

It defaults to .01 and must be in the interval ]0, 1]
If a message expands to N objects, then it costs N / group_method_cost
and activity tool stop reserving messages the sum of all costs exceeds 1.

By default, this preserves original behaviour, i.e. MAX_GROUPED_OBJECTS = 100

Value 1 is not rejected to allow generic coding
(ex: activity_kw['group_method_cost'] = 1. / packet_size)

Tester accessors was not generated for acquired properties,
only content accessor was generated.

Extend test to prove the fix.