It looks like most of the pieces are place, bar the Htsql(parser?). I like the ability to instrument fossil as shown on the Htsql site, - perhaps using http://www.simile-widgets.org/timeplot/ to track activity over time.
But I don't think Htsql is a requirement for this, and extending the reports functionality in the ui to allow for the creation of new views and even templating json. I'm using fossil for project management in addition to scm. S. On Friday, February 4, 2011, Richard Hipp <[email protected]> wrote: > I just ran across HTSQL (http://htsql.org/) a few moments ago. I haven't > looked at it much, yet, but it seems like an intriguing idea. > > Suppose we did this: > > (1) Add a small assortment of VIEWs and/or VIRTUAL TABLEs to Fossil that > allow things like timelines and branch lists to be queried as if they were > plain old tables. > > (2) Add an HTSQL-like interface to Fossil that returns results in either > HTML, XML, or JSON. > > (3) Add a single command that lets you easily submit any URL request from the > command-line. (The "http" command is close to this already, but it would be > better if you could put the URL as an argument on the command-line rather > than having to pipe it into standard input.) > > I'm not exactly sure what problem the above solves, but it seems interesting > all the same. Please do not hesitate to expression confirming or contrary > opinions... > -- > D. Richard Hipp > [email protected] > -- -- Stephen De Gabrielle [email protected] Telephone +44 (0)20 85670911 Mobile +44 (0)79 85189045 http://www.degabrielle.name/stephen _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
