Welcome to the MacNN Forums.

mainframe.ai · Mar 23, 2004, 11:30 AM

Adobe has obviously eol'ed FrameMaker for the Macintosh�

Another app (while not that major) leaving the arena� (Hopefully they will iintergrate the features into InDesign or something� )
Used to do some FrameMaker stuff at the University, but never had to work with it� though it was a fine program�

bye bye FrameMaker�

I would have liked to know you better (on MacOSX).

BTW: Is there any good and luxurious Footnote/Endnote Plugin for Indesign CS?

Cheers,

Mainframe

Maflynn · Mar 23, 2004, 11:58 AM

Originally posted by mainframe.ai:
Adobe has obviously eol'ed FrameMaker for the Macintosh�

What is eol'ed and why would that cause you to drop it?

mainframe.ai · Mar 23, 2004, 12:04 PM

FrameMaker is stopped on Mac.

And I just found it sad� as FM has some very good features, especially when you are into working with bigger documents�
That's all�
Since it hasn't been on the news here�_I thought I might as well drop the news here�

regards,
Mainframe

veryniceguy2002 · Mar 24, 2004, 06:33 AM

Originally posted by mainframe.ai:
FrameMaker is stopped on Mac.

And I just found it sad� as FM has some very good features, especially when you are into working with bigger documents�
That's all�
Since it hasn't been on the news here�_I thought I might as well drop the news here�

regards,
Mainframe

Yes, it is very sad indeed

I love FrameMaker for book building (especially if the book has multiple list of TOC, annex etc).

The paragraph style features is light years ahead of Microcrap Word

So sad... I doubt InDesign will ever do what FrameMaker can do (it's an application target to different usersbase).

Millennium · Mar 24, 2004, 07:36 AM

Originally posted by Maflynn:
What is eol'ed and why would that cause you to drop it?

EOL = End-Of-Life. In other words, they have stopped developing it.

No version of FrameMaker was ever produced for OSX. A number of people have been sticking to OS9 in anticipation of an OSX release; this same thing also happened for Quark. Now that we know there will never be an OSX release, most FrameMaker/Mac users will either switch to another platform (to keep running FrameMaker) or to another program (to keep running Macs).

Keeping the Solaris release while dropping the Mac, though, is an insult. Are they trying to say that their Solaris market was more profitable than their Mac market? Even if it was, can that be blamed on anyone but Adobe itself, given how badly they dragged their feet development-wise?

mitchell_pgh · Mar 24, 2004, 08:52 AM

Originally posted by Millennium:
EOL = End-Of-Life. In other words, they have stopped developing it.

No version of FrameMaker was ever produced for OSX. A number of people have been sticking to OS9 in anticipation of an OSX release; this same thing also happened for Quark. Now that we know there will never be an OSX release, most FrameMaker/Mac users will either switch to another platform (to keep running FrameMaker) or to another program (to keep running Macs).

Keeping the Solaris release while dropping the Mac, though, is an insult. Are they trying to say that their Solaris market was more profitable than their Mac market? Even if it was, can that be blamed on anyone but Adobe itself, given how badly they dragged their feet development-wise?

While I would say it's an insult to drop the Mac and keep Solaris, looking at it from a technical standpoint, it does make sense.

To upgrade the code base of the Solaris version wouldn't be that difficult as Solaris hasn't changed that much over the past few releases. The jump from OS 9 to OS X is considerably more difficult.

Would you rather release a poor quality application on OS X and deal with all the bad press or simply kill it for the platform.

hmurchison2001 · Mar 24, 2004, 08:54 AM

I think Adobe will eventually take the features and meld them into Indesign or something. Why maintain two codebases when you can handle everything with one.

mitchell_pgh · Mar 24, 2004, 09:06 AM

Originally posted by hmurchison2001:
I think Adobe will eventually take the features and meld them into Indesign or something. Why maintain two codebases when you can handle everything with one.

And... it will be another way to increase the price of InDesign (which is considerably more popular... AKA, making more money then the original application)

cowerd · Mar 24, 2004, 11:28 AM

I think Adobe will eventually take the features and meld them into Indesign or something.

And people who use Frame who only buy it if:
InDesign suddenly speed up by a factor of 10-20x. Frame in Classic is faster than Word for long documents and UI responsiveness. Its also more stable than both Word and InDesign.

Realistically, there is no way Adobe can merge even half the functionality of Frame into InDesign.