Re: FrameMaker UI

["Thomas Michanek" <framers@xxxxxxxxx>]

> >Then there's the need to press Command-L to refresh the display. No
> >other app I use needs to refresh its display, they handle all their
> >content without getting "confused".
> 
> There was some discussion about this when Lee 
> Richardson was still on the list, and the upshot was - apparently - 
> that it took too much processor attention to keep it updated. I 
> found, and still find it difficult to swallow that.

I'll be less polite: that was, and still is, complete bullshit.
I still experience the lack of screen refresh in very simple
layouts, on pages with only text, when simply hitting Return.
The text below doesn't move correctly and leaves behind copies
or traces of the text at the previous position. This is *not* a
problem with lack of processing power, at least not within the CPU...

Now, maybe there is a problem with the "core code" of FM that
somehow makes it difficult to address this issue. Fine. But that's
just one more reason to start modernizing the code. Look, Adobe has
had access to the source code for nearly 10 years now, don't you
think someone would have been able to solve this by now? This ain't
a Mars lander we're talking about here, folks.

Adobe needs to team up with Nike. Just Do It. 
Maybe the FM developers in India should strive for a "Just Do It Award",
which often is given to people who just went ahead and did something,
without asking for permission, which had a positive impact on customers.
I have a feeling this doesn't exist at Adobe, though...

Boy, am I in a cranky mood this weekend? ;-)

___________________________________________
Thomas Michanek, FrameMaker/UNIX/MIF expert
Technical Communicator, Linkoping, Sweden
mailto:Thomas.Michanek@xxxxxxxxx
___________________________________________


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