Date: Tue, 28 Sep 2010 11:30:05 -0400
Reply-To: Art@DrKendall.org
Sender: "SPSSX(r) Discussion" <SPSSX-L@LISTSERV.UGA.EDU>
From: Art Kendall <Art@DrKendall.org>
Organization: Social Research Consultants
Subject: Re: more virtues of using syntax: getting and giving remote
help
In-Reply-To: <3DC961479C9E48A19C55847E452AAEFF@yourg2asvv4l2m>
Content-type: text/html; charset=ISO-8859-1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
I always consider a readable set of syntax a target for any SPSS
work. Although using syntax is one of my soapboxes, <b>I am
flexible about how to get that set of syntax. <br>
</b><br>
I use the GUI for some first drafts of syntax both for work, and for
giving help.<br>
<br>
In giving help, I frequently simulate some data that represents my
understanding of the post.<br>
I use the syntax for that, and often use the usually-to-be-avoided
"execute". When the data view looks right, I often then use the
GUI until I get what I <br>
want in the output from a procedure. Then I go back to the GUI and
click <paste>. Sometimes I remove specifications from the
syntax that are defaults.<br>
<br>
<br>
I find it hard to help people on how to use the GUI unless they are
sitting looking at the same screen.<br>
<br>
Art Kendall<br>
Social Research Consultants<br>
<br>
On 9/28/2010 10:56 AM, John F Hall wrote:
<blockquote
cite="mid:3DC961479C9E48A19C55847E452AAEFF@yourg2asvv4l2m"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<meta name="GENERATOR" content="MSHTML 8.00.6001.18939">
<style></style>
<div><font size="2" face="Arial">I only ever use syntax in
preference to GUI. </font></div>
<div> </div>
<div><font size="2" face="Arial">Reasons for this will soon become
clear if you check out the syntax-based SPSS tutorials on my
site.</font></div>
<div> </div>
<div><font size="2" face="Arial">John Hall<br>
<a moz-do-not-send="true" href="mailto:johnfhall@orange.fr">johnfhall@orange.fr</a>
<br>
<a moz-do-not-send="true"
href="http://surveyresearch.weebly.com">http://surveyresearch.weebly.com</a>
<br>
</font></div>
<blockquote style="border-left: 2px solid rgb(0, 0, 0);
padding-left: 5px; padding-right: 0px; margin-left: 5px;
margin-right: 0px;">
<div style="font: 10pt arial;">----- Original Message ----- </div>
<div style="font: 10pt arial; background: none repeat scroll 0%
0% rgb(228, 228, 228);"><b>From:</b> <a
moz-do-not-send="true" title="Art@DrKendall.org"
href="mailto:Art@DrKendall.org">Art Kendall</a> </div>
<div style="font: 10pt arial;"><b>To:</b> <a
moz-do-not-send="true" title="SPSSX-L@LISTSERV.UGA.EDU"
href="mailto:SPSSX-L@LISTSERV.UGA.EDU">SPSSX-L@LISTSERV.UGA.EDU</a>
</div>
<div style="font: 10pt arial;"><b>Sent:</b> Tuesday, September
28, 2010 1:16 PM</div>
<div style="font: 10pt arial;"><b>Subject:</b> more virtues of
using syntax: getting and giving remote help</div>
<div><br>
</div>
<br>
Using syntax makes it a lot easier to get help from others and
for<br>
other to give help.<br>
<br>
Sending syntax (and error messages) makes it possible for others
on the<br>
list to know what you are trying to do and make good guesses
about what<br>
the problem is.<br>
<br>
Also helpers can be explicit about what they are suggesting and
can<br>
often even test the concepts they are suggesting.<br>
<br>
Many people who would help have a single monitor. Putting
instructions<br>
for using the GUI in an email is a very error prone process.
They have<br>
to remember exactly which choices they made in the GUI. Steps
become so<br>
"obvious" that it is easy to omit some. There are not many
conventions<br>
for instructing how to go through the menus. About the only ones
I am<br>
are aware of are: angle brackets to indicate what to click or
choose<br>
from a menu, and "type" to specify what to enter in edit boxes.<br>
<br>
Many people who help do use the GUI to write first drafts but
when they<br>
are satisfied they exit via paste. The syntax pasted into the
syntax<br>
window can then be copied into email and pasted into the
requester's<br>
syntax window. Whereas when an email is a long series of click
<this><br>
and type "that" the requester has to go back and forth from the
email to<br>
the GUI to do what is suggested, another error prone process.<br>
<br>
<br>
Art Kendall<br>
Social Research Consultants<br>
<br>
=====================<br>
To manage your subscription to SPSSX-L, send a message to<br>
<a moz-do-not-send="true"
href="mailto:LISTSERV@LISTSERV.UGA.EDU">LISTSERV@LISTSERV.UGA.EDU</a>
(not to SPSSX-L), with no body text except the<br>
command. To leave the list, send the command<br>
SIGNOFF SPSSX-L<br>
For a list of commands to manage subscriptions, send the command<br>
INFO REFCARD<br>
<br>
</blockquote>
</blockquote>
</body>
</html>
=====================
To manage your subscription to SPSSX-L, send a message to
LISTSERV@LISTSERV.UGA.EDU (not to SPSSX-L), with no body text except the
command. To leave the list, send the command
SIGNOFF SPSSX-L
For a list of commands to manage subscriptions, send the command
INFO REFCARD
| 
