It seems there’s no substitute for using a piece of software in actual production to really surface bugs and usability issues 🙂
This isn’t too surprising to anyone who has been doing software development for any amount of time, but it still amazes me that no matter how comprehensive you think your testing is, there’s always something that slips through~!
See this list of documented issues that I have surfaced from just a day of using the DX_SourceOutliner in actual production code vs. the sample solution that I had been using to test its behavior: http://code.google.com/p/dxsourceoutliner/issues/list
I’m working on these issues this weekend and they should be resolved before Monday. Only the bug listed on the Google Code site is really a blocking issue for adoption (but its a pretty embarrassing one if you ask me!) and the rest are usability enhancements so this doesn’t by any means indicate that you need fear using the tool before the fixes are posted in the next day or so.
Happy coding~!
Hey Steve,
the source outliner is working really well, but 😉 I suspect there is still something wrong with the pattern matching.
“*Click” lists all methods etc. that are ending with “Click”. This is what I expected.
But “*Click*” does list every element without doing any filtering. I expected to see only methods etc. that contain the string “Click” in its name.
Best regards,
Phil
@Phil:
Since I’m using regex under-the-hood, permitting more than a single instance of a ‘*’ wildcard in the filter pattern is a bit complicated (not impossible, just complicated) so I’ve put ‘greater than one wildcard instance in pattern string’ off as a > v1.0 feature for now; the v1.0 release you should have should at least prevent VS from crashing when you enter the ‘*’ in the pattern string more than once.
This feature *will* be coming, but its vNext for now (sorry!).