All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] color command
Date: Thu, 26 Jul 2007 00:14:20 +0300	[thread overview]
Message-ID: <46A7BD2C.50609@nic.fi> (raw)
In-Reply-To: <20070725205327.GA2153@aragorn>

Robert Millan wrote:
> Hi,
> 
> I'd like to discuss the possibility of providing functionality equivalent to
> the "color" command in GRUB Legacy.
> 
> One of the downsides of how color worked in GRUB Legacy is that internally
> colors were handled by GRUB directly as VGA codes.  Since this isn't portable,
> I suggest that we avoid it completely instead of just mapping them for
> platforms using non-VGA tables (I've seen that ofconsole is using RGB structs).
> 
> The solution I propose would be to have a "color" variable (and another one for
> highlight color?) with human readable names based on the list in GRUB Legacy,
> and let each terminal parse that and pull their colors during initialisation
> (this has the downside that one would have to reinitialise terminal after
> changing color, but this seems to be akin to the gfxterm / gfxmode situation
> and I think is reasonable).
> 
> Any comments?  Should I go on implementing that?
> 

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 ;)

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).

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

Thanks,
Vesa Jääskeläinen



  reply	other threads:[~2007-07-25 21:14 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 [this message]
2007-07-26 14:41   ` Robert Millan

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=46A7BD2C.50609@nic.fi \
    --to=chaac@nic.fi \
    --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.