Hi, Bill: At 8:23 AM -0300 4/27/06, Bill Briggs wrote: >At 7:14 AM -0400 4/27/06, Batsford, Steve wrote: >>Rick, >> >>My sentiment exactly. >>The popups and all of the available links SOUND cool. But in the real >>world all my content to my end users is in PDF. > > There used to be a product called FrameViewer, and you could view >other people's FrameMaker documents with it. In FV all of the popups >worked. Of course FV died after Adobe took over the product.
FrameViewer was FrameMaker, just crippled to prevent authoring. It was expensive to purchase for just a product that reads and prints FrameMaker files, and it was also expensive in the amount of storage space and machine resources it required in those days. Adobe's not the villain here, IMO. Acrobat's PDF is more versatile for distributing files for reading, commenting, printing, information-collecting, and publishing for more applications beyond FrameMaker. You might say that Windows is a more likely villain, because on unix, FrameMaker's "floating" licensing approach minimized the need to purchase one license per user. Floating licenses could be checked out, used, and checked in, to release them for other users. If 20 simultaneous users are likely to need FrameMaker at any one time, a customer needs to purchase only 20 floating licenses to serve an enterprise of thousands of potential users. There are some similar third-party application-sharing tools that work on Windows across applications; they incur other overhead penalties and impose their own maintenance requirements. ________________ Regards, Peter Gold KnowHow ProServices