From: Jakub Narebski <jnareb@gmail.com>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Johan Herland <johan@herland.net>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 3/4] gitweb: show notes in log
Date: Sat, 6 Feb 2010 13:57:57 +0100 [thread overview]
Message-ID: <201002061357.59245.jnareb@gmail.com> (raw)
In-Reply-To: <1265300338-25021-4-git-send-email-giuseppe.bilotta@gmail.com>
On Thu, 4 Feb 2010, Giuseppe Bilotta wrote:
> The notes are shown in full to the left of the log message.
Thats all good if you have wide (high resolution) screen, and your
project follows common commit message conventions of keeping lines in
commit message no longer than at most 80 characters, and you don't need
to use large size fonts.
What happens if screen size is too small to contain both commit message
and notes? Does it do the sensible thing of putting notes _below_
commit message in such situation? I do not know CSS+HTML enogh to
answer this question myself.
BTW. signoff?
P.S. We would probably want some support for notes also in feeds (Atom
and RSS feed), but this can be left for the future commit.
> @@ -1631,6 +1631,7 @@ sub format_subject_html {
> # display notes next to a commit
> sub format_notes_html {
> my %notes = %{$_[0]};
> + my $tag = $_[1] || 'span' ;
This could be
my $notes = shift;
my $tag = shift || 'span' ;
and then use %$notes.
> my $ret = "";
> while (my ($ref, $text) = each %notes) {
> # remove 'refs/notes/' and an optional final s
> @@ -1639,15 +1640,15 @@ sub format_notes_html {
>
> # double markup is needed to allow pure CSS cross-browser 'popup'
> # of the note
> - $ret .= "<span title='$ref' class='note-container $ref'>";
> - $ret .= "<span title='$ref' class='note $ref'>";
> + $ret .= "<$tag title='$ref' class='note-container $ref'>";
> + $ret .= "<$tag title='$ref' class='note $ref'>";
> foreach my $line (split /\n/, $text) {
> $ret .= esc_html($line) . "<br/>";
> }
> - $ret .= "</span></span>";
> + $ret .= "</$tag></$tag>";
> }
> if ($ret) {
> - return "<span class='notes'>$ret</span>";
> + return "<$tag class='notes'>$ret</$tag>";
> } else {
> return $ret;
> }
Nice trick, but is this distinction really necessary?
> @@ -4581,6 +4582,7 @@ sub git_log_body {
> next if !%co;
> my $commit = $co{'id'};
> my $ref = format_ref_marker($refs, $commit);
> + my $notes = format_notes_html($co{'notes'}, 'div');
> my %ad = parse_date($co{'author_epoch'});
> git_print_header_div('commit',
> "<span class=\"age\">$co{'age_string'}</span>" .
> @@ -4598,6 +4600,7 @@ sub git_log_body {
> git_print_authorship(\%co, -tag => 'span');
> print "<br/>\n</div>\n";
>
> + print "$notes\n";
> print "<div class=\"log_body\">\n";
> git_print_log($co{'comment'}, -final_empty_line=> 1);
> print "</div>\n";
With respect to the question about what happens if the screen is not
wide enough, shouldn't notes be put in HTML source below body (commit
message)?
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2010-02-06 12:58 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 16:18 [PATCH 0/4] gitweb: preliminary notes support Giuseppe Bilotta
2010-02-04 16:18 ` [PATCH 1/4] gitweb: notes feature Giuseppe Bilotta
2010-02-04 16:33 ` Junio C Hamano
2010-02-04 16:46 ` Junio C Hamano
2010-02-04 17:21 ` Jakub Narebski
2010-02-04 20:08 ` Giuseppe Bilotta
2010-02-04 21:03 ` Junio C Hamano
2010-02-04 23:38 ` Giuseppe Bilotta
2010-02-05 10:36 ` Johan Herland
2010-02-05 16:10 ` Junio C Hamano
2010-02-05 21:31 ` Giuseppe Bilotta
2010-02-05 22:31 ` Junio C Hamano
2010-02-06 8:16 ` Giuseppe Bilotta
2010-02-04 21:07 ` Junio C Hamano
2010-02-04 23:20 ` Jakub Narebski
2010-02-05 0:44 ` Jakub Narebski
2010-02-05 0:55 ` Junio C Hamano
2010-02-05 8:42 ` Giuseppe Bilotta
2010-02-05 23:44 ` Jakub Narebski
2010-02-06 9:02 ` Giuseppe Bilotta
2010-02-06 22:14 ` Jakub Narebski
2010-02-06 22:58 ` Giuseppe Bilotta
2010-02-07 1:20 ` Jakub Narebski
2010-02-07 1:38 ` Jakub Narebski
2010-02-07 1:48 ` Johan Herland
2010-02-07 11:08 ` Jakub Narebski
2010-02-07 11:14 ` Giuseppe Bilotta
2010-02-07 12:41 ` Jakub Narebski
2010-02-07 18:38 ` Junio C Hamano
2010-02-07 20:11 ` Giuseppe Bilotta
2010-02-07 21:08 ` Jakub Narebski
2010-02-07 10:57 ` Giuseppe Bilotta
2010-02-07 11:11 ` Jakub Narebski
2010-02-04 16:18 ` [PATCH 2/4] gitweb: show notes in shortlog view Giuseppe Bilotta
2010-02-06 0:18 ` Jakub Narebski
2010-02-06 9:24 ` Giuseppe Bilotta
2010-02-04 16:18 ` [PATCH 3/4] gitweb: show notes in log Giuseppe Bilotta
2010-02-06 12:57 ` Jakub Narebski [this message]
2010-02-06 13:14 ` Giuseppe Bilotta
2010-02-06 21:47 ` Jakub Narebski
2010-02-04 16:18 ` [PATCH 4/4] gitweb: show notes in commit(diff) view Giuseppe Bilotta
2010-02-06 13:16 ` Jakub Narebski
2010-02-06 14:15 ` Giuseppe Bilotta
2010-02-06 14:34 ` Jakub Narebski
2010-02-06 16:13 ` Giuseppe Bilotta
2010-02-06 21:50 ` Jakub Narebski
2010-02-06 22:17 ` Giuseppe Bilotta
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=201002061357.59245.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=giuseppe.bilotta@gmail.com \
--cc=johan@herland.net \
/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).