ForumsDevelopersCustom field in tasks API
Custom field in tasks API
| Author | Message |
|---|---|
|
haeffb |
Would you consider adding a custom field to tasks through the API? I'm envisioning a method whereby a developer could extend, for instance, a mobile applications's functionality by storing data that's not currently available in Toodledo such as location, etc. If a developer adds fields in a third-party app today, there's no way to store that info in Toodledo without commandeering one of the existing fields (tags, for instance).
If you allowed a custom field in the task database, then a developer could store whatever additional info is necessary in a text format (JSON). You could limit the field length if storage is a concern. |
|
Jake Toodledo Founder |
This is on our to-do list. In the meantime, what we have been recommending to developers is that they create a Notebook entry called "AppName MetaData" and store all your extra information in there as XML or JSON or whatever. Then you can just grab that notebook entry and parse out your custom data. This obviously isn't ideal, but it is better than commandeering an exiting field that the customer might be using.
|
|
rbrooke99 |
This would be a fantastic feature. Please can you tell us when this is likely to happen.
I am in development at the moment as dont want to go down the Notebook entry route you mention (with all its associated issues) if this is something that is likely to happen in the near future. Any indication you could give on this would be most appreciated This message was edited Jul 31, 2010. |
|
Jake Toodledo Founder |
This is on our to-do list, but it is our policy to not comment on our roadmap or delivery dates for future feature improvements.
|
You cannot reply yet
U Back to topic home
R Post a reply
To participate in these forums, you must be signed in.