Re: FFmpeg considering GIT

From: Junio C Hamano <junkio@cox.net>
Date: May 7, 2007, 19:10 UTC
Message-ID: <7vfy6878la.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <17983.6136.147062.346626@cargo.ozlabs.ibm.com>

Paul Mackerras <paulus@samba.org> writes:

Show 15 quoted lines

> Linus Torvalds writes:
>
>> Finally, it realy _should_ check that the first 7 characters of the commit 
>> log (the ones it ignores by just asking for substring 7..) are actually 
>> the exact characters "commit ", but I'll blame my lack of comfort with the 
>> language again.
>
> I have thought about rewriting it in a different language, but I
> haven't found anything that really appeals.  I don't want to go to
> C/GTK or C/Qt since that would make it hard to port to Windows and
> MacOS AFAIK.  Python/Tk would be a possibility, but I have never
> learnt python and I'm actually not all that comfortable with having to
> do things the object-oriented way.
>
> Any suggestions?

I've looked at Perl and Python Tk integration in the past; they take slightly different approaches. The Perl integration tries to first libify Tk part to make it less dependent to the host language, tcl, and then retargets it to a new host language, Perl. Compared to that, Python integration was shallower; calling from Python to Tk and callback from Tk to Python were done using Tcl as intermediary. Which looked somewhat hacky but at the same time cleaner. From scriptability point of view, both were much more pleasant to use than tcl. You would have object-orientation in the nature of data anyway (e.g. your commitdata, commitlisted, commitidx and friends will not be look-up tables keyed with commit object name, rather they will become attributes to commit objects), so I would expect doing it in Python+Tk would feel natural.