Hi Peter, Hi Shlomo, I beta tested FM8 and I didn't run into the keyboard shortcut bug because my templates are pretty solid and I didn't happen to have the para designer displayed when I used the keyboard shortcuts. Sorry I missed that one, but I sure would have reported it - big time - if I had seen it. I saved a lot of the messages regarding bugs that were found and I don't see one where that bug was reported.
It was a real pain when I discovered the bug after we upgraded to FM8 at work, and I did not know the workaround yet. I use keyboard shortcuts for almost everything, but I've been using FM since it was just a kid and I'm used to them (uh- sort of - they keep changing them - arrgh). Hard to believe that in another year FM'll be old enough to drink. LOL. Happy Holidays. Diane Gaskill -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Peter Gold Sent: Wednesday, December 12, 2007 1:50 PM To: Shlomo Perets Cc: [EMAIL PROTECTED] Subject: Re: Keyboard shortcuts in FM8 (was Re: 8.0.1 patch fixes FM Book toPDF issue) On Dec 12, 2007 2:27 PM, Shlomo Perets <[EMAIL PROTECTED]> wrote: > Adherence to time tables is certainly important, but in this case, it seems > to me that FrameMaker 8.0 -- at least at this stage -- will be associated > more with the ongoing problems and user frustration, rather than with the > release according to schedule. Was it worth it? I have my doubts... > > > Shlomo Perets Hi, Shlomo: It's always embarrassing when this kind of relatively minor but supremely annoying bug slips through into a released product. If the bug was reported during beta testing, but wasn't fixed because resources and development time were devoted more to the major improvements in Unicode, XML, and DITA areas, and less to bugs like this, it's a bad choice to have made, because however small they seem, they do interrupt smooth working habits. For example, when a fast typist applies formats by proven keystroke shortcut sequences, and later finds out they have been ignored, retracing one's steps destroys efficiency as well as trust in one's skills and in the product. If the bugs weren't reported, however, it's possible that the beta-test community of users (experienced users invited to participate, not just in-house Adobe developers and testers) didn't use the shortcuts, and didn't see the problem. Beta testers are encouraged to use the product in their normal workflows, so perhaps only a few users use these shortcuts. As a side issue, it would be discouraging to find out that only a small number of users are aware of and use these efficient shortcuts - when they work, they're very helpful. In the larger view, when something in software breaks when other things are added, it's a sign that the overall architecture of the product is hard to maintain. This has always been an issue with adding features to FrameMaker; it's always been difficult to maintain the architecture, so adding new useful features and abilities has always lagged. IMO, the release of the new Technical Communications Suite is a good place to stop holding on to the old architectures of these suite products, and time for Adobe to begin serious development of new and proven engineering that brings the products into the current generation. Regards, Peter _______________________________ Peter Gold KnowHow ProServices _______________________________________________ _______________________________________________ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
