Hi Rob, 2007/9/6, Rob McMullen <[EMAIL PROTECTED]>: > > Nicely done from a user-interface point of view as > well -- didn't have to read any instructions to start using it.
That's one of the goals for Task Coach, so I'm glad to hear this. > I haven't had a chance to look at the source yet, but I'm sure there > are areas of overlap. I had definitely been thinking about a task > managing major mode for peppy, but it was just going to be something > simple. Now, I wonder if I could make a wrapper that would allow Task > Coach to be plugged in? Because now there's no way I want to spend > any time writing some mini-task-list thingy when there's all this > functionality in Task Coach. Maybe a Task Coach major mode is too > ambitious, so I wonder if instead if you'd thought about communication > between apps to perhaps submit new tasks from an IDE. The option that should be possible right now is to reuse code from TC to create tasks and write them into a taskfile. The architecture more or less follows the Model-View-Controller/Presenter pattern. You should be able to use code from the Model and Controller layers (i.e. the domain and persistence packages) to do that. Hmm, there is one problem though: if you write tasks to a taskfile that is open in TC, TC won't currently notice that. In the longer term I'd like to support the iCal standard and then you should be able to mail a task to the user to add it to her tasks. But that is not implemented in TC yet and I'm not sure how communication back to the IDE would work. I guess the best solution would be to expose an API on a network port? Is this a job for pyro or twisted maybe? Cheers, Frank
