Module CustomFields Dev: Difference between revisions

Jump to navigation Jump to search
Line 977: Line 977:
* AJAX? (but only optional, because else it won't work for mobile phones and tablets)
* AJAX? (but only optional, because else it won't work for mobile phones and tablets)
* Add an AJAX select box for constrained values : when a constrained type is selected and a table is selected, a hidden select box would show up with the list of the fields of this table to choose the values that will be printed as the values for this customfield (eg: for table llx_users you could select the "nom" field and then it would automatically prepend "nom_" to the field's name).
* Add an AJAX select box for constrained values : when a constrained type is selected and a table is selected, a hidden select box would show up with the list of the fields of this table to choose the values that will be printed as the values for this customfield (eg: for table llx_users you could select the "nom" field and then it would automatically prepend "nom_" to the field's name).
* Enhance date picker for date and datetime types by using jquery datepicker.
* Find a way to make constrained subfields (constrained on another custom field on the same object) to work in creation page (it only works in edition page for now because the previous field must be set and registered in db before the next field can fetch its value from the database). Maybe something with AJAX? (but can't autosave using AJAX because at creation we don't yet know the object ID, so we would need to use something like a simple Javascript get value then use AJAX to fetch the values for the subfield...).
* Find a way to make constrained subfields (constrained on another custom field on the same object) to work in creation page (it only works in edition page for now because the previous field must be set and registered in db before the next field can fetch its value from the database). Maybe something with AJAX? (but can't autosave using AJAX because at creation we don't yet know the object ID, so we would need to use something like a simple Javascript get value then use AJAX to fetch the values for the subfield...).
* Fine-grained rights management: rights per group, per user, and per field.
* Fine-grained rights management: rights per group, per user, and per field.
* Replace overloading functions (extend class) by hookmanager if possible (but how to simulate the *full switch? Plus this will force users to make their own modules to make those functions, and to disable/renable their modules everytime they will add a new function...).
* Replace overloading functions (extend class) by hookmanager if possible (but how to simulate the *full switch? Plus this will force users to make their own modules to make those functions, and to disable/renable their modules everytime they will add a new function...).
* Refactor the trigger array: merge it with the modulesarray (along with a new way to specify which customfields trigger action a trigger should correspond, eg: 'linebill_insert'=>'customfields_create'). But the triggers aren't necessarily associated with a specific module...
* Refactor the trigger array: merge it with the modulesarray (along with a new way to specify which customfields trigger action a trigger should correspond, eg: 'linebill_insert'=>'customfields_create'). But the triggers aren't necessarily associated with a specific module...
439

edits

Navigation menu