Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!nuchat!sugar!peter
From: peter@sugar.UUCP (Peter da Silva)
Newsgroups: comp.sys.amiga,comp.sys.atari.st
Subject: Re: Software Development
Message-ID: <861@sugar.UUCP>
Date: Tue, 6-Oct-87 08:01:03 EDT
Article-I.D.: sugar.861
Posted: Tue Oct  6 08:01:03 1987
Date-Received: Fri, 9-Oct-87 03:17:34 EDT
References: <872@percival.UUCP> <3878@well.UUCP> <1263@dasys1.UUCP> <1769@cadovax.UUCP>
Distribution: na
Organization: Sugar Land UNIX - Houston, TX
Lines: 24
Xref: mnetor comp.sys.amiga:9123 comp.sys.atari.st:5493

> >             Now, a subroutine library that allows you to make GEM
> >calls but uses Intuition... that I could see.

Did you miss this line?

> And hell, it just opens up it's own screen so you can still multitask at
> the same time.   Not 'sticking' the GEM interface on the users is
> only going to 1) hurt the Amiga sales of Atari developers, and 2) hurt
> Amiga users who would like to have Atari packages.  Cad-3D anyone?

You're confusing the users with the developers. The developers can be kept
happy with a GEM compatibility library that runs under Intuition. The users
need to be presented with as few divergent working environments as possible.
For the Amiga, for better or for worse, that means Intuition.

I have experience with one ST port already. Music Studio uses a GEM-like
interface (touchy menus, one-button-mouse, the whole nine yards), and it's
a pain to use.

GEM.library would give you all the GEM junk, *and* save memory. How many
copies of different menu-handling code do you want, anyway?
-- 
-- Peter da Silva  `-_-'  ...!hoptoad!academ!uhnix1!sugar!peter
-- Disclaimer: These U aren't mere opinions... these are *values*.