graphics mode

graphics mode

[Yoshinori K. Okuji]

Today I checked the graphic console patch by Mandriva to get some idea. Their 
patch looks very similar to a patch by Conectiva or Red Hat (not surprising, 
as Mandriva = Mandrake + Conectiva).

Basically, they add these functions into GRUB Legacy:

- Set the VGA mode to 0x12 (640x480x16).

- Get font data from BIOS and attach shades to glyphs optionally.

- Put a background image and tweak the palette according to the image.

- Set the font color.

- Blink the cursor by an interrupt handler.

- Specify a viewport where the contents of a menu are shown.

I guess there is no reason that we cannot use the mode 0x12 instead of 0x10 
(640x350x16), if they can. Since the height 350 is very small, I'm willing to 
go back to 0x12. Marco, do you agree?

I don't know how important to use shades. Maybe the readability becomes too 
bad when drawing a colorful background without this kind of trick.

The palette optimization is dirty, but required when the color depth is very 
small.

Personally, I don't think cursor blinking is required. I rather prefer a 
static, reverse-color cursor, as in Emacs.

The concept of a viewport is really good, and we should implement this in GRUB 
2.


Another thing. Now I'm considering that it might be better to merge the vga 
terminal and the vesafb terminal from users' point of view. After all, 
ordinary users don't know what VGA is or what VBE is, and they do not want to 
specify such a complex thing. They just want to see a graphical interface.

So, one way is to make a graphics terminal and somehow automatically choose a 
valid mode, while still allowing an expert to specify detailed information 
via options. For example, when the user specifies nothing, GRUB can first try 
VBE and fall back to VGA.

Okuji

Re: graphics mode

[Marco Gerards]

"Yoshinori K. Okuji" <okuji@enbug.org> writes:

> - Get font data from BIOS and attach shades to glyphs optionally.

I prefer the fontmanager, it is portable.

> I guess there is no reason that we cannot use the mode 0x12 instead of 0x10 
> (640x350x16), if they can. Since the height 350 is very small, I'm willing to 
> go back to 0x12. Marco, do you agree?

Does everything (especially scrolling) still work correctly after
changing it?  If it does, I do agree.

> The palette optimization is dirty, but required when the color depth is very 
> small.

How does this work?

> Personally, I don't think cursor blinking is required. I rather prefer a 
> static, reverse-color cursor, as in Emacs.

If someone has a good reason to use this, it can be implemented later.

> The concept of a viewport is really good, and we should implement this in GRUB 
> 2.

Yes, it is important.  By doing this it will be easier to make a
theme.  The more things that can be customized, the better IMO.

--
Marco

Re: graphics mode

[Yoshinori K. Okuji]

On Sunday 04 September 2005 01:09 am, Marco Gerards wrote:
> Does everything (especially scrolling) still work correctly after
> changing it?  If it does, I do agree.

Why not?

> > The palette optimization is dirty, but required when the color depth is
> > very small.
>
> How does this work?

It supports only XPM format, and XPM defines a palette in the beginning of a 
file. So it just needs to tweak the VGA palette (up to 14 colors).

Okuji

Re: graphics mode

[Marco Gerards]

"Yoshinori K. Okuji" <okuji@enbug.org> writes:

> On Sunday 04 September 2005 01:09 am, Marco Gerards wrote:
>> Does everything (especially scrolling) still work correctly after
>> changing it?  If it does, I do agree.
>
> Why not?

I vaguely remember there was a problem with scrolling.  I do not
remember anymore what causes the problem.

--
Marco