GUI Work

GUI Work

[John S.]

[-- Attachment #1: Type: text/plain, Size: 228 bytes --]

 I am interested in getting involved with GRUB and was wondering what work has been done on implementing a GUI for GRUB 2.

If anyone is working on it right now, could you please let me know how I can help.

Thanks,
John S.

[-- Attachment #2: Type: text/html, Size: 538 bytes --]

Re: GUI Work

[Vesa Jääskeläinen]

John S. wrote:
>  I am interested in getting involved with GRUB and was wondering what
> work has been done on implementing a GUI for GRUB 2.
> If anyone is working on it right now, could you please let me know how I
> can help.

Hi,

I have been doing preparations for it by introducing Video API to GRUB 2
(http://grub.enbug.org/VideoSubsystem). It is still being fine tuned,
but basic design of the GUI could be started by now.

If you search archives from this mailing list you can notice some
messages about it. Here are some links that you should check out:

http://lists.gnu.org/archive/html/grub-devel/2006-04/msg00056.html
http://lists.gnu.org/archive/html/grub-devel/2006-05/msg00008.html

Thanks,
Vesa Jääskeläinen

Re: GUI Work

[John S.]

I'm trying to get myself started in all of this, but I have a ton of  
questions.  You'll have to forgive me if they are obvious, but this  
is my first time looking at the grub source.

Also I have never written code this low-level (on a PC) before.  My  
most relevant experience would probably be writing some ms-dos games,  
which is similar but I'm assuming theres a ton of differences.  So  
please forgive me if I don't know all of the concepts yet.

So here are the questions:

How much of the video API has been written?

What exactly does the file vbe.c do?  I'm assuming it implements a  
VESA BIOS Extension interface that we can use when writing the API  
functions.  Please correct me if I'm wrong.  Also how much work is  
required on this set of code?

If the API has already been started which file is it in?  if it has  
not, which file should be created for it? how about /video/i386/pc/ 
api.c ?

A ton of questions I know, but I'm a fast learner and should be  
caught up soon enough.


On 25-May-06, at 5:31 AM, Vesa Jääskeläinen wrote:

> John S. wrote:
>>  I am interested in getting involved with GRUB and was wondering what
>> work has been done on implementing a GUI for GRUB 2.
>> If anyone is working on it right now, could you please let me know  
>> how I
>> can help.
>
> Hi,
>
> I have been doing preparations for it by introducing Video API to  
> GRUB 2
> (http://grub.enbug.org/VideoSubsystem). It is still being fine tuned,
> but basic design of the GUI could be started by now.
>
> If you search archives from this mailing list you can notice some
> messages about it. Here are some links that you should check out:
>
> http://lists.gnu.org/archive/html/grub-devel/2006-04/msg00056.html
> http://lists.gnu.org/archive/html/grub-devel/2006-05/msg00008.html
>
> Thanks,
> Vesa Jääskeläinen
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel

Re: GUI Work

[Vesa Jääskeläinen]

John S. wrote:
> I'm trying to get myself started in all of this, but I have a ton of
> questions.  You'll have to forgive me if they are obvious, but this is
> my first time looking at the grub source.
> 
> Also I have never written code this low-level (on a PC) before.  My most
> relevant experience would probably be writing some ms-dos games, which
> is similar but I'm assuming theres a ton of differences.  So please
> forgive me if I don't know all of the concepts yet.

You don't actually have to care too much about low-level details. What
is required is to write "high-level" GUI using low-level systems provided.

> So here are the questions:
> 
> How much of the video API has been written?

Bitmap support is missing from CVS, but otherwise most of the
functionality should work. There might be some changes, but I have to
think more on some issues raised on this list.

> What exactly does the file vbe.c do?  I'm assuming it implements a VESA
> BIOS Extension interface that we can use when writing the API
> functions.  Please correct me if I'm wrong.  Also how much work is
> required on this set of code?

vbe.c implements VESA Bios Extension 2.0+ driver for GRUB Video
Subsystem. You are not supposed to use this driver directly. Use Video
API instead. It abstracts used video driver, so we can use same GUI code
on all supported platforms.

> If the API has already been started which file is it in?  if it has not,
> which file should be created for it? how about /video/i386/pc/api.c ?

See video/video.c.

There is also term/videoterm.c and commands/videotest.c that exercises
Video API.

Thanks,
Vesa Jääskeläinen