Funnily enough, I was just looking at the API. Looks like there's a few holes in there. On one hand, I like the Eclipse team's approach of not making something "API" unless there's an actual consumer in the wild, on the other hand, if we change the api in the near term, we'll probably affect a lot fewer people than they would.I like ListTodos, particularly w/ optional filtering
I don't know the history of NewTodo vs NewRichTodo, but I think it looks like they should be merged. It looks like RichTodo exists as a sort of hack to add parameters like project to the call w/o changing the signature. I'm proposing that NewTodo should explicitly accept a projectID and we get rid of NewRichTodo altogether. (the client should be responsible for the shortcut string voodoo that the RichTodo method handles today) I also think there should be a way to mark Todos as finished via the api. One thing the API does differently than the Web interface is that you couldn't implicitly create a new project by entering a new project name with a new todo. Does that bother anyone? Before the next release, I think we should handle these cases NewTodo(user,token,context,project,description,note) FinishTodo(user,token,todoid) ListContexts(user,token) ListProjects(user,token) ListTodos(user,token,contextid,projectid) in all these cases, context and project should be optional. That still leaves a lot of functionality on the shelf, but I think opens up the door to a first wave of clients. On Nov 27, 2007 1:26 PM, Corey Bordelon <[EMAIL PROTECTED]> wrote: > There doesn't seem to be much use since the API is only available in the > non-production version. > > The documentation on it is missing, but I think that's because there is > still work being done on it. There is an excellent /integrations page, but > it only give examples. That said, here's what I've gathered about it: > > It is only available as an XML-RPC. The methods available are > > - NewTodo ( userName, token, contextID, description, notes) - This > adds a todo to a context > - NewRichTodo (userName, token, defaultContextID, description, > notes) - This adds a todo, but it has a specific purpose that I'm unaware > of. > - ListContexts (userName, token) - Lists all Contexts > - ListProjects (userName, token) - Lists all Projects > > I'm attaching a very basic patch to add another method to this list: > ListTodos (username,token) - Lists all Todos > > I'm still figuring my way around rails, but this was simple enough to > accomplish. I may try to add some more specific ListTodo methods, such as > by Context and Project to save on the processing side of the client. Any > help on what it takes to filter the list of todos down on the web services > level would be appreciated > > On Nov 19, 2007 2:55 PM, James Kebinger <[EMAIL PROTECTED]> wrote: > > > Folks, is there a list of consumers of the tracks API anywhere? Failing > > that, can everyone who knows of one mention it? > > thanks > > > > > > _______________________________________________ > > Tracks-discuss mailing list > > [email protected] > > http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss > > > > >
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
