Path: utzoo!mnetor!tmsoft!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!uunet!munnari.oz.au!brolga!bunyip.cc.uq.oz.au!marlin.jcu.edu.au!glmwc
From: glmwc@marlin.jcu.edu.au (Matt Crowd)
Newsgroups: comp.sys.amiga.misc
Subject: Re: A3500 ??
Message-ID: <1991Jan27.090217.6057@marlin.jcu.edu.au>
Date: 27 Jan 91 09:02:17 GMT
References: <7100@crash.cts.com> <1991Jan24.192933.11944@zoot.avgrp.cr.rok.com>
Distribution: comp.sys.amiga
Organization: James Cook University of North Queensland
Lines: 26

In article <1991Jan24.192933.11944@zoot.avgrp.cr.rok.com> dah@zoot.avgrp.cr.rok.com (Dave Haverkamp) writes:
>In article <7100@crash.cts.com> seanc@pro-party.cts.com (Sean Cunningham) writes:
>>...I'd also like to see C= publish a minimum styleguide for developers to
>>follow.  Not as strict as Apple's, but something that Ami developers could
>>build on while maintaining some consistency across applications.
>> 
>   Very, good suggestion.  C= needs to take an active role in establishing
>standards for the Amiga.  That way developers will be compatible with 
>each other to some degree.  Users always benefit when there is a low learning
>curve for some new software package.  Plus, it would be nice to think you
>can continue purchasing Brand-X software to run on Brand-Y hardware.
>-- 

The 1.3 Libraries and devices manual has a smallish chapter on 
making your application fairly standard.  If every developer
following the guidelines in the RKMs, applications would be
pretty standard.  Hopefully the 2.0 RKMs will be even better
than the excellent 1.3 manuals...

>--------------------------------------------------------------------------
>David A. Haverkamp                    Collins Commercial Avionics Division
>                                      Rockwell International   MS 124-211
>INTERNET: dah@zoot.avgrp.cr.rok.com   Cedar Rapids, Iowa 52498

Regards,
Colin Adams