Job object updated to output a json result noting its schedule. Format should be discussed along with the input format

Earliest Due Date, Earliest Order Date and Number Of Remaining Stations scheduling rules implemented

priority implemented as first scheduling rule. priority is optional argument for entities and schedulingRoute optional argument for Queue. sortEntities() method in Queue does the sorting and it is called every time a Queue receives an Entity

stepNumber attribute added in the JSON notation of the route of the Jobs. This way the route is read correctly no matter what the sequence of steps in the JSON tree is

first working version of routing Jobs. From the trace it seems to work ok. Cleanup to be done. Also there are ways to make this more generic

main script updated in order to read Job data and create the job. Also Jobshop1 topology modified to match new JSON format

because the response content_type from raw.github.com is text/plain.

for json in *json ; do echo $json; cat $json | python -m json.tool > $json.clean ; mv $json.clean $json; done

calculation of the processing time for the machine tranfered in another method (calculateProcessingTime). This method should be overriden for machines that read the calculation time from the Entity attribute

haveToDispose updated so that the caller is passed as an Argument. Now there is not use of the sys._getFrame method in ManPy, that might caue problems in different version. Execution does not seem to get faster

canAccept updated so that it does not require to identify the caller. Now it is passed as an argument