When websites are using another translation gadget we end up with two
translation gadgets loaded (which causes issues)

Otherwise "conflicts" happen when a web site is configured to use
anotehr translation gadget

We can not use the default gadget as ERP5JS for translations, because
web sites with different messages needs to be using a different
translation gadget.

As a first step we stop referencing the default gadget translation on
web site, so that upgrader does not try to update the default
translation data script.

Next step will be to use different translation gadgets on each web site
which uses translation.

This website has different translations from renderjs_runner web site,
so they can not share the same translation gadget

Automate the process of running "Update Translation Data" in
post-upgarde step when the translation data has changed.

This means that translation scripts (such as gadget_translation_data.js
for default ERP5JS gadget) will be updated automatically after each
update and it becomes wrong to have multiple sites using the same
translation gadget for different translations.

If that happens, the upgrader tries to detect a loop and raise an
easy-to-understand error in that case

With officejs web sites, the translation gadget is not referenced
directly on the web site, but in the "app" web section. Teach this
script to look on the web section to know which translation data script
to use

- user no longer have to choose the translation data script, it's
  selected automatically from the translation gadget configured on the
  web site
- add some notes in workflow history for traceability
- rename from "Create Translation Data" to *Update* Translation Data, as
  this script can be called multiple times to update
- rename the dialog and script to comply with naming conventions
- add a header to generated translation data script to explain that this
  is generated and that it should not be edited manually
- generate code passing jslint and typescript

( remove that extra line at end of file )

We were using many different terms every for "username", this is an attempt to use a consistent term every where for login and a few other terms used for logging in and resetting password

See merge request !1164

As a follow up of !1158 , now that stock browser supports inventory conversion, the old converted inventory report is not longer needed.

The reason for removing instead of fixing is that this report was using approaches that have no equivalent in ERP5JS interface (select in the module and run a report based on selection, listbox domain tree), so we could repair it for old ui only, but we thought it would be better to remove it and improve stock browser further.

One reason this was broken is that it was using `SimulationTool.getAllInventory` which does not support brain attributes from `SimulationTool.getInventoryList`, so dynamic attributes like `node_title` were not displayed correctly. This adds a warning on `getAllInventory` docstring. This method has another user so we don't remove it.

See merge request !1162

Make stock browser a dialog where user can select the node category, for compatibility with ERP5JS

Introduce a preference to select the node category by default.

Allow to select quantity unit / metric type in the dialog to get converted inventories.

See merge request nexedi/erp5!1158

Uploaded the content of
https://github.com/nicolaskruchten/pivottable/tree/v2.23.0/dist/
using web dav and ran Alarm_checkSkinCache

This version allow sorting and fixes an XSS vulnerability

Browsers (at least chrome) saves the textarea content and restore it
when going back or resurecting a closed tab, which prevents loosing
unsaved work.
This browser feature does not work in "rich" javascript
editors, but this trick of syncronizing the rich editor content to a
hidden textarea seem to makes it work.

This is an emergency commit to repair failing tests

use "Slideshow" for now. "Slide Show" would also be OK, the discussion
about what's the best term is still ongoing, this is an emergency commit
to repair tests.

We fixed login forms to use consistently "Username", some translation
did not have message for "Username", but only for "user name".
Add missing "Username" messages, with same translation as existing one
for "User name"

with erp5_credential it's a bit more than password reset, because
there's also a feature to recover the username for a given email, but
all this can be named "Recover your Account". That was the term already
used in ERP5JS

Use consistent term as in PreferenceTool_viewChangePasswordDialog. In
dialogs the field label show "what information is in the field" not
"what the user is supposed to do with this field"

Other login related dialogs ( PasswordTool_viewEmailPassword ,
ERP5Site_viewCredentialRecoveryLoginDialog ,
PasswordTool_viewResetPassword ) all use Username.

Login_view/my_reference uses "User Login", but that's maybe OK, because
the context is different and there's also "User Password" on the same
form.

this has been merged in erp5_officejs

This gadget only works in ERP5JS, as it depends on multiple ERP5JS only gadgets.

Some functionnalities have not been backported for now:
* image upload, which seems broken on xhtml style
* test template (I was not able to trigger something from the UI)

Normally, it could be possible to create an OfficeJS app with this editor.

This functionality is enabled only if 'trusted-proxies' configuration
value is ('0.0.0.0',) by putting the following in zope.conf :

trusted-proxy 0.0.0.0

This report have been broken for years and does not work in new UI, now
that stock browser support inventory conversion this report is no longer
needed.

formulator does not seem to like generator for listfield items

getConvertedInventoryList is deprectated and use mergeResults which
does not support brain classes, so the brain.node_title was no longer
correct.
Use a simpler approach, same as Resource_getInventoryList ("stock
browser"), ie: getFutureInventoryList to get all future stocks +
getCurrentInventory and getAvailableInventory for each brain. It's a bit
less efficient because we now do 2 getInventory for each line instead of
3 getInventoryList merged, but that should be enough.

Also:
 - use float fields to format numbers properly
 - activate domain tree for site (instead of showing all nodes)

this 'relative_url | ascending' sort can lead to killer queries and it is of no use

Convert the amounts in inventory list view, the movement history list
views still show in movement unit for simplicity.

At the same time:
 - don't cast to int() in macro, but expect caller to pass already
   correctly formatted values for *_inventory
 - document macro like it was done for erp5_pdm_ui_test

This was never counting movement, but the number of inventory brain that
the getInventoryList should return.
Document this macro and rename argument everywhere.

init macro cannot open the stock browser report, because some other
tests are assuming that this macro remain in view mode and they can
select another view.
move the "select stock browser report" in a stock-browser-test specific
macro

make the node_category dialog pre-select the preferred node category

Previously, these tests were displaying the listbox with two lines, one
for source one for destination and where checking both lines at once.
Now that it's possible to filter by node category (site) in renderjs as
well, adjust the test to select the node categories one by one and check
that the results for each line category is what we expect.

Also fix a few typos

This allows to filter the node by site in new and old interface in
a consistent way.

The domain tree is also removed for consistency (so that we don't have
different features on new and old interface)

Old UI tests have also been updated to use more meaningful macro names.

Having this as a dialog will make it possible for user to supply some
parameters.
In the old UI, this was relying on domain tree to let the user select
the sites they want to see, but in ERP5JS domain trees only work on
list mode listboxes.
Also, we have plans to make this browser more interactive, to let the
user choose more parameters (section category, quantity unit for
conversions etc) in the report dialog, but this was not possible in a
view action.

same as group