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.
Subject:RE: The Never Ending Saga: Screenshots From:"Richard Smith" <Richard -dot- Smith -at- windriver -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 7 Jun 2001 11:16:57 -0700
I'll share what little I know (or think I know).
> Doesn't software creation require
> the design of the various
> screens outside the executable?
I suppose that all aspects of software design should happen outside the
executable, requirements, design specs, functional specs, use cases, etc.
But that does not mean what's in the design spec will be a valid substitute
for what the UI eventually becomes. Things can and do change.
> Don't the various development
> packages create and save the various
> screens, forms, and menus in some fashion?
This varies highly by what you code your UI in. For instance, in Java there
are Swing (JFC) classes, and AWT classes that are standard window elements
like buttons, containers, scroll bars, title bars, etc. that are all called
by API in your code (I'd guess MFC works along the same lines). So while
some graphical elements can be constructed and viewed alone, often the UI is
a collection of elements that don't really exist in one place as a whole.
Just a bunch of little pieces that don't have the right names or values
until they are called by your specific code.
At the other extreme, something might have a simple web-based management
screen (UI) where it's graphical layout can be laid out in one place.
As a side note, I never put screenshots in until code freeze. I learned that
one the hard way.
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
Sponsored by Cub Lea, specialist in low-cost outsourced development
and documentation. Overload and time-sensitive jobs at exceptional
rates. Unique free gifts for all visitors to http://www.cublea.com
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
