David RENÉ / hayamiki_lib

…by update. The behavior of update is to create a row if not exist or update it if exists. But this behavior introduce a bug I didn't notice until now. By calling only update_row function the trigger belonging to create function are never applied. So the core was updated to distinguish the creation or update and then apply the correct trigger.

…t the DB_id other than the first "id"

…e these types are to big. The good solution is to have a diff function on these type to show the difference

…rent type anymore because it was useless.

… the database. This is useful because the name is predictable and the CKEDITOR can be destroyed easily

move css file in the new path (hayamiki/css/ or hayamiki/js/)

load_vtm and load_latest_vtm call arguments changed.
Now we must provide the name of application and the path where to search the vtm file.
the filename format of the vtm file are also changed.
Now the vtm file name must follow the following rule:
AAAA_vtm_vVVVV.adm
where :
AAAA = name of the application
VVVV = version of database

as example for application named "my_app" with version "1.2.0.0" the vtm file name must be "my_app_vtm_v1.2.0.0.adm"

[+] add upload and download action

[+] get hidden to add in form as value. if there is web arg with name starting with "hidden_", the name after "hidden_" will be add as hidden value in form. This allow to add necessaries values which are not especially exposed as editable but mandatory in database record. For example if there is database record editable by user and that user is not allowed to change or set some important information reserved to company's staff.

…ser is only allowed to select entry in selector

add init_value in ajax combo init

add helper for column, column_label, label and table