From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH] multistring support in gui_label
Date: Tue, 16 Apr 2013 21:10:23 +0400 [thread overview]
Message-ID: <20130416211023.34876656@opensuse.site> (raw)
In-Reply-To: <1720724.fd4NVO69U8@icedphoenix>
В Tue, 16 Apr 2013 13:04:28 +0400
Vladimir Testov <vladimir.testov@rosalab.ru> пишет:
> >Please don't use // comments.
> O.k. I won't.
> >This code completely forgets the cases
> >when even the first word doesn't fit in the available space.
>
> Mmm. It can handle this case actually.
>
> >The code as whole breaks some unicode concepts like e.g. bidi stack.
>
> Didn't get what you mean.
>
> >Could you reuse the already available line-vreaking algorithm in
> >normal/term.c and normal/charset.c ? Since the line-breaking is
> >artificially disabled for labels it should require only minor
> >adjustments to be reenabled.
>
> Yep! Here it is (patch included)!
>
> +/* Differs from grub_font_draw_line only in multiline output */
You mean grub_font_draw_string? Is it possible to extend this function
instead of duplicating it?
> +grub_err_t
> +grub_font_draw_multiline (const char *str, grub_font_t font,
> + grub_video_color_t color,
> + int baseline_y, int font_height,
> + int max_width, int max_height,
> + int align)
> +
> + grub_err_t print_line ()
> + {
> + while (pos != ptr)
> + auto grub_ssize_t getcharwidth (const struct grub_unicode_glyph *c);
> + grub_ssize_t getcharwidth (const struct grub_unicode_glyph *c)
> + {
> + return grub_font_get_constructed_device_width (font, c);
> + }
All nested functions were removed from trunk. Please do not reintroduce
them. This should not even compile.
next prev parent reply other threads:[~2013-04-16 17:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 9:04 [PATCH] multistring support in gui_label Vladimir Testov
2013-04-16 17:10 ` Andrey Borzenkov [this message]
2013-04-17 6:56 ` Vladimir Testov
2013-04-17 7:01 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-17 9:02 ` Vladimir Testov
2013-04-17 11:16 ` Vladimir Testov
2013-04-17 11:39 ` Vladimir Testov
2013-04-17 12:41 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-23 11:58 ` Vladimir Testov
2013-04-23 16:26 ` [RFC][PATCH] " Vladimir Testov
-- strict thread matches above, loose matches on Subject: below --
2013-03-22 15:58 [PATCH] " Vladimir Testov
2013-04-03 7:20 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-03-21 17:17 Vladimir Testov
2013-03-21 18:12 ` Gerard Butler
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=20130416211023.34876656@opensuse.site \
--to=arvidjaar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).