#107 closed enhancement (rejected)
Improve capabilities for modularization and operator reuse
| Reported by: | gkronber | Owned by: | swagner |
|---|---|---|---|
| Priority: | medium | Milestone: | HeuristicLab 3.3.0 |
| Component: | General | Version: | 3.2 |
| Keywords: | Cc: |
Description
OperatorLibraries are meant as a way to enable modularization and reuse of operators. However currently the capabilities for reuse of operator-trees is limited because OperatorLibraries resemble clipboard more than a library of reusable code.
The main problem is that using an operator from the OperatorLibrary means copying the operator into the executable operator-graph. This leads to 'code-duplication' which means that when (not if!) the original definition of the operator is changed in the OperatorLibrary it also has to be changed in all existing engines that contain a copy of that operator.
Change History (8)
comment:1 Changed 17 years ago by gkronber
- Owner swagner deleted
comment:2 Changed 17 years ago by gkronber
comment:3 Changed 16 years ago by swagner
- Owner set to swagner
comment:4 Changed 16 years ago by swagner
- Milestone changed from 3.1 to 3.2
- Version changed from 3.1 to 3.2
comment:5 Changed 16 years ago by swagner
- Milestone changed from 3.2 to Iteration 0
Milestone 3.2 deleted
comment:6 Changed 14 years ago by swagner
- Resolution set to wontfix
- Status changed from new to closed
This ticket is not relevant anymore, as operator libraries have been removed in HeuristicLab 3.3.
comment:7 Changed 14 years ago by swagner
- Milestone changed from Iteration 4 to Current
Milestone Iteration 4 deleted
comment:11 Changed 14 years ago by swagner
- Milestone changed from Current to HeuristicLab 3.3.0
Milestone Current deleted
For a possible solution see ModularizationAndReuseWithOperatorLibraries