Re: The future of gitweb - part 2: JavaScript
From: Pau Garcia i Quiles <hidden>
Date: 2016-06-15 22:51:03
Hi, My suggestion is going to be tremendously unpopular, but still: if I were to develop my own gitweb, I'd use Wt ( http://webtoolkit.eu ) + libgit2. In fact, there is a very basic gitweb-like example bundled with Wt sources, it's available online at http://www.webtoolkit.eu/wt/examples/git All those detect if this feature is available or not, fallback to plain HTML (no Javascript, no AJAX), use HTML5, or SVG, or... where available are already solved (and are totally automatical) in Wt. It's C++ with Boost and Qt-like API, not plain C, Perl or bash scripting, though. On Thu, Apr 14, 2011 at 11:54 AM, Jakub Narebski [off-list ref] wrote:
This is second installment, talking about JavaScript (client-side) part of gitweb code. [...] Those issues are already solved in __JavaScript libraries__ and frameworks, probably better way than in our attempt. Using JavaScript framework would also give as higher level constructs, and could replace what we have and could have in gitweb/static/js/lib:
-- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer)