Split the runtime-adjustment functionality of ImageManager out. In order to preserve backwards compatibility, the complete functionality including runtime-adjustment can be found in ImageManager which now extends BaseImageManager. The bulk of functionality is now in BaseImageManager and anyone who wants an image manager without the RuntimeAdjustment bits (it uses ClientPrefs and thus isn't friendly in server-land) should use that directly.

git-svn-id: svn+ssh://src.earth.threerings.net/nenya/trunk@433 ed5b42cb-e716-0410-a449-f6a68f950b19
This commit is contained in:
Mike Thomas
2008-03-06 18:31:04 +00:00
parent 9c3a7e2904
commit f00ff51a7b
17 changed files with 594 additions and 528 deletions
@@ -35,7 +35,7 @@ import com.threerings.media.Log;
* for some other reason.
*
* <p> These objects are never created directly, but always obtained from
* the {@link ImageManager}.
* the {@link BaseImageManager}.
*/
public class CachedVolatileMirage extends VolatileMirage
{
@@ -44,7 +44,7 @@ public class CachedVolatileMirage extends VolatileMirage
* prepared image.
*/
protected CachedVolatileMirage (
ImageManager imgr, ImageManager.ImageKey source,
BaseImageManager imgr, BaseImageManager.ImageKey source,
Rectangle bounds, Colorization[] zations)
{
super(imgr, bounds);
@@ -96,7 +96,7 @@ public class CachedVolatileMirage extends VolatileMirage
/** The key that identifies the image data used to create our volatile
* image. */
protected ImageManager.ImageKey _source;
protected BaseImageManager.ImageKey _source;
/** Optional colorizations that are applied to our source image when
* creating our mirage. */