Variable UI combolist elements are no more accessed by their (english) value.

They now are accessed by their number in the underlying list.
Their order has been changed to be the lexicograpic one.
Remove a root variable bug in the variable UI.

This root variable was asked for its fathers whereas it has not got one (logically).
Solve the accumulation of fathers.

When a user modified a variable, this variable's fathers were attribute to it twice.
Once when the modification were validated in VariableTreeController.validateChanges.
Once when the modification were applied (this is done by overwriting the variable's father corresponding child) in AbstractNodeVariable.insertChild.

"It's in the mood."
Solve the non-deallocation of unused variables.

When a variable is modified, we overwrite it with a new variable.
It used to be the former (dead) variable that was referenced in a dict that links variable displayed on the treeview to their IDs.
Replace getValue with getTokenValue in ComputedRelationVariable.

ComputedRelationVariable used to find the base value on which they compute their with the getValue function.
But the getValue function is implemented only for variable that have values (DataVariable for instance).
So for node variable, it caused a crash.

getTokenValue returns the subvalue of the final value (in the VariableProcessingToken) a variable is responsible for.
Make the SizeRelationType lies on DecimalWordType.

It used to lie on IntegerType which is not much comfortable and used.
Solve a bug in NodeVariable children initialization.

During construction of a node variable, children were not added properly (with the addChild() function that manages also the fathering of these children).

Remove a small bug in RepeatVariable forRepeatVariable without children.
Activate and enhance the tokenChoppedIndex list.

This list is used to follow which part of the final value is due to which variable. This is very useful in case of ComputedRelationVariable pointing on NodeVariable (that do not have an inherent value on which the computation can be based).

Moreover it ensures that only a written value is taking into account.
Resolve accumulation of ComputedRelationVariable value.

These variable used to see their value auto-increasing each time they were used.
This is solved by reseting the tokenChoppedIndexes for each new write access.
Put the treeview of the variable UI into a scrolledWindow.
Give a default size to the variables UI.
Change the title of the variable UI.

This title shows now the field of which we are modifying variables.
Merge branch 'master' of dev.netzob.org:netzob
IntegerType is sized in bits.

It used to be sized in base 10 integer.
For instance a size of 3 means an integer between 100 and 999.
Now it means an integer between 0 (000 in bits) and 7 (111 in bits).
Add a default normalizeValue() method.

This function is called when a variable has to set its value.
Its makes sure this value is of the good size, and adds padding characters or truncs the value if it is not the case.
Original values of DataVariable are now bitarrays.

They used to be in a DataType-dependent string format. It was not easy to manage, so I decide to transform them into the simplest (and elementary) format used: bitarrays.

Conflicts:
	src/netzob/Common/Field.py
Replace the SizeRelationType with two new types:

I splittes the SizeRelationType into two different types, depending on how their value is written eventually.
- BinaryRelationType: represent the size of a given field into a binary format.
- WordSizeRelationType: represent the size of a field into a string format.

These RelationTypes have been created with a new functionality in mind: implementation of a factor and an offset in their size computation. The final size value worth this now:
Final size = factor * (size in bits) + offset.
This gives users more flexibility on how the size is to be computed.
Implement the two new RelationTypes into the interface.

Thes new types are BinarySizeRelationType and WordSizeRelationType.
Implement the new factor and offset attributes of SizeRelationVariable into the variable UI.
Implement the new factor and offset attributes of SizeRelationType into Project.xsd.

These new attributes need to be saved in projectxml files. For this modification to be allowed, we need to modify the xsd file that rules these xml files.