From: Vladimir Serbinenko <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: vesafb terminal for testing.
Date: Mon, 15 Aug 2005 18:06:54 +0200 [thread overview]
Message-ID: <4300BD9E.9030708@gmail.com> (raw)
In-Reply-To: <4300B36B.2000602@yahoo.fr>
Vincent Pelletier wrote:
> Yoshinori K. Okuji wrote:
>
> >Just to give you some ideas,
>
>
> Same here :) (from simple to ambitious) :
> -Pictures corresponding to entries (set a background/in front
> of/near/instead of)
> -customisable positions for menu entries (ubuntu could out them in
> circle over their logo as background, things like that)
> -Subentries
Exactly the thing that I planned to do the next (it's a part of
scripting support)
> -some generic & skinable widgets (?)
We don't need to make the whole thing absolutely skinnable (just the
basic skins)
if we make like I proposed (menus like terminals, in modules) because if
someone wants to
change completely the look he can just write a new menu module.
> -mouse handling (??)
>
It must not be difficult: we can just port mouse.com from FreeDos or use
any other
mouse implementation. But here we also need the general interface because
there are different mouse types: PS/2, USB, serial (old PC), perhaps
something else
exotical. It could be something like
register_mouse_click_callback (void (*mouse_callback) (int x, int y, int
flags));
remove_mouse_click_callback (void (*mouse_callback) (int x, int y, int
flags));
and flags are like GRUB_MOUSE_LEFT, GRUB_MOUSE_RIGHT,
GRUB_MOUSE_DOUBLE,... and callback checks itself we it has to react to
this click
but mouse support can be added at any moment. Now the most important
questions is how
to make the *general/basic* things to ensure the maximum flexibility in
the future as
Yoshinori K. Okuji said in about 6 months we have to block them: don't
change them anymore.
The mouse support and fancy menu interface can be written even after but
now we must decide
what's the best way to write basic things, so we don't have to create
any incompatibility and
in preference without touching kernel code at all: just write the module
to add fancy
menu or mouse support or anything else.
> Vincent Pelletier
Vladimir
next prev parent reply other threads:[~2005-08-15 16:22 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-14 11:52 vesafb terminal for testing Vesa Jääskeläinen
2005-08-14 14:48 ` Yoshinori K. Okuji
2005-08-14 15:45 ` Vesa Jääskeläinen
2005-08-14 16:47 ` Vladimir Serbinenko
2005-08-14 19:25 ` Yoshinori K. Okuji
2005-08-15 15:23 ` Vincent Pelletier
2005-08-15 16:06 ` Vladimir Serbinenko [this message]
2005-08-15 17:02 ` Marco Gerards
2005-08-15 17:19 ` Yoshinori K. Okuji
2005-08-15 17:41 ` Marco Gerards
2005-08-15 18:55 ` Yoshinori K. Okuji
2005-08-15 20:54 ` Marco Gerards
2005-08-15 21:44 ` Vesa Jääskeläinen
2005-08-16 6:47 ` Vincent Pelletier
2005-08-16 10:20 ` Marco Gerards
2005-08-15 17:07 ` Marco Gerards
2005-08-16 6:54 ` Vincent Pelletier
2005-08-14 21:48 ` Vesa Jääskeläinen
2005-08-14 22:19 ` Yoshinori K. Okuji
2005-08-15 15:52 ` Vesa Jääskeläinen
2005-08-15 16:13 ` Yoshinori K. Okuji
2005-08-15 15:42 ` Vladimir Serbinenko
2005-08-19 0:48 ` Yoshinori K. Okuji
2005-09-18 21:03 ` Vesa Jääskeläinen
2005-09-19 19:00 ` Yoshinori K. Okuji
2005-09-19 23:11 ` Vesa Jääskeläinen
2005-09-20 17:13 ` Yoshinori K. Okuji
2005-08-15 17:24 ` Marco Gerards
2005-08-15 21:05 ` Vesa Jääskeläinen
2005-08-15 21:21 ` Marco Gerards
2005-08-15 21:39 ` Vesa Jääskeläinen
2005-08-16 10:04 ` Marco Gerards
2005-08-16 18:36 ` Vesa Jääskeläinen
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=4300BD9E.9030708@gmail.com \
--to=phcoder@gmail.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.