Introduction
Documentation is simultaneously both one of the most
important parts of any application, and also one of the parts most
developers like doing the least. And while writing documentation is boring
and tedious, maintaining documentation is nothing short of
soul-destroying.
Nowhere is this more evident than with screen-shots. Integrating
screen-shots into documentation enormously enhances the quality of the
documentation, but at the same time taking screen shots is extra work, and
maintaining the screen-shots is often ignored. It is not uncommon to see
documentation with old screen-shots, or in many cases no screen-shots at
all.
Nor is this problem limited to technical documentation. It is well known
that web sites which include screen-shots encourage users far more than
sites which don't. But there again screen shots often lag behind the
actual product. Maintaining screen-shots is a time-consuming and painful
process.
While DrawShot cannot magically make writing documentation a pleasing
experience, it can at least assist in keeping that documentation up to
date, and specifically it can assist by keeping your screen-shots up to
date.
What DrawShot does is create screen-shots of your application as you
navigate through the application. Thus (when DrawShot mode is activated)
one, or more, screen shots are automatically created for you as you visit
the windows in your application. The names of the shots are consistent and
can be included as-is in documentation and web sites.
ClarionLive
ClarionLive
Webinar
#243 introduces DrawShot, shows how it works in a program, and also
shows how to add it to a Program.
Features
DrawShot automatically creates a screen-shot of every
window as you navigate through your application.
If the window contains a SHEET control, with multiple tabs, then multiple
shots of the window will be created. Each shot will display with a
different tab taking the focus.
In addition to the above automatic shots you can create one or more
additional custom shots for each window. Custom shots can contain
annotations where you highlight a control and include a notation, or
reference to the control.
Custom shots and annotations can be defined at runtime thus allowing users
other than the developer to create the definitions for each screen-shot -
ideal for situations where the person responsible for the documentation is
not the person developing the code.
You can create a screen-shot of the procedure at any time and save to a
file by typing a Hot Key. This is Ctrl-S by default, but can be set by the
programmer.
A simple PrintScreen option can be added to windows as a HotKey or as a
button. This allows any user to Print a current window, or more
specifically every tab on the current window. This is especially useful
for Forms where users may want to capture the fields on a current form in
a report format. Naturally as a report the user can then make use of
alternative report destinations, like PDF or Email, if your program has
that facility.
Compatible With
DrawShot ships as source code, and does not include
any Clarion-Specific DLL's. It does make use of the generic DLL's which
ship with Draw to create PNG's but these DLL's are not Clarion version
specific.
| Clarion 7 |
No |
| Clarion 8 |
No |
| Clarion 9 / 9.1 |
Yes |
| Clarion 10 |
Yes |
| Clarion 11 / 11.1 |
Yes |
| Clarion Templates |
Yes |
| ABC Templates |
Yes |
| Local Mode |
Yes |
| DLL Mode |
Yes |
| Multi DLL |
Yes |
Documentation & Support
Documentation for the product is available
here.
Go
here for further support.
Cost
Refund Policy
CapeSoft believes that if you aren't satisfied with
our products, we would like them back - and we will refund you the money.
This allows you to purchase our products with confidence. You can read our
full refund policy
here.
