All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] color command
Date: Thu, 26 Jul 2007 16:41:56 +0200	[thread overview]
Message-ID: <20070726144156.GA8579@aragorn> (raw)
In-Reply-To: <46A7BD2C.50609@nic.fi>

On Thu, Jul 26, 2007 at 12:14:20AM +0300, Vesa Jääskeläinen wrote:
> 
> Hi,
> 
> One idea was to define themable colors and then use grub_video_map_color
> to map this to hardware (color index or RGB value):
> 
> http://grub.enbug.org/VideoSubsystem#head-0df1ed220076ff6cc8188d1a192a21d443cc2456
> 
> You could define normal VGA color with like
> GRUB_COLOR_{WHITE|BLACK|LIGHT_GREEN|YELLOW...}. Then setup theme to map
> GRUB_COLOR_CONSOLE_BACKGROUND->GRUB_COLOR_BLACK and
> GRUB_COLOR_CONSOLE_FOREGROUND->GRUB_COLOR_LIGHT_GREEN. Of course we have
> this missing component 'theme support' here ;)

Ok, but you're missing the user interface part.  How would that be glued?

> You can make dynamic variables in GRUB so that when you set it it will
> call function (which could call proper {term|theme}->set color function).

Nifty.  Is that some sort of preprocessor hack?

> I would rather resolve this issue at same time when resolving graphical
> menu issues (meaning within graphical menu subproject) (still looking
> for more members ;)):
> 
> http://grub.enbug.org/Subprojects
> http://grub.enbug.org/Subprojects/GraphicalMenu

Uhm that's inconvenient for us [1], because we need basic color functionality
(i.e. similar to GRUB Legacy's) soon, and I can't really volunteer more time to
speed up the graphical menu efforts.

[1] Debian, that is.

-- 
Robert Millan

My spam trap is honeypot@aybabtu.com.  Note: this address is only intended
for spam harvesters.  Writing to it will get you added to my black list.



      reply	other threads:[~2007-07-26 14:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 20:53 [RFC] color command Robert Millan
2007-07-25 21:14 ` Vesa Jääskeläinen
2007-07-26 14:41   ` Robert Millan [this message]

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=20070726144156.GA8579@aragorn \
    --to=rmh@aybabtu.com \
    --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.