Sandbox 1.0 (Almost there)

Since the conclusion of the Sandbox Designs Competition, I’ve been working on making the final changes to Sandbox to get it at 1.0 and out of its nest, so to speak.

If you’ve been watching the Sandbox SVN, you may have noticed two branches now existing: 0.9 and 1.0. Let me explain.

Version 1.0 is designed specifically for WordPress 2.3 and utilizes its native support of tagging. That means additional semantic class names for tags. Additionally, there had been a number of functions that had to do a bit more work since they had to work seamlessly with WordPress 2.0.x, 2.1.x, and 2.2.x. Those have been simplified to be 2.3-specific. All deprecated tags have been dropped, too.

Version 0.9 is exactly the same as 1.0, except it retains some of those exotic functions and works with pretty much any WordPress version (at least 2.0.x and later). It doesn’t have any incorporated native tagging support. This version will remain around so that 2.0.x legacy users will be able to use the Sandbox as well.

For fun I’ve also added the milestone versions from 0.1 to 0.8 in the SVN. These are quite entertaining if you’ve been following the development of the Sandbox for the past 13 months.

Finally, there are some bugs in 1.0. Mostly with tags. As developing for pre-release software is rather difficult, I’ve found.

You thoughts and comments on where the Sandbox stands are welcomed.

Comments

  1. adam wrote:

    it’s amazing how much lighter v1.0 is for not having all those legacy code checks.

    i’m working on a hooks and add_actions patch, that we can kick around. although for 1.0, it feels like overkill.

  2. Scott wrote:

    I was meaning to mention this on Sandbox Discuss. Yes, file a ticket and submit it. I think it’s wise to use this, at least with the 0.9 branch.

    How ’bout those MIME type classes for attachments? I’m quite pleased with those. :)

  3. adam wrote:

    awesome (i hadn’t expanded the functions, so i’d missed them)!

Post a Comment

Your email is never published nor shared. Required fields are marked *

*

*