We may differenciate 2 groups of customers Suppliers and Consumers on which kind of products are possible to request on ecommerce interface.

   Sometimes the information comes much later them we expect, this
   prevents false positives and flacky tests

  Several packages has same namespace, this prevents fail if several
  slapos related packages are installed on the same machine.

Indroduce the possibility to request Slaves by respecting software definition ("shared").

tests on this method clouldn't reach updateCausalityState and updateSimulation with the condition portal_activities.countMessage(...) == 1

Change software type can be catastrophic, so the parameter form has to restrict update of parameters in order to not allow user make a mistake.

This change is a complete of the commit f65752c5

When render the form, ensure the "Show Form" button is hide.

Show description and Software Release
Reorganise form order to follow Instance's field disposition

Move description up to make easy to quick view the informations.

Buttons/inputs with type submit conflicts with the implamentation of gadget field, as the event loop is added to all buttons.

Better not include one single form and action of every single preference existing out there for slapos.

Better not include one single form and action of every single preference existing out there for slapos.

Seems not used anyway.

slapos_web: fix user ticked creation, update ticket method use proxy rule "Manager" to let user re-open closed tickets.

Add proxy rules Manager to script Delivery_manageBuildingCalculatingDelivery.
Fix condition which check if activity doesn't exists with this path, check if there is no more than one activity running where method is Delivery_manageBuildingCalculatingDelivery and path is current path.

It was always been ignored.

Because we like good editors.