TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I had no shortage of desktop space. As I noted in the Adobe forum, the
problem was a lack of sample code and documentation to show a beginner
how to create a project from scratch. There was documentation of the
UI and advanced docs for programmers, but nothing in between to guide
a new user in creating a project from scratch. If I'd been able to get
my hands on a real-world project, I'm sure I could have figured it out
easily. Maybe FM8 had better samples.
On Sat, Mar 1, 2014 at 12:48 PM, Peter Neilson <neilson -at- windstream -dot- net> wrote:
> Robert, did you use a machine that had two displays or only one? I learned
> it (structured FM8, IIRC) on my own, but there were two displays, so that at
> all times I could see both a full view of the WYSIWYG and also the
> underlying structure. I felt it would have been extremely difficult without
> that kind of view. I feel that being able to see the structure, where it
> shows you, "Oops, you can't do that here," or "Something missing here," is
> crucial.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Doc-To-Help: new website, content widgets, and an output that works on any screen.
