From mboxrd@z Thu Jan 1 00:00:00 1970 From: david@lang.hm Subject: Re: Google Summer of Code 2009: GIT Date: Wed, 11 Mar 2009 09:32:05 -0700 (PDT) Message-ID: References: <49B74373.3090609@gmail.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: saurabh gupta , git@vger.kernel.org To: Johannes Schindelin X-From: git-owner@vger.kernel.org Wed Mar 11 17:34:03 2009 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1LhRNG-0000yW-CZ for gcvg-git-2@gmane.org; Wed, 11 Mar 2009 17:33:42 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751688AbZCKQcO (ORCPT ); Wed, 11 Mar 2009 12:32:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751790AbZCKQcN (ORCPT ); Wed, 11 Mar 2009 12:32:13 -0400 Received: from mail.lang.hm ([64.81.33.126]:59572 "EHLO bifrost.lang.hm" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751727AbZCKQcM (ORCPT ); Wed, 11 Mar 2009 12:32:12 -0400 Received: from asgard.lang.hm (asgard.lang.hm [10.0.0.100]) by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id n2BGW5iC008338; Wed, 11 Mar 2009 08:32:05 -0800 X-X-Sender: dlang@asgard.lang.hm In-Reply-To: User-Agent: Alpine 1.10 (DEB 962 2008-03-14) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On Wed, 11 Mar 2009, Johannes Schindelin wrote: > Hi, > > On Wed, 11 Mar 2009, saurabh gupta wrote: > >> What I think is to implement file formats other than text like that >> written on wiki i.e. latex, xml, or even any database file (db file). >> Another idea (although it can be weired also) is to implement the new >> file formats in the plug-in formats. For example, to incorporate the >> merger engine for a new file format, a plug-in is created and can be >> integrated with the present merger in the git. However, I am not sure >> how much valid is this idea to make the present merger in git to be >> compatible with the plug-ins for enabling newer file formats. > > I am not sure that a plugin structure is needed. Take, for example, three > different .xml based formats: OpenOffice documents, .svg files and Ant > build.xml files. They need very different user interfaces. > >> I am thinking of using gtk+ libraries to implement the GUI part (I am >> quite comfortable with gtk+). > > I mentioned Tcl/Tk, because it is portable, but I'll also take gtk-based > stuff ;-) > >> However, I think in merging and notifying about the conflicts in the xml >> files, other things can also be put forward. Like the GUI will show the >> number of tags differing and what are the new tags added and even if any >> tag is renamed with the content unchanged. If possible, how about >> showing a tree like structure (just like DOM model) to compare (or diff) >> the two xml files. > > This is a little bit too low-level for my liking. Taking the OpenOffice > example again, the GUI should not expose XML at all... don't assume that you have a GUI just to handle a filetype. if you have one, good, make use of it. but have a fallback for how to deal with things if all you have is a text terminal. David Lang