Bruno Lopes's dashboard

Bruno Lopes started following the question "The iPhone app is not available in all countries" in Delicious Monster.

A comment on the idea "Amazon's banning of iPhone App" in Delicious Monster:

Just did so. Honestly, I was very excited to know about the iphone app, and finding out that because of amazon I'll not be able to use it really pissed me off. I hope they manage to revert it. – Bruno Lopes, on August 09, 2009 01:06

Bruno Lopes started following the idea "Tell Amazon to stop blocking Delicious Library for iPhone" in Delicious Monster.

Bruno Lopes marked one of Ken Wiesner's replies in Delicious Monster as useful. Ken Wiesner replied to the idea "Amazon's banning of iPhone App".

Bruno Lopes started following the idea "Amazon's banning of iPhone App" in Delicious Monster.

Bruno Lopes marked one of Jessie's replies in Delicious Monster as useful. Jessie replied to the question "The iPhone app is not available in all countries".

Bruno Lopes started following the idea "Different colours for the boxes (done, current, backlog, icebox)" in Pivotal Labs.

Bruno Lopes started following the idea "Pivotal Traker for iPhone, only view lists and add Stories to icebox." in Pivotal Labs.

Bruno Lopes started following the question "keyboard shortcuts in tracker?" in Pivotal Labs.

Bruno Lopes started following the question "Add ability to add stories to bottom of icebox ( currently goes to top )" in Pivotal Labs.

Bruno Lopes shared an idea in Pivotal Labs on January 15, 2009 15:01:

Stories retrieved via the api should have a last change timestamp

I'm working on a tool that uses the api data to store a local cache of the stories. Instead of retrieving and storing all the stories all the time, I'd like to be a little more intelligent and only update locally the stories that have changed.
To do so now I would need to compare every story locally with the story I obtain via the API and only update the ones that changed.
At the very least the API could supply a "last-changed-at" time stamp which I could store and use to update only the changed stories. Ideally we'd have access to a last-changed-at time stamp and to the history of the story, so that I don't have to compute the changes myself.

Thank you

Bruno Lopes started following the idea "It would be nice to have Timestamp each time the Status field is changed" in Pivotal Labs.

Bruno Lopes shared an idea in Pivotal Labs on January 06, 2009 02:22:

Format for API dates

Format the dates the API returns as numbers instead of using the short (english) month.
As it is, the API returns the dates in the following format: Sep 16, 2008. While I can ask the DateTime library to parse it according to English Culture rules, I think it's a bit frail, and we would be better served with a more culture-agnostic format for the dates.
Ideally I think the dates would come ISO formatted, with timezone information if it includes time, but YYYY/MM/DD would be better nonetheless.

A comment on the problem "Importing tasks from a CSV with international characters cuts the fields short." in Pivotal Labs:

Hey,
I'm using Windows XP with SP3 and Office 2007 to work with the csv file.
Excel I believe outputs the file in ANSI, from what Notepad2 can tell me.
What I ended up doing is saving from excel as csv (which outputs the sheet with ; as separator character), loading it in emacs to turn the ; into , and placing "" around the values, and then loading that file in notepad2 to encode it in UTF-8.

I think the link got killed on the original report, so here it is again: http://dl.getdropbox.com/u/118385/int... . – Bruno Lopes, on December 12, 2008 16:01