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

Item attributes meanings? #1

Open
jonathanlaniado opened this issue Apr 28, 2018 · 6 comments
Open

Item attributes meanings? #1

jonathanlaniado opened this issue Apr 28, 2018 · 6 comments

Comments

@jonathanlaniado
Copy link

jonathanlaniado commented Apr 28, 2018

Hi, thank you for this project! I'm porting this over to Python, but I am trying to figure out what a to-do item's attributes are.

I have the basics down, but I don't know the majority of them. For instance, would you happen to know what icsd or ix or tg refer to?

@meub
Copy link

meub commented Jun 12, 2018

I'm super late to this but it looks like the following based on some quick testing:

-tg refers to the tag, for me "Work" is an item in that tg array called ""CC-Things-Tag-Work"
-tt refers to the Title of the To Do
-ss refers to the To Do status, 0 for To Do and 3 for Done I think?
-nt refers to the Note, as in "<note xml:space="preserve">I'm a note!\n"
-dd refers to the deadline on the Note

Still working on figuring out the rest. I'm examining the app with Charles with the intent of build a simple web-based read-only view of my open Todos. This doesn't seem possible without parsing the entire history of changes which seems ridiculous. Am I missing something?

@jonathanlaniado
Copy link
Author

I think I figured out some others.

cd is the item's created date
ar is a list of areas
pr is a list of projects
md is the item's modified date

I also think that st is something like destination, where:

  • 1 = today/evening (set sb to 1 for evening)
  • 2 = someday

@meub
Copy link

meub commented Jul 13, 2018

I did a Charles capture with a new installation of the app with syncing enabled and discovered that the app gets the current history index ("https://cloud.culturedcode.com/version/1/history/" + account_id) and then in batches of 2500 gets all the history from the beginning of time ("https://cloud.culturedcode.com/version/1/history/" + account_id + "/items?start-index=" + index_in_increments_of_2500).

I then wrote some python to construct the list of todos from the history list (over 12000 items) by taking the list of events and applying it to an array of todos to finally arrive at the current state of things. However, this still seems insufficient for doing what I wanted. It never is quite accurate. Have you had any luck, perhaps with a different approach?

@aaronbeekay
Copy link

@meub I’m in about the same place you are, trying to get a list of current todos by rebuilding the history.

Have you had any luck with other methods since then? I would love to look at your Python code if it’s available.

@chandlerroth
Copy link

I appreciate the work here — definitely wanting to contribute to figuring the Things API out. Has there been any more active research?

@vrinek
Copy link

vrinek commented May 27, 2024

Late to the party but, I started documenting these props here: https://github.com/vrinek/things2org/blob/main/properties.org

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

5 participants