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.
KEVIN SAYS:
I
disagree with your use of "screens". I'd say "dialogs" or views or use
some app-specific / plug-in-specific term, according to what is going
on in whatever part of the visual real estate, but not "screens" if I
could help it.
========
Fair enough. No way do I say "Screen" is inherently good. My point is, there's a browser and an application -- Each has its set of terms. In this case, where I believe the original post mentioned that the URL does not change, the thing that changes belongs to the application and not the browser. So use the application terminology. If the application terminology is ugly, that's another question (and maybe cause for a meeting, urgings to the contrary notwithstanding). But for this particular issue I think it's clear, and no need for a meeting. But I do see a need to make a sharp distinction between application and HTML page... Muddling a distinction as fundamental as this ultimately muddles the user.
Am I ranting yet???
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
See what's new in Doc-To-Help 2012 in a free webcast:
Read all about them: http://bit.ly/C1-webcast
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com
