Wow guys; It seems I shouldn’t sleep.
Regarding upgrades:
If you don’t replace the config file, the defaults in the actual code are set to work the same as if you used the new settings in the new config file. At least, that’s the theory. I’ve been adding all of the new config options to the bottom of the file, above the Post Config options, so they’re easy to locate. Bottom line- Just don’t copy over the new config file and you should be OK.
Regarding not finding the Plugin activation page:
WordPress restricts access to this admin tab based on user level. Be sure you are logged in as a user with a high enough level to be able to see this tab before becoming convinced that something is wrong with Exhibit.
Regarding installing GD:
Sorry, when I was using Linux my PHP came packed with working GD and I never cared to learn how to recompile anything. When the time came that I needed to upgrade, I switched to Windows (where I’m personally more comfortable) and everything’s been working swell.
Regarding resampling the original image:
The config file tells you exactly what to do to not resample the originals: “Use 0 if you don’t want to resample.”
Regarding uploading huge images:
Depending on the metering to your server, yes you are sucking up a lot of bandwidth. But it’s your choice to upload the big files as opposed to the small ones. Actually, I resample nearly everything before I toss it online. But for the occasional file, I just want to upload it and be done, so I make use of the online resampler.
Note that you can also zip all of your images and upload them. Exhibit will unzip them into the directory in the file picker. This works if your PHP has the zip extensions.
Regarding bad resampled image quality:
There is an option to turn on antialiasing in GD, but the version of PHP required is too new (5?), I think. I’ll look into it. But if you’re not happy with the quality of the images that are resampled by the server, then the logical course of action is to resample them locally. Exhibit is not Photoshop, and I wouldn’t expect Photoshop performance from it. Resampling locally will save you some bandwidth, too.
Regarding scrollbars in the popup:
There are a couple of ways to do this. You could edit the Exhibit popup code. Around line 267 in exhibit10p.php. Or (perhaps better for upgrades) you could create your own popup page and set the configuration file appropriately. I leave either of these options as an exercise for the user, since I have already written my fair share of popup code here. ??
Regarding watermarks:
I think that applying the watermark to the full image when adding it to a post might be the way to go because it’ll give you the chance to manipulate it a bit before the watermark is applied. I can check the database when the image is added to the post and if it’s not already in the table, the watermark will be applied.
The more I think about it, I think this way might be the way to go. Get your transparent PNGs ready, friends, otherwise all of your images will say “Exhibit” on them!
Removing a watermark can be done if the watermark is applied with an XOR operation. I don’t know if GD (I doubt it) supports such a thing, but now I don’t have to bother looking. ??
At some point, I need to try getting some actual work-work done. Perhaps I will finish up with the watermark stuff today and release 1.1b. Maybe.