git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Artem Khodush <greenkaa@gmail.com>
To: Andreas Ericsson <ae@op5.se>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [wish] Auto-generate gitk's pretty pictures
Date: Sat, 14 Jan 2006 19:26:04 +0300	[thread overview]
Message-ID: <40b2b7d90601140826k7c30ce7bk3a259061cb333133@mail.gmail.com> (raw)
In-Reply-To: <43C8FE6F.4050206@op5.se>

On 1/14/06, Andreas Ericsson <ae@op5.se> wrote:
> Artem Khodush wrote:
> But, the next feature I plan to add
> > is to show commits in the same window in a way like gitk does.
> >
>
> Why not just have a separate frame for the commits and load gitweb.cgi
> there?

Mainly because gitweb can't show the commit in most
convenient (IMHO) way, with everything on one screen.
I like the way gitk does it, when you can see all at once -
list of changed files in the lower right pane and commit message
with links to parent and child commits and diff in the left.

And with gitweb, those links to related commits must allow somehow
to highlight those commits on the diagram, wich means that gitweb
must be made aware of the frame that it's embedded in, and must
be able to call some javascript there. Eventually I will add interaction
with gitweb in some way or another, but for now, it's easier for me
to just show the commit.

      reply	other threads:[~2006-01-14 16:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12 21:02 [wish] Auto-generate gitk's pretty pictures Martin Langhoff
2006-01-13 22:14 ` Artem Khodush
2006-01-13 22:19   ` Johannes Schindelin
2006-01-13 22:21   ` Junio C Hamano
2006-01-13 22:30     ` Artem Khodush
2006-01-13 22:44   ` Martin Langhoff
2006-01-14  3:05     ` Artem Khodush
2006-01-14 13:36       ` Andreas Ericsson
2006-01-14 16:26         ` Artem Khodush [this message]

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=40b2b7d90601140826k7c30ce7bk3a259061cb333133@mail.gmail.com \
    --to=greenkaa@gmail.com \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.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).