DmitryBaranovskiy/g.raphael — comment on commit a64f080fa07206021a914f76887c56f25a92129d
File:  line 0
By rzurad:

I see. In that case, then yes this can wait until after 0.5.1. I agree that the API doesn't make much sense (much of the API doesn't make sense) and I want to reconcile that as soon as possible. I'd just rather not reconcile that as part of a 0.0.x release. I want the next release to focus on resolving bugs and documenting first and foremost (as well as several test cases to make sure everything is doing/behaving the way it is "supposed" to be. At this point I'm not sure all of the pull requests I merged into next are going to make it into 0.5.1. They might have to wait until 0.5.5). That way when you upgrade to 0.5.1, it should be [relatively] seamless. Once we completely know all the caveats and the bugs, we can then review the API as a whole and decide what is sane/stupid and how to make it better.

There's a lot of work ahead to make g.raphael stable, extensible, and feature-rich. I just want to make sure there is a solid foundation to work with. The current state of the codebase is not solid by any means, but the entire codebase is not that large, which means a complete review/analysis is quite doable in a reasonable amount of time.