Yep Mac, P3dO is CBuilder based but you can say goodbye to the Borland .dlls they will be removed with next release. Should I do it again I wouldn't choose CBuilder. That's why all plugins are Visual C++ made and most of the P3dO code is C Ansi - I now avoid greedy Borland classes. P3dO is slowly but steadily moving to Win32. I've heard about CodeWarrior and even tried another portable library called QT - definitely QT won't make it. No portable library can be as close to the OS as a native one is to Windows. The choice is : have a portable library and be slow and flickerfull or have a nice designed layout. I intend to study CodeWarrior - it has a great reputation - but I haven't enough time. I spent one hour every morning studying new solutions, fortunately this is also part of my job. P3dO is more and more fast because I remove the Borland stuff, and improve myself too ;) The tree view is not good but I've a lot of work to plug a new one. I often make trials from a relase to another and remove the new stuff if it is not better. That's why P3dO 1.5.5 went just one month after 1.5.4 : the tree view was a failure. Those trials cost a lot of time (more than 6 months of work last year). I did the Rsr/Png stuff alone, MartinC gave me some help in the end to validate the solution - and he found some bugs of course - but I did P3dO without any CL support. e-on software helped me for the Vue 4 decoding, and eovia is helping me for the coming Carrara plugin. XnView is impressive with 300+ pictures formats and is ahead but P3dO is not really an image viewer although better than many of them - just trying to grasp a little this side and I will of course ;)

Yarp - author of P3DO Organizer for Poser