Iteration 1: Tasks up for grabs

May 5, 2011 at 7:12 PM
Edited May 5, 2011 at 7:14 PM

After I've been regression testing the new DB (should be finished by the end of this week), these tasks are also available:


May 7, 2011 at 8:31 PM

I found some minor problems during regression tests of the DB.

I'll try to resolve them tomorrow. Until it's done, the Refactor FestivalAdapter task ( should not be started.

May 8, 2011 at 10:41 AM

Regression test is now done and checked in.

May 8, 2011 at 6:56 PM

I've started working on the refactor festivaladapter task. I am about half done and the work is checked in. Moved scenes to a content provider. Events are still in the same place.

May 8, 2011 at 10:59 PM


Just a follow up for everyone on the events view now in the 2011 db.

The events view is today a join of the Acts and Schedules tables. The view is a retro fit of the new data, so that the existing code doesn't break. This de-normalised view comes from the fact that last year, all data was based on schedules and their attached data, not the other way around. As there was no way to recognize if the schedules related to the same act, all data was taken in, even if the title and description could be a repetition.

It's not written in stone to only use the events view. However, it does currently work as a sort of "flattening" of the root (Acts) and it's children (schedules).

This can be seen in for example search results, where, when searching for "artist x", which has 3 schedules, will result in 3 rows in the result. I think that's preferred instead of having to "drill down" (one less click for the user), however, an update of the rows in the results view should be done, as they are quite anonymous right now. The results rows should, in my opinion, include schedule time, just as the rows in the favorites list. I can make a task on that... 

May 13, 2011 at 11:31 AM

Ping ping!

As the refactor FestivalAdapter task ( has now been done (check-in 66541), these tasks are now really up for grabs ;o)

Furthermore, the following are suggested for implementation in Iteration 1:

Wanna start working? Grab the task by:

  • Letting everyone know that you intend to work on it here in discussions.
  • After go-ahead: Assign the task to yourself, set status to Active and Release to Iteration 1.


May 13, 2011 at 7:01 PM

I'm think about taking (.Net service) on Sunday, if no-one else from the server side team are planning to? Alternatively I'll take ...

May 15, 2011 at 10:54 AM (.Net service) is now done, which opens up for (Download db updates from app - Android)...

May 17, 2011 at 1:07 PM

Hello, I take 6468 Show categories in event detail view: (Android).

May 17, 2011 at 1:28 PM

Anatoly, tonight I was planning to do a change in the DB and the view, which is needed to lookup links (which I work on) and categories (they both need ActId). I'll let you know here, when I'm done, so you can start, ok?

May 17, 2011 at 1:39 PM


May 17, 2011 at 5:50 PM

Done with my stuff.

Anatoly - how this relates to you: Basically the EventDetailActivity now loads the ActId into a variable, which can then be used for queries on links and categories belonging to the act.

I made a LinksProvider and some test client code in EventDetailActivity that you can use for inspiration (the real client code for links is yet to made, as part a different issue). The *Provider pattern is what we use from now on to query for data... let me know if you have any questions...

May 17, 2011 at 5:56 PM
Edited May 17, 2011 at 7:49 PM

By the way, the mock-ups for 6468, are they enough for you to go on with? 

The categories are depicted with buttons, but that's honestly not my goal ;o) I was thinking more in the lines of some nice 9-path image, but for now we can insert either buttons or just generic layouts, as long as they react to clicks etc.

May 19, 2011 at 11:39 AM

I'm contemplating on taking: English as default language: (Android) - any comments before I begin?

May 19, 2011 at 1:21 PM

no comments :) I am wondering what I could do :-)

May 19, 2011 at 1:26 PM

Ok, I take 6424