In a previous article, I described a Concealed Controller Pattern, which allows Java classes to be packaged separately, while maintaining access control to certain sensitive methods. In today’s article, I discuss the shortcomings of Java’s package capabilities and present a simple pattern (the Keyed Access Pattern) for overcoming one case.
I just stopped coding for a moment and realized we were a month into 2009. I thought I’d better let everyone know that I’m still hard at work developing the brand-new old-school (so-far, so-called) Potential RPG.
At the close of 2008, I evaluated and distilled my game design goals. My recent focus has been to solidify and enhance the core capabilities of my (so-far, so-called) Potential Platform, in support of these desired gameplay features. For example, a new map management capability allows maps to be either persistent (such as mainland continents) or instances (such as caves to clear).
I’m looking forward to (the rest of) 2009 and plan to have something fun to offer soon…
