<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
mso-believe-normal-left:yes;}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
{mso-style-priority:99;
mso-style-link:"Body Text Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-name:"Normal \(Web\)\,ZimsEmail";
mso-style-priority:99;
mso-style-link:"Normal \(Web\) Char\,ZimsEmail Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Normal \(Web\) Char\,ZimsEmail Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BodyTextChar
{mso-style-name:"Body Text Char";
mso-style-priority:99;
mso-style-link:"Body Text";}
span.NormalWebChar
{mso-style-name:"Normal \(Web\) Char\,ZimsEmail Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.BodyTextChar1
{mso-style-name:"Body Text Char1";
mso-style-priority:99;
mso-style-link:"Body Text";
font-family:"Calibri","sans-serif";}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Courier New";
color:maroon;
font-weight:bold;
font-style:normal;}
span.BalloonTextChar1
{mso-style-name:"Balloon Text Char1";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle26
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><![if mso 9]><style>p.MsoNormal
{margin-left:3.0pt;}
</style><![endif]><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple style='margin-left:3.0pt;margin-top:3.0pt;margin-right:3.0pt;margin-bottom:.75pt'><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I share a lot of Gary's frustrations, although I haven't expressed it as eloquently :-). I also appreciate Alexandra's and Scott's opinions. I am not opposed to the OWL interface, per se, having used it in InDesign, etc. It is the general lack of quality control and consistency that has been disappointing for me. FM 9 was really a dog as far as performance and stability and the interface changed the way important short cuts worked in previous versions. FrameMaker 11 had an undocumented FDK change that caused problems with document display updates in plugins and scripts. Documentation updates have lagged behind in each release. The ExtendScript documentation is sparse and contains inaccurate information. At the same time, users have had to pay premium dollars for each release while Adobe struggles to "get it right".<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>For me, FrameMaker 8 was a solid version. It had unicode support and the "old", simple interface made things fast and efficient for automation. Scripts typically run slower in the newer versions and you have to ignore long periods of a white, "Not Responding" screen.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>InDesign is not perfect for long documents, but the quality and "fit and finish" of the entire InDesign universe is a stark contrast to the FrameMaker world.<o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Rick Quatro<o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Carmen Publishing Inc.<o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>585-366-4017<o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>rick@frameexpert.com<o:p></o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><o:p> </o:p></span></b></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> framers-bounces@lists.frameusers.com [mailto:framers-bounces@lists.frameusers.com] <b>On Behalf Of </b>Zimmerman, Gary<br><b>Sent:</b> Saturday, March 29, 2014 7:08 PM<br><b>To:</b> framers@lists.frameusers.com<br><b>Subject:</b> RE: making stuff unconditional in FM12<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><b><span style='font-size:10.0pt;font-family:"Courier New";color:maroon'><o:p> </o:p></span></b></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I swear it's like the Adobe FrameMaker developers do absolutely NO usability testing, get absolutely NO feedback from existing customers, focus groups, or anything else before they foist on us a crappy, untested GUI that their offshore developers implemented in some kind of cultural vacuum. (Not offshore culture so much as programmer culture - before any programmers get offended, there are plenty of exceptional programmers who have a GREAT sense of usability and customer needs - apparently Adobe hasn't hired any for the FM team, nor any usability/human factors consultants.)<o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>The programming underneath may be great (I doubt it, with the general fragility of the thing for many releases now), but the usability if off-the-charts bad. Like something designed by a bunch of college programmers who have no concept of building a usable product, but instead think "more is better" so they toss in everything figuring that they'll have something for everyone, and end up with such a hash salad that you spend more time jumping through GUI hoops than you do productive writing. (Remember what college kids did when word processors introduce lots of fun fonts to play with - the FM 9 and 10 GUI is pretty much the GUI equivalent of "ransom letter" tech writing.)<o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I can remember when FM was unquestionably a better choice than Word for any serious documentation work. Now they're approaching parity. I don't know about FM8, but when we jumped from 7 to 9, it was all downhill after that. We're on 10 now, debating upgrading. We're also moving to a DITA CMS and Xmetal editor - much less powerful, but it does what it needs to do without being an obstacle to the writers. We didn't even consider using FM as our XML editor, though the transition might have been less of an issue for our writers who are used to FM.<o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Sorry to rant. I LIKE FM. I'm just so sorry they messed with the GUI and messed up so badly with 9 and onwards. They may fix it to be decent again incrementally, but like Windows 8, they should have scrapped the whole thing when they realized what a horrible blunder they made instead of turning a deaf ear and insisting everything was great for so long, when real users knew it wasn't so. Credibility gone. Maybe 11 is better, maybe 12 even better. Don't know if I'll ever get to try them.<o:p></o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal style='margin:0in;margin-bottom:.0001pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>-- garyZ<o:p></o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><p><span style='font-size:10.0pt;font-family:"Segoe UI","sans-serif"'><o:p> </o:p></span></p></div></div></body></html>