Hi, Caleb! i can't say much to points 1 and 2, but...
> 3) The web interface could use a face lift, as well as some HTML5 > functionality. > > I've got a lot of web development experience and would love to contribute > in this area, also. > > All of the work on the JSON APIs is a great step toward making the entire > interface XHR compatible. What are the community's feelings on jQuery? I get > the gist that externals are trying to be avoided, so that's why I'm asking, > The JSON API itself doesn't need any 3rd-party JS libs (it's jot JS-specific, some of my test code is written in Java, and Zach's working on Python code). That said, jQuery is (by far) my favourite of the various JS libs, and is the only one i use with any regularity. For any given HTML interface, of course, jQuery/mojo/whatever would be essentially necessary. Rather than initially re-implement the existing HTML interface, my suggestion would be that we create an external HTML app, independent of fossil. The main advantages would be: - no concerns about dependencies vis-a-vis the fossil core - it would help us figure out what the JSON API needs (and how what it currently can do might need to change) - releases would be independent of fossil There's a live prototype/demo here: http://fossil.wanderinghorse.net/repos/fossil-sgb/json/ That copy is a week or 10 days old, but not much has changed in that time. I would love to write a library that turns the current site in to a highly > interactive version without touching the HTML or CSS at all. > That's one of the goals of the JSON API. In case you haven't see "The Doc" yet: https://docs.google.com/document/d/1fXViveNhDbiXgCuE7QDXQOKeFzf2qNUkBEgiUvoqFN4/edit?hl=en_US That contains the current status, the TODOs, etc. We're of course more than happy to have collaborators on that. i'm running out of steam, going through one of my slow periods (which typically last 4-6 weeks), so collaborators could really help move it along (== get it out the door more quickly). In particular, your experience with web apps would be very welcomed :). The JSON API still has lots of room for change, so now's the time to get your opinions voiced. The only small catch is that the repo requires one to sign a copyright waiver and send it to Richard before commit access will be granted or patches accepted: http://www.fossil-scm.org/fossil/doc/trunk/www/copyright-release.html it's a painless process, though. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
