- Now except for the modify_rank tests test_component didn't fails
- Added simple integer operation capabilities to EmFieldType_integer ( int cast, +=, -=, *=, /=, +, -, *, /, %, ...)

Maybe very bugy

Written some test setup and the begining of the __init__ test

- Added a _fields property (also added it as class property, but the way its done is not satisfactory... we want an ordered dict and not a tuple list as class property)
- Its now allowed to give an uid or a name as em_class for EmFieldGroup.create(name, em_class).
- Now when EmFieldGroup.create is called with an existing name it raises an error (ValueError)
- Removed EmFieldGroup.populate and EmFieldGroup.save

Now an MlString instance is able to say if another MlString instance is equivalent using mlstr1 == mlstr2

Using sqlite db in test_components

EmComponent.create() now takes keywords arguments corresponding to the _fields property of the calling class

WARNING !!! Hardcoded rank = -1 at component creation and Hardcoded 0 as default value for EmClass icon

Correction du bloc de mcommentaire de class encore sous l'ancien modèle.

remplacement des self.id restant par self.uid

Changed id in uid and changed the dummy class for testing

Now EmComponent is populate if it's instanciated with a name or an id

runtest script has now comments inside showing usefull options to run tests

Added tests for newUid, __init__, save and modify_rank

Written test environment init
Written test for newUid and __init__

Pass the value of ranked_in instaed of the column name.

same as precedent

test si new_rank - 1 existe pour signe '='

En cas de signe égale prend désormais en charge une valeur de new_rank superieur ou inferieur a la valeur actuelle.

En plus de modifié la valeur en base, modifie la valeur d'instance.

Prise en compte du nom de la collonne indiqué par ranked_in

Fonction new_rank dans component. Permet la modification d'un rank tout en gardant la collection de component valide.

Ajout de local.py (sans majuscule)

The dates are set in EmComponent::create() for date_create and in EmComponent::save() for date_update
The values are sets to datetime.datetime.utcnow() so we now that EVERY date in the db are in UTC, no matter django, database or even server configurations.
We will have to take care to convert dates from database to django timezone in dates fieldtypes.

The dates are set in EmComponent::create() for date_create and in EmComponent::save() for date_update
The values are sets to datetime.datetime.utcnow() so we now that EVERY date in the db are in UTC, no matter django, database or even server configurations.
We will have to take care to convert dates from database to django timezone in dates fieldtypes.

Conflicts:
	EditorialModel/fieldtypes.py