Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2009-03-22 | Don't make left square braces terminate versions, so we can parse "foo ↵ | Daniel Burrows | 1 | -1/+1 | |
[UNINST]". This doesn't introduce an ambiguity: the left square brace can introduce a dependency whose source was fixed up, but in that case the version number will always be present and the dependency will be separated by whitespace. | |||||
2009-03-22 | Add a special case to render the minimum tier as "minimum". | Daniel Burrows | 1 | -0/+1 | |
2009-03-22 | Support parsing from-dep-source choices. | Daniel Burrows | 1 | -4/+12 | |
2009-03-22 | Adjust how successors are detected, to work reliably (with the new code). | Daniel Burrows | 1 | -24/+7 | |
The "Enqueuing" lines aren't paired with the "Trying" lines they refer to. Rather than fiddle around the edges, I decided to just change the log format to emit a new line when trying a dependency generates a new successor. That means that the search tree that's rendered is now correct. | |||||
2009-03-22 | Support parsing the solutions written by the trace code in my development tree. | Daniel Burrows | 1 | -0/+1 | |
2009-03-22 | Label nodes that don't represent a productive step so it's clear what type ↵ | Daniel Burrows | 1 | -2/+2 | |
they are. | |||||
2009-03-22 | Be more robust when showing the text corresponding to a choice, and show ↵ | Daniel Burrows | 1 | -13/+27 | |
text in more cases. | |||||
2009-03-22 | Get the resolver log visualizer into a halfway working state. | Daniel Burrows | 2 | -105/+205 | |
It more or less works now; probably not worth spending a lot of time tweaking it further. | |||||
2009-03-22 | Get the resolver visualizer more-or-less working. | Daniel Burrows | 3 | -142/+707 | |
It still doesn't display log fragments, but the major problems are more-or-less dealt with. | |||||
2009-03-21 | Display a minimal progress indicator for the load time tester. | Daniel Burrows | 1 | -1/+12 | |
2009-03-21 | Nicely pretty-print choices in the list display. | Daniel Burrows | 1 | -2/+18 | |
2009-03-21 | Don't bother including a condition that you update if the old progress bar ↵ | Daniel Burrows | 1 | -2/+1 | |
fraction is "much smaller" than the new one. | |||||
2009-03-21 | Use widgetShowAll to display the main window, so all its subparts really appear. | Daniel Burrows | 1 | -1/+1 | |
2009-03-21 | Destroy the progress bar window after the file is loaded. | Daniel Burrows | 1 | -0/+1 | |
2009-03-21 | Actually add visible columns to the tree display, and make sure to set the ↵ | Daniel Burrows | 1 | -1/+4 | |
model information after we create its columns. | |||||
2009-03-21 | Add a trivial executable that can be used to see how long it takes to load a ↵ | Daniel Burrows | 2 | -0/+21 | |
log file. | |||||
2009-03-21 | Show the current progress as a percent on the load progress bar, and make ↵ | Daniel Burrows | 1 | -1/+4 | |
the UI more responsive by dispatching *all* events on each iteration. | |||||
2009-03-21 | Fix the logic that decides when to update the progress bar. | Daniel Burrows | 1 | -4/+6 | |
Before, we were updating it on every line. With this change, log files are still slow to load, but they load in a somewhat reasonable amount of time. | |||||
2009-03-21 | Move "while" into a separate utility module. | Daniel Burrows | 2 | -7/+9 | |
2009-03-20 | Finish an initial implementation of code to render the main tree view and ↵ | Daniel Burrows | 5 | -50/+363 | |
add Cabal build files. | |||||
2009-03-16 | Start working on a tool to parse and graphically display dependency resolver ↵ | Daniel Burrows | 6 | -0/+1129 | |
traces. Currently only parsing works; the GUI is built in Glade, but still needs to be hooked up to the parse. We might want to extend the log format so that more details can be parsed out (e.g., information about soft deps is a little sketchy now). Note: the output of the log category aptitude.resolver.search is used as input to this tool, but you probably want to disable the category aptitude.resolver.search.tiers or you'll get a truly HUGE log file (tens of gigabytes when I tested it). |