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.
On Mon, Jan 21, 2013 at 8:10 AM, Chris Despopoulos
<despopoulos_chriss -at- yahoo -dot- com> wrote:
> As the original question points out, the "page" (the web "document", or that which has a specific URL) *contains* the application, but the application has a series of different "screens" within it. When you change screens you don't change the URL (the container), and the browser doesn't store these screen changes in its history. I would say these widgets are whatever the application lexicon calls them... Views, tabs, or even screens. But they are NOT pages, and the *browser* lexicon doesn't apply, IMO.
That probably depends on the architecture of your particular web
application. I've worked on several over the past couple of years,
and for the ones that I can recall, when you changed pages the URL
changed as well. I'm sure there are web apps out there where
everything happens in a single URL but I may not have worked to
document one yet.. So in my past experience, I've always used "page"
not "screen."
As always, YMMV.
--
Julie Stickler http://heratech.wordpress.com/
Blogging about Agile and technical writing
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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