[comp.sys.amiga] Amiga 500, digitizing, c-compilers, help!

jojo@speedy.WISC.EDU (Jon Wesener) (10/16/87)

Hi comp.sys.amiga,

	I've just jumped the comp.sys.ibm.pc ship after getting totally sick
of it's graphix.  (What Graphix would that be ;-) )  Anyway, I wrote a
game for the pc called Astrotit that will be my first port to the Amiga
and seeing I just got a 500, I don't know shit about where to start.

	1st, What is a good c-compiler for the Amiga.  I only have the 1
	floppy at present and want one that works off 1 floppy rather well.

	2, Which is a good graphix editor?  My system on the pc was to use
	an editor, draw the cells of the animation sequence, capture the screen,
	come in with a cell grabber that would generate c-code for each cell and
	link it in to the program.  Is there an easier way to do this on the
	Amiga?

	3, I want to get a digitizer but don't know what this entails.  I've
	seen adds for digi-pic which I gather you attach between a camera and
	your amiga, but am lost from there on.  What equipment do I need,
	where can I get it and what are approximate costs?

	4, I'll have more questions as I run into walls!  Thanx in advance
	for any and all help.

--j

jon wesener
jojo@speedy.wisc.edu
	"Truth is stranger than fishing..."

higgin@cbmvax.UUCP (Paul Higginbottom SALES) (10/16/87)

in article <4477@spool.wisc.edu>, jojo@speedy.WISC.EDU (Jon Wesener) says:
> 	1st, What is a good c-compiler for the Amiga.  I only have the 1
> 	floppy at present and want one that works off 1 floppy rather well.

Two drives is really helpful as you can then have a system disk and a
source/object/binary disk.

> 	2, Which is a good graphix editor?  My system on the pc was to use
> 	an editor, draw the cells of the animation sequence, capture the screen,
> 	come in with a cell grabber that would generate c-code for each cell and
> 	link it in to the program.  Is there an easier way to do this on the
> 	Amiga?

DPaint is the most popular graphics program, and it has some amazing
features.  There are public domain utilities to take brushes and turn
them into C code.

> 	3, I want to get a digitizer but don't know what this entails.  I've
> 	seen adds for digi-pic which I gather you attach between a camera and
> 	your amiga, but am lost from there on.  What equipment do I need,
> 	where can I get it and what are approximate costs?

Digi-View is $199 (I think) for the software and interface.  They'll sell
you a B&W good resolution security type camera for another $199 (I think).
It's VERY popular.

> jon wesener

	Paul.

richard@gryphon.CTS.COM (Richard Sexton) (10/18/87)

In article <4477@spool.wisc.edu> jojo@speedy.WISC.EDU (Jon Wesener) writes:
>Hi comp.sys.amiga,
>
>	I've just jumped the comp.sys.ibm.pc ship after getting totally sick
>of it's graphix.  (What Graphix would that be ;-) )  Anyway, I wrote a
>game for the pc called Astrotit that will be my first port to the Amiga
>

I read the .ibm.pc group (out of morbid curiosity) and they sure were 
excited over astrotit. REAL excited.

Somebody get this guy a cape.

>jon wesener
>jojo@speedy.wisc.edu
>	"Truth is stranger than fishing..."

-- 
Richard J. Sexton
INTERNET:     richard@gryphon.CTS.COM
UUCP:         {hplabs!hp-sdd, sdcsvax, ihnp4, nosc}!crash!gryphon!richard

"It's too dark to put the keys in my ignition..."

richard@gryphon.CTS.COM (Richard Sexton) (10/18/87)

In article <2529@cbmvax.UUCP> Paul Higginbottom  writes:
>in article <4477@spool.wisc.edu>, jojo@speedy.WISC.EDU (Jon Wesener) says:
>> 	1st, What is a good c-compiler for the Amiga.  I only have the 1
>> 	floppy at present and want one that works off 1 floppy rather well.
>
>Two drives is really helpful as you can then have a system disk and a
>source/object/binary disk.

I only have one drive, and have found the following procedure helpful.

I have 1 Meg of memory and copy the compiler, assembler, linker, includes
libraries and source into RAM:

I do my compiles in RAM:, and iff the compile was successful, 
the source is copied back to floppy.

You get the advantage of RAM: speed, with the security of knowing you
always have a good copy of your source on a floppy.

I originally had the script copy the source after every compile,
which was an unmitigated disaster. After the compiler noticed an error
it wasted my time by replacing the last good copy on the floppy with
the one that just got errors. Arrrrg !

>> jon wesener
>
>	Paul.


-- 
Richard J. Sexton
INTERNET:     richard@gryphon.CTS.COM
UUCP:         {hplabs!hp-sdd, sdcsvax, ihnp4, nosc}!crash!gryphon!richard

"It's too dark to put the keys in my ignition..."

dillon@CORY.BERKELEY.EDU (Matt Dillon) (10/19/87)

	I have found that to develop seriously you need at least 2 Meg of RAM.
With that, I can put all the executables, libraries, and include files, as 
well as the rest of my working enviroment in VD0:  .. I placed all the
sub-directory includes (*/*.h) into a single precompiled symbol table  (I
use Aztec C).

	I usually leave the source on floppy.  The object files are destined 
for either floppy or RAM: ... this way if the machine crashes I don't loose
anything.  BTW this infers only one floppy drive is required, although I have
two myself.

					-Matt