WiimoteLib Survey Results

  .NET , Wiimote

Once again, a bit thank you to all of you who took the time to respond.  I was amazed to receive 100 responses as quickly as I did.  So here are the results and a few comments.

1. What type of release schedule would you prefer?

Response

Response Percent

Response Count

Frequent, small updates

59.1%

55

Infrequent, large updates (what I have been doing so far)

40.9%

38

 

2. I broke backward compatibility between version 1.1 and 1.2. I'm looking to do it again by cleaning up various things such as:

  • Moving anything with an X/Y coordinate to a Point struct
  • Since there are now 4 IR points all with the same properties (X, Y, MidX, etc.), I'd like to turn an IR itself into a struct, thereby having 4 IR structs in the IRState struct instead of the mish-mash of properties
  • And anything else I haven't thought of or mentioned here...

How important is backward compatibility to you?

Backward compatibility is for chumps...clean it up!

 

I'm indifferent

 

It absolutely, positively must be backward compatible to v1.2

Rating
Average

Response
Count

45.3%
(43)

14.7%
(14)

25.3%
(24)

8.4%
(8)

6.3%
(6)

2.16

95

 

3. I don't use CodePlex for source control so it is never an active repository of the "work in progress". It is only updated at release with the same source that's provided in the .zip file. As long as I provide full source with every release, do you care about having the source code in the CodePlex source control server in addition to the .zip'ped source?

Response

Response Percent

Response Count

Yes

46.9%

46

No

53.1%

52

 

As for write in comments, I had quite a few people ask for multiple Wiimote support.  It's coming.  And my favorite comment from the 31 write-ins:  "poop".

So what does it all mean?

I guess it means that:

  • I'll try to start doing more frequent updates with less changes.
  • Backward compatibility apparently is for chumps and I'll definitely be cleaning up some of the ugliness in the code.
  • While not a victor, it's important enough to a lot of people that I'll continue to wedge source code into CodePlex with each new release.

I'm working on a few new features with the library and hopefully will have a version 1.3 up soon.  Stay tuned...