This chapter discusses some topics of interest to developers working on extending, customizing or maintaining frePPLe.
FrePPLe has 2 main components, and the technical documentation is structured accordingly:
- User interface and scripting, coded in Python for flexibility and agile development.
- Solver engine, coded in C++ for performance.
- Architecture
- Source code repository
- User interface
- Solver engine
- Security
- Unit tests
- buffer_procure_1
- calendar
- callback
- cluster
- constraints_combined_1
- constraints_combined_2
- constraints_leadtime_1
- constraints_material_1
- constraints_material_2
- constraints_material_3
- constraints_material_4
- constraints_resource_1
- constraints_resource_2
- constraints_resource_3
- constraints_resource_4
- constraints_resource_5
- datetime
- deletion
- demand_policy
- flow_alternate_1
- flow_alternate_2
- flow_effective
- forecast_1
- forecast_2
- forecast_3
- forecast_4
- forecast_5
- forecast_6
- jobshop
- load_alternate
- load_effective
- lpsolver_1
- multithreading
- name
- operation_alternate
- operation_available
- operation_effective
- operation_pre_post
- operation_routing
- pegging
- problems
- python_1
- python_2
- python_3
- safety_stock
- sample_module
- scalability_1
- scalability_2
- scalability_3
- setup_1
- setup_2
- skill
- xml
- xml_remote