rotary dial subclass? #18
Description
It might be best to break the knob control into two classes and make the rotary dialer a subclass of the knob control. This would clean up a lot of code. A rotary dialer isn't really a knob, and things like dialNumber: don't really belong in the knob control.
But as an app developer, I like solutions that come in a single code unit, with one .h and one .m file. It's really simple to grab something from GitHub and pop it into a project that way. Hence, I'm reluctant to build a lot of smaller code units and force the use of a framework.
However, I am going to be releasing some other open-source iOS components soon, and the iOS Knob Control will certainly at least be friends with that code base and probably join the family before too long. That project will definitely be a framework with multiple components, and the knob and rotary dial controls would make a nice fit.
This public repo will not go away any time soon, but it's likely over the coming months that this control will be deprecated in favor of the new project.