Quote:
Originally Posted by taichichuan
I get the goal of the WPILib. Try to make it easier for teams to be successful at getting something on the field. That's a laudable goal and for the most part, between Labview and/or the WPILib, it sort of works. There's a lot that could be made less obtuse, but I get it.
|
That is a major goal, but we don't want it to be obtuse... and I don't believe those two must be mutually exclusive. If you have ideas for ways to make it better, please suggest them. Better yet, create patches that demonstrate what you have in mind and it'll be more likely to change for the better.
Quote:
Originally Posted by taichichuan
What I'm looking for is a way to be able to test and develop code in absence of a cRIO. Something that a school or even an individual can afford more than one or two (or three) of. Even with those teams with 3 cRIOs, one is on last-year's robot. One is on this year's robot for driver training and mechanics checkout and then the last one is scavenged for parts or so hard to schedule time on that the software developers are hard pressed to gain access.
|
I can appreciate that.
Quote:
Originally Posted by taichichuan
I feel that what FIRST has put together with the software system certainly hits a significant goal of allowing a team with minimal software background field a robot. I just want to take those ideas a little further, make them more accessible, less magic and help us grow some talented software engineers.
|
I look forward to some specific suggestions for improvements. The
WPILib tracker is open for business!
-Joe