[root]/src/seg/jUCMNav/model/util/modelexplore
queries
(7 files, 1050 lines)
scenarioTraversal
(6 files, 1819 lines)

| Author | Changes | Lines of Code | Lines per Change |
|---|---|---|---|
| Totals | 45 (100.0%) | 554 (100.0%) | 12.3 |
| jpdaigle | 18 (40.0%) | 308 (55.6%) | 17.1 |
| jkealey | 23 (51.1%) | 153 (27.6%) | 6.6 |
| etremblay | 4 (8.9%) | 93 (16.8%) | 23.2 |
no bug: formatting cleanup with our default formatting template.
11 lines of code changed in 6 files:
bug 518: refactoring
5 lines of code changed in 1 file:
various issues found by findbugs
3 lines of code changed in 1 file:
MSC: improved message passing.
8 lines of code changed in 2 files:
bug 454: quick hack prototype traversal algorithm
9 lines of code changed in 2 files:
cleaned/commented everything under seg.jUCMNav.model except the commands
101 lines of code changed in 7 files:
bug 320 - loops; to investigate: given this preliminary version, what is okay, what is not. I think it looks pretty good but I haven't tested everything thoroughly. I know that it is too restrictive concerning paths that have a stub that should be considered to contain a start/end point, but for simplicity's sake, I think the workarounds are sufficient.
8 lines of code changed in 2 files:
bug 320 - reimplemented the connection router. the new version uses JP's query framework and is a listener to model objects. is also a step forward for the implementation of nicer and joins/forks. furthermore, in my only test, this new implementation makes the command tests run 39% faster.
8 lines of code changed in 2 files:
JP: Bug 263 progress - mega huge commit of doom!
Implemented querying for reachable nodes, reachable startpoints, and endpoints, etc.
Fixed illegal creation of loops when dragging start or end points to a NodeConnection.
Contextual actions and dragging to a PathNode can still introduce loops and aren't fixed yet.
69 lines of code changed in 7 files:
Internationalization of all the strings.
93 lines of code changed in 4 files:
More query infrastructure work. Query chaining doesn't need so much flexibility and may be deemed unnecessary and removed in a subsequent commit.
48 lines of code changed in 4 files:
JP: Started laying down the structure for a query processing framework.
Intent: process queries about the model / explore graphs / etc.
DO NOT USE RIGHT NOW - Public interface will change - I drank almost an entire
bottle of Beaujolais so I'm drunk. Restating: PUBLIC INTERFACE WILL CHANGE - wait for
jpdaigle to declare interface stable before modifying or referencing.
191 lines of code changed in 7 files: