🚀 go-pugleaf

I (and 1 other guinea pig in my group) currently use FM in Classic under OS X. Having FM Carbonized is the one thing that would get me to buy the upgrades.  

Running Classic is not as bad as it sounds in this thread. The integration between Classic & OS X is _nearly_ seamless. Frankly, I am impressed at the level of integration Apple achieved with this. Classic does not need to be on another partition or drive, though it can be. You don't so much boot into it as it (OS9) is just another application, essentially an emulation layer. Within this app (Classic) you run other, older applications. To switch back & forth all you do is click on or CMD-Tab to another folder window or icon. The same as switching between any app. I run PhotoShop 7, so it is X-native. When I open a PS image from Frame, the image simply opens in PhotoShop. Seamless.  

You can copy & paste between X & Classic apps. Drag & Drop does not work in all cases. Some Classic apps that do not use Navigation Services have issues with connecting to servers if you are using SMB instead of AppleTalk. Classic really is well done. 

Why would I buy the upgrade though, "just for an X-native version"? Despite the integration and elegant execution, I don't like working in Classic. It is a resource hog and if it crashes, all Classic apps crash. There are graphic glitches and it is a bit slower than running natively in 9. Not having full interoperability between the apps and the graphics glitches bugs the hell outta me. Would I stop using X and go back to 9? Not a chance.  

Running in OS X is a real pleasure. Fast, powerful, fluid, and reliable and intuitive. It is a real treat and when FrameMaker comes to OS X I will never have to boot into Classic again. FM is the only Classic app I use.