Le Tue, 3 Apr 2012 12:54:24 +0200, Stephan Beal <[email protected]> a écrit :
> i can't promise to provide statically-generated copies. (A) i > wouldn't use them myself, so the maintenance involved would be 100% > time sink for me, (B) the nature of a JSON API excludes any clients > which cannot process JSON (e.g. static web pages), so i don't feel > compelled to make any extra effort for such clients. You can generate static pages from JSON using server-side scripts ;) That's what I do: http://dev.kd2.org/fotoo/ is using https://fossil.kd2.org/fotoo/wiki?name=about with the JSON API and generates a static page. Personally I have a smartphone with Opera Mini (so no JS), because data is very expensive here, and Opera Mini is the most widely used mobile browser in the world I think. As a web developer I can say that nobody should ever rely on JS for web. JS should enhance the experience, but not keep the user from accessing the content, which is the main stuff you want from a web page. > That simply means i can't tie in to fossil's built-in mechanism for > help. i have considered adding such a feature to the JSON API, and > even experimented with it, but (A) the help results would have to be > in JSON form (making them quite unreadable from the command line) and > (B) the API changes all the time, so maintaining the help text would > be a PITA at this point. OK I get it that's kind of a pity but ok. Another point, you're saying that the API is changing all the time, but don't you plan to make it stable at one point? We can't build anything on top of the API if it's not stable and can be changed anytime. -- BohwaZ http://bohwaz.net/ _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
