I have a whole bunch of plug-ins in the plug-ins folder which PL shares with Canvas X (most came free, so I just dumped them in, but to be honest, I almost never try them let alone use them I'll dump some of them out after looking t them critically as I have just done!). No doubt we would use Topaz Adjust in different ways which would be interesting, and it would give Gerhardt and Martin and idea of some things they needed to keep an eye on. If 27 of us are using Topaz Adjust, fine, it would be good if 27 said so. Would anyone care to list what works for them? And let's not worry about duplicating listings.

It would be great to have a comprehensive listing of what plug-ins work with PL and what don't, on which platforms, and what the plug-ins do, and what we do with the plug-ins. So plug-ins are good - they can add functionality you want without making for extra cost and bloat for everyone else who don't want that functionality. Building and maintaining the database of hundreds of legacy lenses simply is not something someone can do in their spare time! And it is not something you would want Martin and Gerhard doing instead of developing the core functions of PL. If you go to the PTLens website you'll see the reason why a plug-in like that is a plug-in rather than a native part of programs. One example of this is one I've mentioned on another thread - Kekus's LensFix, and its 'friendly competitor' (they use the same database), PTLens. Only a limited number of users of any given graphics program would use them, so they would not be worth developing for any single program (except something with the 500 kg gorilla market characteristics of P'shop, of course) but they are worth developing for users across many programs. There are simply some things which are quite specialized and it would be stretching program developers unnecessarily to include them. Now, I tend to have pretty limited demand for them but there is no doubt that there is room for plug-ins.

Epaperpress ptlens