Aren't we getting a little ahead of ourselves?

["Abbas Zaidi" <abuzz@xxxxxxxxxxx>]

Subject addressed at the end.  (aka revealing true colors.)  Re: 
>
Ah, but that just proves that you aren't a _true_believer_ committed
unalterably to the idea that Microsoft is _eeeeevil_. Therefore, you've
discredited yourself. 
;-) 
>
Hey, last I checked, this was supposed to be a Framers list, and free too..
Or are we too human to recognize that we are _not_ free of our prefered
platform / environment of choice..  *grin*

Re: WinFrame, I have shared the same experience..  Frame 5.5.x - 7.x on a
firewalled (www.zonelabs.com > ZoneAlarm Free) Win 2000 Pro or Windows XP /
Pro system works sufficiently.  (Firewall only essential for purposes of
safeguarding sanity.)  Of course, if I could have my way, I'd stick with
OSX, even though Frame runs in classic.  But if I were to do that, as Steve
well said, I'd be missing Mif2Go, and I can't consider that now that I am in
the know.  In fact, I can't even imagine FrameMaking (and non-WebWorking)
life without this nifty extension/tool/godsend that's so amazingly simple to
use that it boggles the mind..  Apple could benefit by licencing the code
and re-writing it on Cobra, and dispensing with the WebWorking formality
altogether.. (but then again, here I go speaking _my_ preference..) 

I still find this conversation to be a little pre-emptive though.  After
all, Adobe's CEO supported the MacTel launch and praised it as a good move.
We shouldn't discount the possibility of Adobe, in its desire to live up to
an enthusiastic acceptance of Apple's direction, posibly porting FrameMaker
to OSX..  It is, after all, the OS of the future, the one destined to rule
every desktop, to the glee of every boxed-in grandma and the sad dismay of
windoZe (along with the utterly astonished MIF2Go crowd...?)

Oh no!!  I gotta lobby to get non-Win mif2Go rights/code released into the
Open Source community so that Mac (not to mention *nix) versions can be
developed..    

Abbas
____________________________________________
"OWNING WINTEL IS TOO D***ED EXPENSIVE for 
anyone who cares one whit about their money 
or their profits." 
http://www.securityawareness.blogspot.com
____________________________________________
-----Original Message-----
From: owner-framers@xxxxxxxxx [mailto:owner-framers@xxxxxxxxx] On Behalf Of
steve@xxxxxxxxxxxxxxxxxxxxxxxxxx
Sent: Tuesday, July 19, 2005 2:30 PM
To: framers@xxxxxxxxx
Subject: Re: Adobe Certified Newsletter -- notice about FrameMaker

I've watched discussions of this topic for a long time, and never chimed in.
I figure I'd better say something now, in case the subject never comes up
again.

I started using Frame on a Mac in 1997. I found it worked worked very well.
At the request of management at the time, the writing group I was in decided
to go to Frame on Windows 95. That was an adjustment, but not a difficult
one. There were a few things I missed from the Mac, but not many. I
re-mapped some keyboard shortcuts to compensate for some of the changes.
File management and stability on Windows 95 were the biggest issues.

Once Windows 2000 came along, I found that file management and stability on
Windows were quite good. In my opinion, using Frame on my Mac vs. using
Frame on my Windows 2000 box was a wash. I could do either without missing a
beat.

Windows did provide some additional options not available on Mac, like
MIF2Go, more configurability, and the ability to handle the thousands of
HTML files we now generate from our Frame source. The current Mac version
couldn't offer those things.

As an FDK developer, I still develop for both the Windows and Mac versions.
I think the low single-digit market share for Mac seems like a good guess.
Based on my sales figures, there never were too many Mac Frame users. (At
least not too many who were will to buy FDK plug-ins.) If I didn't still use
the Mac version of Frame myself, and have the sunk cost of hardware, the
Frame software, and a compiler, I wouldn't spend the money or effort to make
the Frame plug-ins for the Mac. But, since I have
those things, I'll continue to do so.   :-)

My advice, for what it's worth, is don't rule out Frame on Windows without
first giving it a serious look. I wasn't thrilled with giving up my Mac for
daily work, but the move wasn't nearly as difficult as I expected.

Steve
steve@xxxxxxxxxxxxxxxxxxxxxxxxxx
http://www.SiliconPrairieSoftware.com



** To unsubscribe, send a message to majordomo@xxxxxxxxx **
** with "unsubscribe framers" (no quotes) in the body.   **


** To unsubscribe, send a message to majordomo@xxxxxxxxx **
** with "unsubscribe framers" (no quotes) in the body.   **