On Thu, Mar 30, 2017 at 12:23 PM, Paul Hammant <p...@hammant.org> wrote:
> Nice achievement and great document on the JSON-api usage (and challenges > you faced). <cough> should be in markdown under source-control of course > </cough>. > i agree, it "should" be in source control somewhere, but at the time it was written (hand-in-hand with the code) that was deemed impractical - i needed something i could edit live from non-development machines, as i often edited it from machines other than my development box. Also, how best to structure it in a wiki wasn't (and still isn't) clear (i wouldn't want it packed up in a single long wiki page). At that time (late 2011), the only wiki format fossil supported was its own, so markdown was not an option. What was the name of your GoogleCode application? They all got auto-moved > to Github at some point. I'm example orientated and can only really make > leaps in understanding after looking a tight solutions :) > The gcode project was called 'wikiwym', a JS implementation of the gcode wiki renderer (and i was one of the devs, so i "should" (might) still have access to export it). However, i'm currently on long-term medical leave for a back/nerve problem which partially disables my hands, and programming (or any significant amount of typing, for that matter) is off-limits for me. "One of these days," when i'm finally off medical leave, i'll get around to fixing the links which import the external code. (i didn't even notice the problem until yesterday.) -- ----- stephan beal http://wanderinghorse.net/home/stephan/ "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
