 |
| Volume 2 Issue 5 October 1997 |
Features
Interviews
Reviews |
 |
| HTINews
Article - Oct97 - [HTI Home Page] |
HomeTech Hot Products Continuously Updated [Click Message To Learn More] |
CEBus Development Tools
|
Early artisans made their own tools because they didn't have
the choice; Home Depot didn't carry flint axe heads back then.
They stopped doing this for one or several of the following
reasons: - they didn't like making tools - they weren't as good
at making tools as they were at using them - they didn't have the
time - someone made a better tool than them - someone invented a
useful tool that they had never even imagined - someone made a
tool that allowed them to work in a more efficient and / or safer
manner.
Early programmers followed a similar path. They may have started
pushing panel switches on an Altair or programming in machine
language. They then started programming in assembler followed by
higher level languages such as Fortran, Basic, and C. Drawing a
simple window required thousands of lines of code until visual
languages such as Visual Basic, Delphi etc. appeared. Other
programmers worked with 4GLs programming tools or application
languages such as dBase or Excel. In other words, programmers
shaped the tools that in turn shaped their programming efforts.
Programmers who program commercially have to choose the right
tool for a variety of reasons. Market pressures mean that
time-to-market is getting shorter and shorter. Most products have
to conform to OS guidelines (i.e. Windows). Many programs are
required to produce or use data conforming to standards (dbf,
graphics formats, etc.). Other products must be in conformance
with protocols in areas such as communication networks. Some
products such as plug-ins have to interoperate with other
products. Many products have to use of proprietary languages such
as PostScript or control languages such as CAL ( the CEBus Common
Application Language).
Choosing the right programming tool is even more important now
because all the above factors are changing continually.
Developers for popular OS' such as Windows know all about the
moving target that these systems present. In a consumer market,
conformity to a standard is necessary. Availability of the right
tools at the right price can change a market. It is clear that
one of the reasons for Microsoft's dominance is their decision to
supply quickly all the tools necessary for developers on the
Wintel platform.
The tools market has different categories: - general development
tools (Delphi, CodeWarrior) - tools focused at specific market
niches (CEBox, Photoshop) - one trick ponies (morphing tools,
network analyzers)
There are other, less visible, examples of programming tools such
as compilers for microcontrollers, tools for developing
semiconductors such as those made by EDA companies like Cadence
Design, and special purpose tools such as debuggers.
Developers of microcontroller-based products were until recently
the last remaining bastion of roll-your-own tools. In many cases,
there was no choice. Specific needs related to code size,
reliability, cost or speed made it worthwhile for programmers to
develop their own development tools or at least customized
libraries. More and more however there is a trend to use
commercial tools.
Early adopters who have made their own tools often find it
difficult to switch to commercial tools because they have a lot
of time invested in their tools. Their tool could very well be
optimized for a specific factor, such as speed, which they feel
gives them a competitive advantage. Switching tools is not easy,
as it will certainly cause at least a momentary blip in
productivity. Even when they want to switch, it may mean that
they may have to convince someone that someone else made a better
tool than them, i.e they made a mistake. They may also like
making tools and their job will change once a commercial product
is purchased. On the other hand, they may not realize that they
will rapidly be left behind if they don't switch.
Once a programmer has decided to switch tools, the next step is
to convince the higher-ups to buy it. Many managers mistakenly
treat engineers' salaries as a sunk cost, i.e one that they
assume with few questions asked. Tools are viewed solely as an
extra cost instead of a means to enhance productivity. In
addition, a project can be thrown off schedule if the programmer
who developed the company specific tool leaves. Commercial tools
generally offer good documentation, conformity to standards,
access to training and support , better interface to debugging
tools and speedier release of upgrades . All things considered,
it is should easy to make a valid case for moving to a commercial
tool.
Generally speaking, a market can't take off until developers have
access to standard tools. Presently the CEBus Standard and
HomePnP market is getting ready for an explosion of demand. Time
to market will become essential for developers who don't want to
be left behind. Developers have to allocate their resources to
features that truly differentiate them from their competitors.
This means that they should spend as little time possible on
tools development and standards compliance and more time on
actual product development .
Domosys Corporation offers tools and services for CEBus Standard
and HomePnP compliant product developers. Our CEBox software
system is presently the only commercially available tool that
supports the 0.91 HomePnP standard. As the Home PnP Specification
evolves, we will continue to support it. CEBox supports the 8051
and 68HC11 micro-controllers and switching from to one to another
just involves recompiling. Domosys is presently working on
support for other microcontrollers and microprocessors and can
develop libraries on a contract basis if a company has special
needs. CEBox supports the CEWay PL-One and PL-III transceivers as
well as the P400 and P300. Support will be added for other
CEBus-compliant transceivers as they are introduced to the
market. CEBox will continue to be the most complete, compliant
and compatible CEBus Standard and Home PnP compliant tool in the
business. The Domosys commitment to offer superior technical
support begins the first day the product is purchased. It is the
Domosys policy to have every CEBox tool delivered, installed and
presented on-site by a representative of its technical support
group.
Use of tools involves trade-offs. Just as traditional cabinet
makers complain that using power tools causes a loss of
sensitivity to the wood, assembly language programmers feel that
they use less memory. This was an important point when memory was
expensive and companies were not focusing on the consumer market.
Domosys feels that the vast majority of programming needs can be
met by a well conceived tool with the appropriate and standard
compliant libraries.
