Date: Thu, 29 Jan 1998 01:02:14 -0200 (EDT) From: Joao Carlos Mendes Luis <jonny@coppe.ufrj.br> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: joelh@gnu.org, tlambert@primenet.com, dag-erli@ifi.uio.no, hackers@FreeBSD.ORG Subject: Re: Graphical screen saver Message-ID: <199801290302.BAA22088@gaia.coppe.ufrj.br> In-Reply-To: <11464.886042215@time.cdrom.com> from "Jordan K. Hubbard" at "Jan 28, 98 06:50:15 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
#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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801290302.BAA22088>