    <rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/">
     <channel>
        <title>ACCU  :: Members' Experiences</title>
        <link>https://members.accu.org/index.php/articles/982</link>
        <description>Professionalism in Programming</description>
        <dc:language>en-us</dc:language> 
        <dc:creator>Administrator</dc:creator> 
        <admin:generatorAgent rdf:resource="http://www.xaraya.org" /> 
        <admin:errorReportsTo rdf:resource="mailto:webeditor@accu.org" />
       <sy:updatePeriod>hourly</sy:updatePeriod>
       <sy:updateFrequency>1</sy:updateFrequency>
       <docs>http://backend.userland.com/rss</docs>




<div class="xar-mod-head"><span class="xar-mod-title">CVu Journal Vol 12, #2 - Mar 2000</span></div>

<table border="0" cellpadding="1" cellspacing="0">
    <tbody>
    <tr>
        <td valign="top">
            Browse in :
       </td>
       <td valign="top">

                                            <a href="https://members.accu.org/index.php/articles/">All</a>

                     &gt;                         <a href="https://members.accu.org/index.php/articles/c76/">Journals</a>

                     &gt;                         <a href="https://members.accu.org/index.php/articles/c77/">CVu</a>

                     &gt;                         <a href="https://members.accu.org/index.php/articles/c127/">122</a>
<br />
</td>
   </tr>
   </tbody>
</table>




<div class="xar-error">
   <p>
 <strong>Note:</strong> when you create a new publication type,
the articles module will automatically use the templates
<em>user-display-[publicationtype].xt</em>
and <em>user-summary-[publicationtype].xt</em>.
If those templates do not exist when you try to preview or display a new article,
you'll get this warning :-)  Please place your own templates in themes/<em>yourtheme</em>/modules/articles . The templates will get the extension .xt there. </p>
</div>
<div class="xar-norm xar-standard-box-padding">
   <h1><strong>Title:</strong>&nbsp;Members' Experiences</h1>
