Rubygame 2.3: Status Update #2

A quick post before I go to bed.

I've implemented the deprecation warnings for the old Mixer module and its classes, as well as put notices in the documentation with the suggested alternative. It should be a fairly simple process for developers to transition to the new classes.

I've decided to postpone the naming functionality until a later version. It's still a half-baked idea, and I'm still trying to work out the best way to implement it. Plus, it's not really necessary in this release, and I can add it later without any trouble, so that's that. I also want to add it for Surface at the same time. Maybe this will be a "minor feature" for 2.4 (event hooks would be the major feature).

So, what that means is that there is nothing left on my checklist for 2.3! All that is left is to create the branch, update the NEWS file, look things over and make sure things look okay, and then release.

I'm not sure when the release will be. Probably next weekend.


Comments

Ash submitted a comment on #

It’s kind of funny – I actually implemented the #[] named resources for a Surface subclass in one of my projects a long while ago. The only real gotcha is that you will probably need to watch for threading issues.

Congrats on the pending release. Just send me an email whenever you need me to prepare the Windows build.

Have something interesting to add to the discussion? Email your thoughtful comments to comments@rubygame.org.