From owner-freebsd-hackers Mon Oct 21 19:57:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA09201 for hackers-outgoing; Mon, 21 Oct 1996 19:57:10 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA09191 for ; Mon, 21 Oct 1996 19:57:07 -0700 (PDT) Received: from haus.efn.org (haus.efn.org [198.68.17.3]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id TAA08443 for ; Mon, 21 Oct 1996 19:57:05 -0700 (PDT) Received: from garcia.efn.org (j_mini@garcia.efn.org [198.68.17.5]) by haus.efn.org (8.7.5/8.7.3) with ESMTP id TAA29271; Mon, 21 Oct 1996 19:59:46 -0700 (PDT) Received: from localhost (j_mini@localhost) by garcia.efn.org (8.7.4/8.7.2) with SMTP id TAA09793; Mon, 21 Oct 1996 19:55:45 -0700 (PDT) X-Authentication-Warning: garcia.efn.org: j_mini owned process doing -bs Date: Mon, 21 Oct 1996 19:55:45 -0700 (PDT) From: Jonathan Mini To: "Jordan K. Hubbard" cc: hackers@FreeBSD.org Subject: Re: Screen savers for syscons.... In-Reply-To: <15186.845931007@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 21 Oct 1996, Jordan K. Hubbard wrote: > > I'm planning on modifying the screen savers that come with FreeBSD > > 2.1.5-R to work with other display devices other than VGA. (like my mono > > system) AFter that, I'd like to write a few screen savers that use the > > 320x200x256 graphics mode of VGA to create a few decent screen savers. > > (let's face it, other than the "green" and "blank" screen savers > > everything else is pitiful.) > > Then please, do it the way we've always discussed it - as a > screen-saver-helper's library you can link your screen saver app with > and save on all the init/teardown code as well as having a convenient > graphics/text library for painting on the screen. Then write your > first few screen savers as consumers of this library, as an > operational test. Well. Considering that that is prettym uch the easies (from my humble point of view) way to do it, I was planning on doing something of the sort. Since I was planning on writing more than one screen saver, it was obvious to me from the start that I was going to either have to wirte a library or cut and paste a lot of redundant code. Fortunatly for you guys, I hate cutting and pasting, plus it annoys me at the size of the "blank" screen saver which really does nothing more than this : fill_screen(' ',FG_WHITE | BG_BLACK); I was planning on making a library that basically gave me three things : - a set of handy routines for writing to the text and graphics modes of the syscons -- be it MDA,VGA, whatever. (I was thinking text,256 and 16 color modes) - hide all that setup and shutdown code -- Why am I looking at it if it's pretty much the same for all screen savers?? - give me a handy hook for a 100hz timer. =) So that I can animate without doing any thinking. > Think "after dark module" :-) I've never played with After Dark's API. Think of it as keeping me "unsoiled." ;) (Or if After Dark did it right, "ignorant.") > Jordan Jon Mini, j_mini@efn.org, mini@4j.lane.edu GAMMA Development Team -------------------------------------------------------------------------- "I think I can, I think I can, I think I can...." little.blue.engine:Reality Protection Fault. (core dumped) --------------------------------------------------------------------------