X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f996b,2884b91eb78b5788 X-Google-Attributes: gidf996b,public X-Google-ArrivalTime: 2003-03-31 16:22:00 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!headwall.stanford.edu!fu-berlin.de!uni-berlin.de!ab3a9.pppool.DE!not-for-mail From: Josef 'Jupp' Schugt Newsgroups: alt.ascii-art Subject: Re: hows the ascii os?? Date: Mon, 31 Mar 2003 22:46:00 +0000 Organization: none Lines: 27 Message-ID: References: <3mc56b.fj8.ln@server.techdrive.foo> NNTP-Posting-Host: ab3a9.pppool.de (213.6.179.169) X-Trace: fu-berlin.de 1049156519 3534731 213.6.179.169 (16 [53633]) X-Orig-Path: jupp.8m.com!news User-Agent: slrn/0.9.7.4 (Linux) Xref: archiver1.google.com alt.ascii-art:22581 On Sun, 30 Mar 2003 00:15:02 GMT, Richard James wrote: > You don't send the picture across you just send the commands to > draw it. This is efficient until you say surf the web and you have > to send across images to draw. And still the amount of data you have to transfer is an order of magnitude more. Suppose you are running X and some cute window manager. Allmost all the grapical elements *are* pictures you need to send. IIRC lines and rectangles are all for which commands do exist. Let us assume that all that needs to be updated is an icon with 16 bit color depth and a size of 48 x 48. That's 4608 byte without any compression. Compare this to 132 x 50 x 2 = 13200 byte - also without compression. Assuming that the graphical data can be reduced to 1/2 and the textual data to 1/3 (both seems reasonable). Draw you own conclusions, we are getting beyond the subject of this group. OB-ASCII: __ ___ / \ |__) \__/ |__) >;-> Josef 'Jupp' Schugt.