From: Petr Baudis <pasky@suse.cz>
To: Artem Khodush <greenkaa@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: announce: git browser
Date: Mon, 5 Dec 2005 01:42:38 +0100 [thread overview]
Message-ID: <20051205004238.GE22159@pasky.or.cz> (raw)
In-Reply-To: <40b2b7d90512041623g1e22fecai9470ffcb94f40a58@mail.gmail.com>
Hello,
Dear diary, on Mon, Dec 05, 2005 at 01:23:24AM CET, I got a letter
where Artem Khodush <greenkaa@gmail.com> said that...
> I'd like to announce experimental web interface for git,
> complementary to gitweb. It visualizes commit history graph
> and shows commit diffs.
>
> See http://straytree.com/git-browser/GitBrowser.html?r=git
quite interesting! I always dreamt (not intensively enough to go
myself and do it) about gitweb having gitk-like visualization, possibly
this might help. ;-)
Couple of initial notes:
* I would find it much nicer if you wouldn't "squeeze" all the day's
(except merge) commits together, but left them separate. Possibly a
switch to squeeze them, but I'm really not sure if it's even useful to
have.
* The line graphics etc. might be more colourful and prettier. ;-)
* Then it could have a "gitk mode" where the time flows vertically and
author+title+time is shown in each line. It turns out that this might
not be the prettiest, but it's really the most informative and useful
view, IMHO.
* When I click on the little black box, the commit window disappears
before I manage to click on anything inside; I would intuitively expect
the reverse behaviour - that this happens when I don't click on the box.
Or that clicking on the box does not matter. *shrug* The web interface
with those windows popping up admitelly makes my mind somewhat
uncomfortable, but it's hard to pin-point down why.
* Possibly, the commit information could be shown in a dedicated
screen area altogether. It also wouldn't obscure the view of the actual
diagram, and it would be more visible that it cutely highlights the
appropriate box based on the current commit you have your cursor on.
* It looks too much like Feynman diagrams when the merge arrow
points slightly backwards; perhaps you could try to avoid that.
* It doesn't seem to handle the UTF8 characters properly.
Quite nice for starters, though! The diff viewer looks pretty slick,
too.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
next prev parent reply other threads:[~2005-12-05 0:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 0:23 announce: git browser Artem Khodush
2005-12-05 0:42 ` Petr Baudis [this message]
2005-12-05 1:20 ` Artem Khodush
2005-12-05 23:26 ` Petr Baudis
2005-12-06 6:40 ` Artem Khodush
2005-12-06 6:53 ` Junio C Hamano
2005-12-06 7:31 ` Artem Khodush
2005-12-06 7:45 ` Junio C Hamano
2005-12-06 8:13 ` Artem Khodush
2005-12-06 8:19 ` Junio C Hamano
2005-12-06 8:56 ` Artem Khodush
2005-12-06 9:09 ` Junio C Hamano
2005-12-06 20:23 ` Junio C Hamano
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=20051205004238.GE22159@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=greenkaa@gmail.com \
/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).