<p><strong>Author:</strong>&nbsp;</p>
<p>
<strong>Date:</strong> 03 March 2000 13:15:35 +00:00 or Fri, 03 March 2000 13:15:35 +00:00</p>
<p><strong>Summary:</strong>&nbsp;</p>
<p><strong>Body:</strong>&nbsp;<div class="sect1" lang="en">
<div class="titlepage">
<h2><a name="d0e20" id="d0e20"></a></h2>
</div>
<p>Can I remind readers that the purpose of this column is for you
to share your experiences (usually of development software) with
your fellow members. Modern applications are generally too
extensive to review in the traditional fashion. In addition,
experience with a piece of software may illustrate things to
consider when writing applications. It is in the light of that last
element that I am including a (very) brief summary of my
experiences when using (and observing professionals using) Quark
Express.</p>
</div>
<div class="sect1" lang="en">
<div class="titlepage">
<div>
<h2><a name="d0e24" id="d0e24"></a>Using Quark
Express</h2>
</div>
<div>
<h3>From Francis Glassborow</h3>
</div>
</div>
<p>For those of you who are unfamiliar with the product it is one
of the two main DTP packages used by professionals in preparing
text for printing (such as for C Vu and Overload). It is a very
expensive (over &pound;900) product that can maintain that price
because of the degree to which it has its customers locked in. The
typical user of QE is working to tight deadlines which prohibit
taking time out to learn how to use a new product. In addition
different users use distinctly different features to achieve
similar objectives. This means that even in a single company,
adoption of an alternative package would require individual
training for all their QE users.</p>
<p>In simple terms, once you have achieved this level of market
penetration you have little reason to fear competition even if the
competitive product were far superior.</p>
<p>It also means that a major change to the interface would not be
welcome to the users (and would open the door to consideration of
alternatives). The kind of continual change of interface that many
of us endure from the likes of Microsoft simply will not cut it in
this market. However, that does not preclude incremental
improvement and with sensible marketing that would result in an
ongoing revenue stream. OK, enough background.</p>
<p>One task that a production editor has to do is to ensure that
material fits neatly in the available space. Irregular column ends
are not acceptable, articles that spill over to a few lines on a
new page have to be adapted to avoid that. There are many
techniques that a skilled production editor uses to meet these
objectives. Such things as a modicum of hyphenation or fractional
changes in the kerning are used to recover a line from a paragraph.
Increasing the kerning can be used to push a slightly short column
to the desired end. Even in the hands of a skilled editor these
techniques are largely a matter of try it and see. If it does not
work you have to undo and try something else.</p>
<p>So how is it that Quark Express does not support a multilevel
undo? Introducing it would have no impact on those that did not use
it.</p>
<p>On the other hand it would benefit those that did by saving the
odd minute here and there. I can only speculate as to why QE has
this weakness (one of quite a number). Unless you have used a
multilevel undo you might not appreciate its value, indeed you
might not even realise that such a tool existed in other
products.</p>
<p>Think carefully about what this teaches us about all aspects of
commercial product development. Users hate large-scale overhauls of
interfaces. However, they appreciate enhancements that do not
interfere with the basic interface. Keeping a customer base means
providing stability, keeping a revenue flow means adding
enhancements, winning over your rival's customers does not mean
providing them with something completely revolutionary. The true
costs of change (upgrade, cross-grade or whatever) to a
professional is the time it takes to learn the new interface. That
is true even if the product is entirely bug free.</p>
<div class="sect2" lang="en">
<div class="titlepage">
<h3><a name="d0e43" id="d0e43"></a>Addendum</h3>
</div>
<p>I have just finished a conversation with one of our members in
which I raised some of the issues above. He made the very
reasonable point that retrofitting modern features to old software
may be far from easy. Old products may have large amounts of
heavily entangled source code that makes adding features to the
interface difficult. When you have a largely tied customer base a
complete redesign and rewrite of an application may seem less than
attractive. I think this is another reason why careful design that
allows for later enhancement is desirable. If you develop a
successful product you need to consider future revenue streams.
Professional users resent paying for having to relearn the use of a
new release.</p>
<p>They may, indeed should, take a very different attitude if the
learning is incremental because each new release behaves exactly
like the earlier ones with added features.</p>
</div>
</div>
<div class="sect1" lang="en">
<div class="titlepage">
<div>
<h2><a name="d0e50" id="d0e50"></a>Domain Name
Registration-Part 1</h2>
</div>
<div>
<h3>From: Silas S. Brown <tt class=
"email">&lt;<a href=
"mailto:ssb22@cam.ac.uk">ssb22@cam.ac.uk</a>&gt;</tt></h3>
</div>
</div>
<p>Although this is not directly relevant to C programming, I am
sharing it because many readers are interested in having their own
web pages, possibly with their own domain names for business
reasons. Besides looking &quot;professional&quot;, a domain name has the
advantage that you can point it at any ISP or web host, and
therefore survive ISP shutdowns and so forth without having the
inconvenience of changing your URL.</p>
<p>A friend of mine wanted a top-level .net domain name, and I
offered to help organise it in return for sharing the space.
Top-level domains (.com, .net and .org) are controlled by the
InterNIC (www.internic.net) and registered by any ICANN-accredited
registrar. Until recently, the only such registrar was Network
Solutions Inc, and all resellers had to go through them, which
meant that these domains did not come cheap. However, there are now
a number of competing ICANN-accredited registrars, the details of
which are on InterNIC's website.</p>
<p>The only ICANN-accredited registrar within the UK was EasySpace
(www.easyspace.com), and I chose this because its being in the UK
meant I would not have to worry about currency conversion. Domain
registration was &pound;15 a year. I opted for the &quot;registration
only&quot; option, thinking I could then point the domain to any ISP of
my choice, and I made an online purchase. Sure enough,
www.landocel.net became a valid web page within 24 hours, but then
the trouble started.</p>
<p>Going to the URL took me to an EasySpace advertisement, saying
that I should upgrade from registration only to full web hosting,
for lots of extra money. And there was no way of re-directing that
domain name to any other server. What is more, the &quot;whois&quot; database
said that the domain was owned entirely by EasySpace, despite their
promise that I would become the legal owner of the domain name. I
had just paid them to register a domain name for themselves, point
it at their advertisement, and give me no control over it
whatsoever.</p>
<p>I contacted EasySpace support by email, and they wrote me a
vague reply, saying that they could re-direct the domain name for
an administration charge of &pound;25 (!), but even then they
implied that they can only point it at another EasySpace account. I
tried to telephone EasySpace but they have no phone number, either
on their web page or via directory enquiries. So I wrote them a
slightly stronger email, cc-ing it to ICANN registrations.
Meanwhile, my friend is somewhat annoyed that I have lost her
beloved landocel, which has been her artist's pen-name for some 20
years.</p>
<p>This is how things stand as I write this just before the copy
date. I will write the conclusion next time. Meanwhile, be careful
with domain name registration, and don't touch EasySpace with a
barge pole.</p>
<p>(<i><span class="remark">Editor's note: I wonder if Trading
Standards should be contacted on this one</span></i>)</p>
<div class="sect2" lang="en">
<div class="titlepage">
<h3><a name="d0e74" id="d0e74"></a>Last minute
update</h3>
</div>
<p>Two things have happened today. Firstly, support told me that I
CAN point the domain name anywhere, and that I hadn't read their
web pages. I HAD read their web pages, but perhaps I had missed
something (for example, they might have had a link that only
manifested itself to the fully sighted user and somehow escaped my
access gateway); at any rate they told me the procedure for
changing the nameserver and there was no charge. (I have as yet not
tried it.)</p>
<p>Secondly, the &quot;whois&quot; command on my computer (and the
university's Unix systems) turned out to be giving a brief
response, not including the administrative and billing contact. I
am rather suspicious of the local setup for this. When I tried it
with whois from brian, all was well.</p>
<p>I take back my remark about not touching EasySpace with a barge
pole.</p>
</div>
</div>
</p>
<p><strong>Notes:</strong>&nbsp;</p>
<p><em>More fields may be available via dynamicdata ..</em></p>
</div>
</channel>
</rss>
