Hi Dave, I am hoping to find some time over the next few days to work on this and will send a note when I have some progress. It looks like an interesting challenge and similar to the todo work I already did. Thanks for sharing.
Thanks, Joe On Wed, Mar 1, 2017 at 11:13 AM, Loyall, David <david.loy...@nebraska.gov> wrote: > >>>> In the spirit of RosettaCode, may I present > http://www.todobackend.com/ ? > >>> > >>> Seems I should give it a try :) > >>> > >>> I don't understand the full extent of the task yet, but could it be > >>> something > >> > >> To be correct, I don't understand it at all! > >> > >> Is the only "spec" a bunch of JavaScript sources? I don't feel like > >> wanting to analyze that, sorry! > > > > Another clue could be to look at the server end: > > > > For instance one in Python > > > > https://github.com/KixPanganiban/todo-falcon/blob/master/todo.py > > > > > > AFAIK the whole thing is like a "hello world" for persistence on the > server and a very light GUI on the client. > > Visit http://www.todobackend.com/client/index.html?https:// > todo-backend-clojure.herokuapp.com/todos for example. > > This is a javascript client. It speaks to some backend. Which backend is > actually configurable. The main site lists dozens. > > So the goal is to make a picolisp backend which is compatible with this > client. > > For language learners, once they know a few of these backends... they will > be able to learn about new languages by reading the source code of other > backends. > > For daily grind developers, they can compare frameworks, I guess. :) > > I guess "backend" here means a RESTful API. (I'm probably misusing the > term.) > > You don't have a read the javascript "spec", you can run this: > http://www.todobackend.com/specs/index.html > > What it does is connect to any backend and attempt to perform actions that > are expected to be implemented. (I wonder if anyone has used "machine > learning" to implement a compliant backend...) > > Cheers, > --Dave >
