Date: Thu, 29 Jan 1998 01:15:01 -0600 (CST) From: Joel Ray Holveck <joelh@gnu.org> To: jkh@time.cdrom.com Cc: tlambert@primenet.com, dag-erli@ifi.uio.no, hackers@FreeBSD.ORG Subject: Re: Graphical screen saver Message-ID: <199801290715.BAA04631@detlev.UUCP> In-Reply-To: <11464.886042215@time.cdrom.com> (jkh@time.cdrom.com) References: <11464.886042215@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> Remember, I'm mostly writing a template here. My code handles the >> mode switching, syscons interface, etc. and calls hacker-defined >> 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); I'm working with graphics here; mine will be more like scrn_mode, getpixel, putpixel, etc. But the idea is sound, and is being used. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801290715.BAA04631>