I'll take another look at your plugin code, but what modules currently handle the image processing?
If I were you I'd concentrate on the image manipulation part. Create a proof of concept implementation which does merge images, or put some text on top of an image.
Once you've achieved that, it would probably be easiest to make it part of the Bandcamp plugin. Around line 145 in Plugin.pm there's the ImageProxy. This handler would receive the original image's URL plus the target size. You'd have to add your code in there to manipulate and resize it.
And I know I've seen it referenced, but how is logging controlled/enabled?
All you need is a folder with your plugin's name, in there a Plugin.pm inheriting from Slim::Plugin::Base, and an install.xml with a unique UUID. The plugin code only needs initPlugin. That's the entry point. All the rest is optional: strings.txt is used for localization, Slim::Plugin::OPMLBased would be an advanced base class providing additional entry points for menus. But just for the POC image merging you don't need this.
But that's probably stuff for the dev's forum. -- Michael _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
