| | 1 | == Main problems == |
| | 2 | |
| | 3 | * Currently when digitizer crashes, the whole GUI also crashes. |
| | 4 | * Caused by the bad handling of the memory by digitizer or...? |
| | 5 | * Requires complete re-design of vector digitizer. |
| | 6 | |
| | 7 | == Requested functionality == |
| | 8 | |
| | 9 | ''Update the list, add links to tickets'' |
| | 10 | |
| | 11 | == Proposal: Use pygrass == |
| | 12 | |
| | 13 | Use pygrass to access vectors. |
| | 14 | |
| | 15 | === Basic usage === |
| | 16 | |
| | 17 | * possibly better and easier memory handling |
| | 18 | * will improve also pygrass |
| | 19 | * avoids code duplication (some interface would be needed for digitizer anyway) |
| | 20 | |
| | 21 | === Solving the crashing in the future === |
| | 22 | |
| | 23 | 1. use pygrass |
| | 24 | 2. use factory design pattern |
| | 25 | * create objects using factory |
| | 26 | * everyone expects the interface provided by pygrass |
| | 27 | 3. create new set of classes with the same interface as pygrass |
| | 28 | * these classes are using modules and not library calls |
| | 29 | * other implementations are also possible |
| | 30 | 4. replace old factory with the new creating new classes |
| | 31 | 5. it is possible to switch between these two ways dynamically |
