- 10 Dec, 2020 40 commits
-
-
Jérome Perrin authored
not used
-
Jérome Perrin authored
-
Jérome Perrin authored
The portal type name is ERP5 Scalability Distribut*or*
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
this was changed in 6560ac6d (erp5_code_mirror: Update to 3.22., 2014-07-23) probably by accident
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
"External Web Page" does not exist and this form is not referenced
-
Jérome Perrin authored
This is required to be able to name forms SmartAssistant_viewSomething
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
and also add a field in left group
-
Jérome Perrin authored
required to be able to name forms SpreadsheetConfiguratorItem_view
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
this is a view for a portal type existing in erp5_budget
-
Jérome Perrin authored
there is no "Method", but there is a property sheet "CatalogFilter"
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
Solver Type only exists in erp5_simulation it does not make sense to have forms for solver types in base.
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
This was no longer used and replaced by Entity_addEventDialog since fbd062eb (Allow creation of events from any document, 2011-02-25)
-
Jérome Perrin authored
The spec says "see _getTypeBaseMethod" and _getTypeBaseMethod walks the portal type class mro, which contain property sheets.
-
Jérome Perrin authored
Probably we should be using interfaces instead, let's do this simple way first and we'll improve later.
-
Jérome Perrin authored
For most of theses, we can not change without risking to break compatibility. Some of them are misnamed legacy fields library or some forms that still needs to be updated to use field libraries.
-