1. I am guessing that fossil's creator might prefer to keep the gui bit seperate.
2. Is it not true that a fossil GUI only need work on local check-outs? 3. So, just create a front-end that shells out to the fossil cmd-line. Andy Reynolds > On 04/26/2010 05:00 AM, Andy Reynolds wrote: >> I think a 'proper' fossil-gui should ideally be a single binary and cross >> platform - maybe java but thats not my area. > > IMHO would be more interesting to somehow integrate into fossil itself, > via something like https://mozillalabs.com/bespin/ - except make "the > cloud" instead "a fossil instance on my computer or another computer I > admin" - and of course glue / hook code. > > """The Bespin project is building a web-based code editor using the > emerging HTML5 standard. The editor is easily extensible with JavaScript > and can be used in your own applications or on our experimental hosted > service.""" > > -- > Daniel JB Clark | http://pobox.com/~dclark | Activist; Owner > \|/ > FREEDOM -+-> INCLUDED ~ http://freedomincluded.com > /|\ > Free Software respecting hardware ~ Lemote Yeeloong reseller > > > > > ------------------------------ > > Message: 2 > Date: Thu, 29 Apr 2010 20:39:55 +0200 > From: Stephan Beal <[email protected]> > Subject: Re: [fossil-users] Didn't someone mention working on a fossil > GUI > To: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > On Thu, Apr 29, 2010 at 7:47 PM, Daniel Clark <[email protected]> wrote: > >> IMHO would be more interesting to somehow integrate into fossil itself, >> via something like https://mozillalabs.com/bespin/ - except make "the >> cloud" instead "a fossil instance on my computer or another computer I >> admin" - and of course glue / hook code. >> > > If we could agree on JSON-based interfaces for outbound fossil data (e.g. > timeline list, artifact details, etc.), and add the appropriate APIs, it > would be relatively easy to build web-based GUIs which operate using > either > a CGI- or server-mode fossil in the back end. Getting a command-line > version > to work with json input would be more effort. e.g. via an interface like > > fossil json < jsonFileContainingCommandStructure > > e.g. the input json might look like: > > {"command":"timeline", "arguments":["-n",20]} > > (The fact that fossil is a monolithic app, and not a library+app, would > make > such an interface more difficult to implement.) > > To this end, i have investigated several C-based JSON libraries, but so > far > i have found nothing which particularly pleases me (in terms of licensing > and API interface). That said, the JSON format is simple enough (and well > documented enough) that writing a custom parser for it wouldn't be all > that > much work. (Maybe that's something for me to do this weekend.) > > One element of JSON which i can imagine (but am not certain) might be > problematic in conjunction with fossil is that it is UTF-8 encoded, and i > don't know if fossil handles UTF8. > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.fossil-scm.org:8080/pipermail/fossil-users/attachments/20100429/a42b0305/attachment.html > > ------------------------------ > > Message: 3 > Date: Thu, 29 Apr 2010 21:09:27 +0200 > From: Stephan Beal <[email protected]> > Subject: Re: [fossil-users] Didn't someone mention working on a fossil > GUI > To: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > On Thu, Apr 29, 2010 at 8:39 PM, Stephan Beal <[email protected]> > wrote: > >> To this end, i have investigated several C-based JSON libraries, but so >> far >> i have found nothing which particularly pleases me (in terms of licensing >> and API interface). That said, the JSON format is simple enough (and well >> documented enough) that writing a custom parser for it wouldn't be all >> that >> much work. (Maybe that's something for me to do this weekend.) >> > > Crockford provides one: > > http://www.json.org/JSON_checker/ > > but it needs to be refactored a bit in order to be useful. It currently > doesn't have a way for the user to accumulate the parsed data as elements > are parsed, but i don't think it would be too difficult to expand it into > a > push parser (like libexpat's interface). > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.fossil-scm.org:8080/pipermail/fossil-users/attachments/20100429/f2531f02/attachment-0001.htm > > ------------------------------ > > Message: 4 > Date: Thu, 29 Apr 2010 12:16:25 -0700 > From: Andreas Kupries <[email protected]> > Subject: Re: [fossil-users] Didn't someone mention working on a fossil > GUI > To: [email protected] > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Stephan Beal wrote: >> On Thu, Apr 29, 2010 at 8:39 PM, Stephan Beal <[email protected] >> <mailto:[email protected]>> wrote: >> >> To this end, i have investigated several C-based JSON libraries, but >> so far i have found nothing which particularly pleases me (in terms >> of licensing and API interface). That said, the JSON format is >> simple enough (and well documented enough) that writing a custom >> parser for it wouldn't be all that much work. (Maybe that's >> something for me to do this weekend.) > > 'yet another json library' aka 'yajl' (on github afaik). With yajl-tcl > binding > by Karl Lehenbauer, definitely on github (under that name). > > tcllib - json, and json::write > > -- > Sincerely, > Andreas Kupries <[email protected]> > Developer @ <http://www.activestate.com/> > > > ------------------------------ > > Message: 5 > Date: Thu, 29 Apr 2010 21:17:19 +0200 > From: Stephan Beal <[email protected]> > Subject: Re: [fossil-users] Didn't someone mention working on a fossil > GUI > To: [email protected] > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > On Thu, Apr 29, 2010 at 9:09 PM, Stephan Beal <[email protected]> > wrote: > >> Crockford provides one: >> >> http://www.json.org/JSON_checker/ >> > > And this one looks quite good (and is a push parser): > > http://fara.cs.uni-potsdam.de/~jsg/json_parser/ > > with a BSD-like "do no evil" license > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.fossil-scm.org:8080/pipermail/fossil-users/attachments/20100429/688c6394/attachment-0001.htm > > ------------------------------ > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > > End of fossil-users Digest, Vol 27, Issue 35 > ******************************************** -------------------------------------------------------------------------------- No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.814 / Virus Database: 271.1.1/2844 - Release Date: 04/30/10 07:27:00 _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
