On 7/22/2013 4:29 PM, fossil-users-requ...@lists.fossil-scm.org wrote:
Date: Mon, 22 Jul 2013 10:02:47 +0200
From: Stephan Beal <sgb...@googlemail.com>
To: "Fossil SCM user's discussion" <fossil-users@lists.fossil-scm.org>
Subject: Re: [fossil-users] Random thoughts on Fossil v2
Message-ID:
<cakd4nah3bxxcg0pbk5w3+nja2hynmbhfp6plgmvu8ykfsaw...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi, Clark! A brief response from the office, and a longer one tonight when
i get home...
On Mon, Jul 22, 2013 at 2:01 AM, Clark Christensen <cdcmi...@yahoo.com>wrote:
Scripting language: I understand the Tcl roots, and I hope you would
consider Javascript as a target. JS seems more universal these days.
Maybe the Tcl guys would disagree. I have no idea what that means from an
implementation standpoint.
The problem is the interpreter. i am not aware of a small embedable JS
interpreter. SpiderMonkey/Jaegermonkey are complex and poorly documented.
Google V8 is nice but (A) huge, (B) C++, and (C) they recently made drastic
API changes which invalidated every single v8-using client out there
(breaking 4-5 years of accumulated code of mine, and i'll never have the
time to fix it), which means that very few people outside of Google can
actually use v8 at the moment. JS _would_ also be my first choice, if we
only had a small, well-maintained interpreter.i don't know TCL, but the TCL
and Fossil communities seem to be cosmically bound to one another. There
are relatively few well-established small/embeddable interpreters. Lua,
TCL, ... none others come to mind (which are small).
Would using something similar to Vim's mechanism (allowing Fossil to be
compiled with Lua/Ruby/MZScheme/Python/etc. support) be more acceptable?
Of course, Vim does have its own scripting language (Vimscript) but this
"language support" is available to users via the Makefiles.
My own humble requests for Fossil v2 include:
- use of Markdown formatting in tickets (unless, this is already possible?)
- +1 for full text search in tickets...and maybe embedded wiki files if
possible
- support for kernel-style commit messages:
For example, you have a commit message like this:
Capitalized, short summary line
<Detailed explanatory text which can be long, preferably wrapped to
around 72 characters or less>
Fossil would then show the summary line in the Timeline view, both in
the web GUI and commandline. Clicking the specific commit would then
display both the summary line and the explanatory text.
(I tried altering the Timeline view CSS for this from a few threads
back, but it made the Timeline page graph ugly.)
Thanks, Stephan!
--Arnel
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
