All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Goth <unununium@aircanopy.net>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] GSoC #07 VBE double buffering (vs r1885)
Date: Sun, 5 Oct 2008 14:57:20 -0500 (CDT)	[thread overview]
Message-ID: <777113540.40311223236640078.JavaMail.root@aczmb1> (raw)
In-Reply-To: <20081005124723.56912905@gibibit.com>

"Colin D Bennett" <colin@gibibit.com> wrote:
> First make it work, then make it rock.

I certainly do appreciate that, but...

> my plan is to avoid complicated dirty-region repaint strategies 
> at first.

Requiring full-screen repaints is an architectural design that might need rework to undo later.  Or might not, depending on how you implement it.  The interim approach you choose now should be informed by foresight.

Full-screen repaint approach that will require rework later:

- One function draws everything in sequence.  It gets called every frame.

Full-screen repaint approach that will be easy to integrate into a partial update scheme:

- A separate function exists for drawing each logical unit of the screen.
- Every frame, one function calls all the separate functions in sequence.

Or something like that.

-- 
Andy Goth | http://andy.junkdrome.org/
unununium@{aircanopy.net,openverse.com}



  reply	other threads:[~2008-10-05 19:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1745824252.39921223234235570.JavaMail.root@aczmb1>
2008-10-05 19:17 ` [PATCH] GSoC #07 VBE double buffering (vs r1885) Andy Goth
2008-10-05 19:47   ` Colin D Bennett
2008-10-05 19:57     ` Andy Goth [this message]
2008-10-06 19:02       ` Vesa Jääskeläinen
2008-10-13 16:48         ` Colin D Bennett
2008-10-13 17:12           ` Colin D Bennett
2008-08-31  6:58 [PATCH] GSoC #07 VBE double buffering Colin D Bennett
2008-10-05  4:43 ` [PATCH] GSoC #07 VBE double buffering (vs r1885) Colin D Bennett
2008-10-05  8:52   ` Vesa Jääskeläinen
2008-10-05 16:16     ` Colin D Bennett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=777113540.40311223236640078.JavaMail.root@aczmb1 \
    --to=unununium@aircanopy.net \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.