Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Old links from blog #6

Closed
tukanos opened this issue Aug 31, 2011 · 1 comment
Closed

Old links from blog #6

tukanos opened this issue Aug 31, 2011 · 1 comment

Comments

@tukanos
Copy link

tukanos commented Aug 31, 2011

This issue number may also refer to the older ticket #6, now #1473.

Hi,

I'm know this is not the proper place to write this. However, the blog & forums are not accepting the registration of new members so I write it here.

I would like to write ruby tracks <-> outlook sync in different way than proposed in the wiki outlook integration. Does not work with outlook 2010. I would like to get hang of "older scripts" to get idea how to approach track's API.

So my question is, when do you think these scripts could be reachable again?
http://www.getontracks.org/downloads/index/ruby-command-line-api-script
http://www.getontracks.org/downloads/index/script-to-allow-adding-of-next-actions-by-sms
http://www.getontracks.org/downloads/index/adding-next-actions-via-scripts-the-tracks-api

Thank you,

Tukanos

@lrbalt
Copy link
Member

lrbalt commented Sep 27, 2011

these are very old scripts from 2006. They probably don't work any more.

  • There is a ruby runner included in Tracks to handle emails and sms, see your integration page from the "?" menu
  • There are two example CLI scripts included in /doc of the current master tree to add todos to Tracks
  • on the forum there are several scripts for adding todos to tracks using the SOAP or REST api

Otherwise you can email bsag to ask if she has the old scripts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants