Path: utzoo!attcan!uunet!mcsun!unido!ira.uka.de!Tokyo!grunwald From: grunwald@Tokyo.ira.uka.de (Grunwald Betr. Tichy) Newsgroups: comp.os.os9 Subject: Re: just a little more help... Keywords: PD OSK stuff Message-ID: <90.187.12:02:06@ira.uka.de> Date: 6 Jul 90 12:02:06 GMT References: <7342@ucrmath.ucr.edu> Sender: news@ira.uka.de (USENET News System) Reply-To: grunwald@Tokyo.UUCP (Grunwald Betr. Tichy) Organization: University of Karlsuhe, West-Germany Lines: 51 There are a lot of project to be done (and i would start them, if i could spend the time): 1. Creating a object of the GNU-C Compiler and giving some instructions to the installation. This should be done for 68000 and 68020 Systems. The Port is available from Japan, but there seem to be Problems with the Compilation. 2. An example RBF-Driver written in C. Complete with a makefile and the hardware Parts marked. The Driver should have Versions like: Primitive Multisector Trackprefetch Cache and other performance features included. An OSK - RBF - Driver needs a lot of administrative work inside to give a good performance. This parts could be distributed to ease the writing of Drivers. I have some sources and a lot of ideas for that task, but not the time to do it correctly (i.e. I can work with it, but there are to few coments and the decisions are not properly overthougt). 3. A Socketmanager. There is only a commercial product and this is bundled to the X-Windows System to my knowledge. 4. A SuperSCF-Manager with functions like insert,delete and history. Also Functionkeys should be supported. 5. A Grafical filemanager to get a standard interface for Grafics. Only the primitives like bitblit, line, arc and character display should be supported. Also clipping only against one window. The Manager should notice the capabilties of a device and only the functions not available should be emulated. The RAVE from Microware has only 8 bit colors and that is to big for black and white grafics. Suggestion: Only copy rectangle to display and the draw line has to be done by the driver the rest could be done by the filemanger or not if the driver/device is capable of the function. The create function opens a window and delete closes it. Open and close gain access to it and makdir creates subwindows. The read and write operation can possibly arranged, such that copying a window to and from the disk is possible. 6. The stdio-lib should be reworked to give more performance. Esspecially the write operation should switch of the verify and do the verify by itself. May be with a sizeable verify buffer. The getc and putc routines are also slower as they could be. 7. The cc and dsave commands should be reworked, to avoid the access of shell. If someone uses another shell this can be annoying.\ That are my suggestions. Knut Grunwald, Maximilianstr. 25, 6729 Jockgrim, 07271/51891