Quote:
Originally Posted by SoftwareBug2.0
This feature is bad because it would use engineering time that ought to be used to fix real problems.
I think it's fun to add features too but I think there are bigger fish to fry.
|
I agree. It's really frustrating to hear that all these great new features have been added at kickoff (robot simulator, robot builder...), but something really, really basic, like the CPU graph, got messed up, because somebody made a stupid mistake, and decided to change working stuff after the beta test.
I'd rather see development time spent on testing and reviewing code that's going to be released to teams. Like including a driver station log viewer that can actually open driver station log files. Or, a debugger that works over a wireless connection in java. In the past, stupid little bugs like having every other encoder work really hurt teams.
However, the thing that bugs me the most is the documentation page included in netbeans. For new programmers, having a nice place to look is really helpful. On the main documentation page in netbeans, the second line said "This document is a work in progress, more to come by final release", this needs to be removed. Also, none of the three demo projects listed can be opened, and one of the sites linked was last updated in 2010. I had some kids trying to get the v20 cRIO image from 2010. Also, as the previous poster has pointed out, some of the code is just too complicated and poorly implemented to be really useful, like the totally incomplete vision libraries. Before a single new feature should be added, ALL of WPIlib should be documented.