Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!lll-winken!uunet!portal!cup.portal.com!Geva_Apple-Maniac_Patz
From: Geva_Apple-Maniac_Patz@cup.portal.com
Newsgroups: comp.sys.apple
Subject: Re: New developments
Message-ID: <16588@cup.portal.com>
Date: 2 Apr 89 13:42:45 GMT
References: <8903312355.AA10273@wpi>
Organization: The Portal System (TM)
Lines: 35

All right,

I have waited all of 2 days and NOBODY has rushed to implement the
standard, PD, windows library for the // series. Thus, I will take said
task upon myself. Now, before I rush into it, I want lots of  feedback
on what people want to see in such a toolbox. Questions which spring
to mind are:

* Mousetext: Should the system use Mousetext, in which event it would not
  work on ][+'s or older //es,  or should it use the Graphics screen, which
  would obviously make the package bigger and slower.

* Calling procedure: How are the routines actually called? Do we want something
  akin to the GS toolbox procedure, something like the ProDOS MLI, or something
  completely different?

* Mouse support: Will a mouse be unsupported, essential, or will the 
  toolbox use 'pseudo-mouse' functions (i.e. allow the keyboard and
  joystick to emulate a mouse) 

* Level: Should  the toolbox allow high-level calls [create dialog box,
  create menus, etc.], low-level calls [clear screen section, save screen
  section, etc.] or both?

* Are uppercase-only systems, 40-column systems, etc. going to be supported?

* Form: What form is the ultimate library going to take? Will it be a 
  run-time library? Will it support BASIC? Assembler? C? Pascal?

I'm sure there are lots of others, but these are all that I can come up
with off the top of my head. I look forward to hearing your response...

%%%%
 Geva
  %%%%