From: Robert Millan <rmh@aybabtu.com>
To: Colin D Bennett <colin@gibibit.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: gfxmenu available in experimental
Date: Sat, 21 Nov 2009 19:40:16 +0100 [thread overview]
Message-ID: <20091121184015.GA5537@thorin> (raw)
In-Reply-To: <20091121101701.72853d48@svelte>
On Sat, Nov 21, 2009 at 10:17:01AM -0800, Colin D Bennett wrote:
> On Sat, 21 Nov 2009 16:43:57 +0100
> Robert Millan <rmh@aybabtu.com> wrote:
>
> > On Fri, Nov 20, 2009 at 11:17:51PM +0100, Vladimir 'φ-coder/phcoder'
> > Serbinenko wrote:
> > > Example menu is available at
> > > http://grub.gibibit.com/files/overlay_2009-07-19.tar.gz
> >
> > Colin, we would need to know more details about the theme support
> > files.
> >
> > Are all the theme files in that tarball written by you? Which images
> > did you make yourself? I'm specially interested in the terminal-box
> > ones.
>
> It would be easier perhaps if I list the elements that I did not create:
>
> - The 'winter' background.
> - The Ubuntu theme logo image/text.
What about the icons? I assume you didn't create the MS Windows logo ;-)
> Everything else I created using the GIMP and Inkscape, primarily. The
> terminal-box images for the 'winter' theme were created in Inkscape (I
> think the theme source tarball includes the SVG source file, which is
> exported to PNG files in slices by a shell script). In Inkscape I
> defined the slices so that the shell script can export them by name.
We would need this SVG source (it isn't in the tarball). Do you still have
it?
> I certainly intend them to be included under my contributor agreement,
Great! I tried to adapt them to make something simpler that would be added
to GRUB tree, but I'm totally incompetent to make beautiful artwork. Our
current options are:
- Make a simple, unifont-based "GRUB theme" that could be added to our
official tree and serve as reference for others. It should include the
basic graphical elements like terminal-box and linear/circular counters.
- Have Debian include a package of themes for GRUB, based on your work.
For that we would require that the parts you made are separated in a
new tarball, and a suitable license be included.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-11-21 18:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 22:17 gfxmenu available in experimental Vladimir 'φ-coder/phcoder' Serbinenko
2009-11-20 22:54 ` Colin D Bennett
2009-11-24 6:43 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-11-21 12:26 ` Robert Millan
2009-11-21 19:04 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-11-21 15:43 ` Robert Millan
2009-11-21 18:07 ` Robert Millan
2009-11-21 18:17 ` Colin D Bennett
2009-11-21 18:24 ` Felix Zielcke
2009-11-26 18:18 ` Colin D Bennett
2009-11-21 18:40 ` Robert Millan [this message]
2009-11-27 11:42 ` Felix Zielcke
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=20091121184015.GA5537@thorin \
--to=rmh@aybabtu.com \
--cc=colin@gibibit.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.