crunch@well.UUCP (John Draper) (09/18/85)
Hello folks,
Earlier, another usenet reader posted a request for some of the earlier
Amiga developers to answer some of the most basic questions. Some have since
been answered, and others yet need answering. All are important "nit pickin"
questions on the little "gotchas" of early Amiga development and a sugesstion
of which version of Operating system, Is it still 29?, and tool usage. And
most importantly whats the development environment like. I already assume it
is very difficult due to lack of adequate documentation. I hear they have
ON LINE Technical assistance. Is is Compuserve, or another network. How is
the Technical support?, Can you get them to call you back in the same day??
Whats the E-mail turnaround time. What are the bugs so we can get around them.
And most importantly, what are the guidelines for creating a "Well bahaved"
application program that isn't going to "Step on" an existing program thats
also running. I mean, Cm on now! is it important for me to know how many
"Sectors per track?"
As a "Low end" Commercial software developer, it would be nice to know
in advance some of the problems programmers will have when writing software for
the Amiga. Here are some examples:
1 - What programs are necessary for starting out writing and compiling the
small amount of examples currently available. What files are needed, and
what are their functions. Include: header files, compiler, linker,
libraries, debuggers, and resource files.
2 - How are the best ways of distributing the necessary Compilers, Linkers,
Header files, and other important files on 2 floppy diskettes. How much
space is available on floppys for large programs (if any)?
3 - What are the steps necessary in setting up the "execute" or "Batch" file
and (if not documented in manual) the contents of a typical Batch file.
Setting these things can take days of tedious work.
4 - How long does it take for the compilation process to occur. If it takes
more than 30 seconds, then you will probably have time to jot some of these
things down, then later Post it.
5 - What other procedures are necessary to create a stand-alone application?
Such as Preparation of special Resource files, Definition of how the
program is to be executed, and other important information.
6 - Naturally, the documentation will appear as inadequate because of the
"Strangeness" of it's new Op System. What are some of the "un-documented"
tricks to make a programmers life easier, and have you noted any mis-prints
or other inconsistancy in its documentation, and what is it and where.
A complete artical or publication like this is really needed, and would
make the Usenet a very useful tool for its clients.
If someone else doesn't post an artical, then as soon as I Get my
Amiga (Last heard 6 weeks to go), I will post it. If I have some time
next week, and I remember, I will generate a little "Questionair" for the
early Amiga developers to fill out, then Post it here. It can be used
as a guideline for all to fill out. Some enterprising young Usenet Hacker
should cook up a little questionair program which people could run to fill
it out on line.
If you don't see something by next week, just mail dual!well!crunch and
jog my memory. It shouldn't be too difficult to take notes if it takes any
time to run the "make" file (or equivalant). It would go far to help us
folks who are still waiting for our Amiga's to come.
The opinions I express are that of my own, and are based on my observation
of the articals posted in net.micro.amiga and hope these "Down to earth"
requests continue because there ARE people out there in Net land that are
hearing your complaints and acting on them.
I remain,
...ihnp4!dual!well!crunch