From owner-freebsd-hackers Wed Jan 28 19:03:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29645 for hackers-outgoing; Wed, 28 Jan 1998 19:03:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gaia.coppe.ufrj.br (cisigw.coppe.ufrj.br [146.164.5.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29588 for ; Wed, 28 Jan 1998 19:02:56 -0800 (PST) (envelope-from jonny@coppe.ufrj.br) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.8/8.8.8) id BAA22088; Thu, 29 Jan 1998 01:02:14 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199801290302.BAA22088@gaia.coppe.ufrj.br> Subject: Re: Graphical screen saver In-Reply-To: <11464.886042215@time.cdrom.com> from "Jordan K. Hubbard" at "Jan 28, 98 06:50:15 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 29 Jan 1998 01:02:14 -0200 (EDT) Cc: joelh@gnu.org, tlambert@primenet.com, dag-erli@ifi.uio.no, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk #define quoting(Jordan K. Hubbard) // > routines for variable initialization and the actual drawing. (The // > actual drawing is currently handled by direct memory writes.) I'm not // // It would be nice if, at the very minimum, you supplied some minimum // routines/macros for talking to this memory region, perhaps like this: // // typedef unsigned int scr_char; // char + color + attributes + fut. expansion // // str_char a_scr_char(char *color, u_int attrs, char ch); // scr_char scr_getchar(int x, int y); // void scr_putchar(int x, int y, str_char ach); // // /* Accessors: Possibly inline, possibly macros */ // char *scr_char_color(str_char sch); // u_int scr_char_attrs(str_char sch); // char scr_char_ch(str_char sch); // // This would sort of give you your "getpixel()/putpixel()" equivalent // interface for implementing the higher-level line, rectangle, circle, // etc. drawing primitives which screen-saver writers would probably // much rather use. Isn't this too much overhead for a screen saver ? I haven't yet seen the graphic screen savers, but shouldn't they be done as a user level program with some kernel hooks ? This would allow X to interface with syscons saver framework. Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67