this will expose default values which are wrongly inputed.

Failover should be render a textarea explaining the error.

This will enable edition of parameter using a JS editor.

Failover should be render a textarea explaining the error.

This will enable edition of parameter using a JS editor.

This is a workarround to use the same version for gadgetfield at slapos website and the gadgets. There is probably a more clever way to do it after.

This is had to be be reviewed in future in order to handle network temporary problems.

- Reorganise the code to be renderjs and gadget field friendly

It was not used anymore.

Instead use portal_sessions and selection, use links on listbox and forms rendered by context. This provides more flexibility on provide links on others locations and sites.

- Code Reorganisation
- More integrations with ERP5 Gadget
- Handle failure smoothly
- Resolve relative URL inside json based on JSON base url.

After the instalation of erp5_web_renderjs_ui a new skin was introduced.

This is a legacy script, it is not required to keep a script only for a single getUid.

- Move Ticket list to myspace, as it is the most usefull communication channel.
- hosting site is used as back end shop (like a cloud manager ui), so we directly show login page.

Simply drop all the parts which are not used anymore for a very long time. It is not usefull to keep it as reference neither (we can use git for that.)

The direct edition of the Software Instance by the user is unwanted and dangerous, this commit only removes already disabled code.

Conflicts:
	master/bt5/slapos_pdm/SkinTemplateItem/portal_skins/slapos_pdm/SoftwareProduct_getSortedSoftwareReleaseList.xml

If user set create_tap to True then specify an interface (tap_gateway_interface) to use as gateway for
guest vm connected to tap interface, slapformat will configure route
to reache each guest from host: "route add -host tap_ip dev slaptapXX",
where tap_ip belong to the same network as the ip on tap_gateway_interface.
slapformat will also create network information for each tap
who will be used to configure network in guest vm.

This is a begining to create cluster of vm which are connected to
each other using tap interface, without bridge.